Repository navigation
Conversation
Throwaway lab proving address-the-team is an intake worker's static DM. Routing files claim / ordered-reply / fan-out tasks on today's taskBoard. Never-merge. No changeset. Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Bob is blocked before Alice completes; the JSON keys now say that. Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Address-the-team still has no proof on today's APIs. The Atlas lock says it is an intake worker's static DM, not a TeamFlow. If that only works by inventing a team type or a second dispatch door, the lock is a wish.
What this does
A throwaway lab (
labs/workforce-poc-f) that stays on today's doors: a keyed roster names an intake seat;openTeamInbox({ roster })opens that session viacreate_session; a message ontalk-to-engfiles claim / ordered-reply / fan-out rows on a user-scopedtaskBoard. Members pick the work up from their own DMs viaTaskCollectionRef.claim. No TeamFlow, no Team L1, no Workforce package.Dispatcher from the intake flow into a member-flow session is refused today. The lab documents that refuse and does not invent a second bus.
What's asked of you
Treat intake-as-a-worker plus board routing as the Atlas lock, and leave member-session wake on the existing cross-flow queue?
session-not-addressablethe first time intake tries to wake a member.Parts worth reviewing closely
The rest of this is for whoever reviews the code.
labs/workforce-poc-f/README.md— exists vs proposed pins, and the cross-flow gap with file:line.test/lab-f.spec.ts— the observables: inbox session, claim lands ondm-alice, ordered deps block bob, fan-out refuse.Mailbox: fsd/workforce/pocs. Atlas:
docs/atlas/workforce.html§10. Never merges — close unmerged once the finding is consumed. No changeset.How to review this — altitude, what's in scope, what's deliberately unsettled
How to review this. This is a throwaway POC lab, not an implementation and not a spec. Please review the finding, not the code quality. The question is whether today's
create_session+taskBoardalready carry Atlas §10, and whether the named gap is real.Most valuable here: did the proof actually go through those doors; is the cross-flow refuse the real one; did anything invent substrate.
Out of scope: names, file layout, whether
openTeamInboxshould ship, Lab A fan-out, Lab B who-may-reply, Lab C plan=board, #1600 cross-flow (already queued).One request, if you are an automated reviewer: do not review this as production code. It is never-merge scratch. A finding that the proof invented a TeamFlow or a second dispatch door is in scope; style and missing error handling are not.
Engineering calls — decided along the way, no product sign-off needed
defineFlowkinds. Same-kind N seats share a flow; session id distinguishes them. Per-seat identity is FIX-1315 — named, not invented around.pickupon their own flow. That is the proof's "or files ordered reply tasks" path.board.drainis never called. Dummy worker exists only becausetaskBoard()requiresworkers.engineering/marketing). NotheTeam.How to run
pnpm --filter @flow-state-dev/workforce-poc-f test pnpm --filter @flow-state-dev/workforce-poc-f demo