Repository navigation
spec(epic): dispatchTask, one tool for handing work to another worker (FIX-1870) #3109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
…, handOff retires with the ledger, coordinator checks in the closure - D2 names the FIX-1816 D3 amendment; Open 1 asks the owner whether a coordinator post becomes rows - coordinator handOff retirement moves from FIX-1875 into FIX-1872, one change with the ledger (ER-10) - closure adds the three coordinator checks, a scripted rename-map diff, package READMEs in the sweep - wait depth stays one and a timeout cancels, as shipped; onTimeout continue dropped - notice marker and openWorkstream clarified; FIX-1840 check reference corrected Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,7 +28,7 @@ The shared story once, and who publishes each specific. The prose is proposed re | |
| > Your turn pauses until the task ends, then carries on with the task's output as the tool's | ||
| > result. Nothing holds a request open while it waits, so a server restart loses nothing. A wait | ||
| > has a time limit, five minutes unless you set one between 30 seconds and an hour. When it runs | ||
| > out, the task is cancelled, unless you asked to keep it running. A worker you're waiting on | ||
| > out, the task is cancelled. A worker you're waiting on | ||
| > can't stop to ask you a question; it answers with what it has, or fails. | ||
| > | ||
| > Only wait when the result changes what you do next. Otherwise let the task run and carry on. | ||
|
|
@@ -44,7 +44,9 @@ The shared story once, and who publishes each specific. The prose is proposed re | |
| |---|---|---| | ||
| | "Giving another worker work" above, replacing the ask section and the `waitForResponse` / `timeoutMs` table rows | FIX-1875, with the tool | This document; option table in FIX-1875's `DOCS.md` | | ||
| | `background-work.md` "Waiting for the answer" rewritten to point at the section above | FIX-1875 | Its `DOCS.md` | | ||
| | `coordinators.md` and `chief-of-staff.md`: the `handOff` tool replaced by `dispatchTask` | FIX-1875 | Its `DOCS.md` | | ||
| | `coordinators.md` and `chief-of-staff.md`: the `handOff` tool replaced by `dispatchTask` | FIX-1872 | Its `DOCS.md` | | ||
| | `packages/orchestration/README.md`: the `waitForResponse` / `timeoutMs` section replaced by `dispatchTask` | FIX-1875 | Its `DOCS.md` | | ||
| | `packages/workforce/README.md`: the coordinator `handOff` section and the delivery ledger replaced by rows | FIX-1872 | Its `DOCS.md` | | ||
| | `coordinators.md`: one answer per delegate per post, fenced by the task row | FIX-1872 | Its `DOCS.md` | | ||
| | The glossary rows above; every remaining use of "ask" or "hand-off" for delivering work, across `apps/docs` | FIX-1876 | This document, then its `DOCS.md` | | ||
|
Comment on lines
+45
to
+51
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The ownership table covers only docs-site pages, but AGENTS.md reference: AGENTS.md:L210-L211 Useful? React with 👍 / 👎. |
||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When one lead owns multiple project workstreams, the existing coordinator must call
handOff({ worker, target })to select the correct existing session (packages/workforce/test/project-coordinator.test.ts:507-525); targeted workstream delegates are explicitly rejected by the ordinary task path as “takes posts, not tasks” (packages/workforce/src/delegates/worker-delegates.ts:270-287). ER-1 defines the replacement using only a row/reference and worker, whilePLAN.md:20retireshandOff, so the specified API cannot express this production route. Preserve target/existing-session addressing indispatchTask, or retainhandOffuntil parity exists.Useful? React with 👍 / 👎.