Skip to content
Prev Previous commit
Next Next commit
spec(FIX-2083): apply cross-spec audit edits
F5 goal rewrites named; F18/F19 round wake entry and wake-less host scope;
F28 routing excludes the coordinator; F32 target rule; F33 FIX-2080's
attempts rule; F38/F57/F39 migration rows and changeset lines; F43
FIX-2077 blocks FIX-2083 (epic row, graph, chain); F44 interim before
FIX-2082; F61 dispatchTask post form points at FIX-2081's row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
  • Loading branch information
claude committed Oct 21, 2026
commit ee0f4978ef65d698cf4cf83c1b05ca46bd14df31
2 changes: 1 addition & 1 deletion specs/epics/FIX-2056/DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ FIX-2081's own scope.

| Seam | Owner, then who else touches it |
|---|---|
| The task tool list (`orchestration/src/skills/task-tools-capability.ts`) | FIX-2081 owns the list and field rules. FIX-2080's settings, FIX-2082's wait and FIX-2086's `message` land after it |
| The task tool list (`orchestration/src/skills/task-tools-capability.ts`) | FIX-2081 owns the list and field rules. FIX-2080's settings, FIX-2082's wait, FIX-2083's `target` on `createTask` and FIX-2086's `message` land after it |
| The claim gate (`task-board/task-entry.ts`, `blocks/record-result.ts`) and the request's end | FIX-2077 owns the predicate and where it runs: the request's `onFinished`, run after background work drains on every terminal path (`engine/src/execution/runAction.ts:2447`→`:2630`, `:2773`→`:2918`). No engine hook needed. FIX-2082's waits wake on its ending; FIX-2078 calls it when a filed task ends |
| The wait (`tasks/helpers/wait-for-response.ts`) and its limits | FIX-2082 owns it and its limits: 5 waits deep; a tree 5 deep, 100 under its top task. FIX-2076 only sets which boards wait. A board's dispatch rides the row's wait. A bare `dispatcher({ wait: true })` has no row, and the engine awaits acceptance only (`core/src/blocks/dispatcher.ts:169-171`, `engine/src/context/dispatch-operation.ts:273-280`): FIX-2082 adds an engine wait that returns the result |
| The sweeper (`engine/src/durability/durability-sweeper.ts:40-50`), re-armed only from wait gates | FIX-2078 adds a due-time source the re-arm reads and a step that pays board debts |
Expand Down
5 changes: 3 additions & 2 deletions specs/epics/FIX-2056/SPEC.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ The reviewed snapshot; live state, and each issue's gap rows, are in Linear.
| [FIX-2080](https://linear.app/fixpoint-labs/issue/FIX-2080) · filing settings | Start, session, result, attempts; cascades; the one read for retired rows ([D3](DECISIONS.md#d3)) | — |
| [FIX-2081](https://linear.app/fixpoint-labs/issue/FIX-2081) · four tools | Four task tools, one rule per field; delegates as authority | FIX-2080 |
| [FIX-2082](https://linear.app/fixpoint-labs/issue/FIX-2082) · waits | `getTask` and the waited dispatch as one wait; 5 deep, 100 under a top task | FIX-2076, FIX-2077, FIX-2081 |
| [FIX-2083](https://linear.app/fixpoint-labs/issue/FIX-2083) · routed tasks | Posts become routed tasks; one fit check; the stopgap goes | FIX-2078, FIX-2080, FIX-2081 |
| [FIX-2083](https://linear.app/fixpoint-labs/issue/FIX-2083) · routed tasks | Posts become routed tasks; one fit check; the stopgap goes | FIX-2077, FIX-2078, FIX-2080, FIX-2081 |
| [FIX-2084](https://linear.app/fixpoint-labs/issue/FIX-2084) · worker contract | Roles checked at hire; `respond` and `dispatch` | FIX-2078, FIX-2083 |
| [FIX-2085](https://linear.app/fixpoint-labs/issue/FIX-2085) · schedules | A schedule files an ordinary task | — |
| [FIX-2086](https://linear.app/fixpoint-labs/issue/FIX-2086) · steer and follow-up | `updateTask({ message })`; finished output never changes | FIX-2077, FIX-2081 |
Expand All @@ -97,6 +97,7 @@ flowchart LR
T -->|"getTask"| W
T -->|"updateTask"| S
T -->|"createTask, delegates"| R["FIX-2083 · routed tasks"]
B -->|"a routed task stays open while its filed work runs"| R
L -->|"session, result, attempts"| R
E["FIX-2078 · endings and debts"] -->|"result to the conversation"| R
R -->|"no post entry"| K["FIX-2084 · worker contract"]
Expand All @@ -105,7 +106,7 @@ flowchart LR
```

An edge is what one issue hands the next. FIX-2076, FIX-2078, FIX-2080 and FIX-2085 start at once;
every child blocks the closure, left off. The longest chain is four.
every child blocks the closure, left off. The longest chain is five once FIX-2081 blocks FIX-2077 (FIX-2080, FIX-2081, FIX-2077, FIX-2083, FIX-2084); four until then.

## What stays as it is

Expand Down
5 changes: 4 additions & 1 deletion specs/epics/FIX-2056/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,9 @@ repo rewrite at upgrade. Each tool's `<tool>_tasks` action follows its tool. Shi
| `completeTask`, `failTask` | Return or throw: the claim gate records the ending | FIX-2081 |
| `blockTask`, `TaskCollection.block`, `unblock` | `updateTask({ status: "held" })` and `"pending"` before it starts; `waitForUser` after | FIX-2080 |
| `TaskCollection.reopen` | A follow-up: `createTask` in the task's session | FIX-2086 |
| `DELEGATED_POST_ENTRY` | A routed task through `WORKER_TASK_ENTRY` | FIX-2083 |
| `DELEGATED_POST_ENTRY`, `delegatedPostEntry`, `delegatedPostHistory`, `delegatedPostOnFinished`, `delegatedPostSchema`, `DelegatedPost` | A routed task through `WORKER_TASK_ENTRY`: declare `work` with `workerTaskEntry`; the turn still gets `{ message }` | FIX-2083 |
| `taskLedgers({ taskTurn })` | Nothing: a routed turn is a task turn | FIX-2083 |
| `defineCoordinatorFlow`'s `delegateFlows`; `defineSessionBoard`'s `postFlows` and `posts`; `posts` and `both` in `listDelegates`' takes | Nothing: a delegate is a worker whose flow takes tasks, checked by its roles at hire | FIX-2083 |
| `TaskCollectionRef.dispatch`, `TaskDispatchOptions`, `Task.dispatchCall`, the `already-dispatched` decline | `createTask`, and `updateTask({ id, status: "pending" })` to release a held row | The later of FIX-2082 and FIX-2083, with `dispatchTask` |
| `settleSplitTask` | Nothing: the claim gate settles a split when its pieces end | FIX-2077 |
| The agent worker's `run` entry | `respond` | FIX-2084 |
40 changes: 28 additions & 12 deletions specs/issues/FIX-2083/DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Solid edges are what you're signing. Dashed edges lost, and the label says why.
|---|---|
| **Instead of** | A `post: true` flag moved onto `createTask`, which refuses a goal; or the model's goal alone, as for any task |
| **Because** | [FIX-1872 D2](../FIX-1872/DECISIONS.md#d2) holds: a delegate answers what the person wrote, and the coordinator goal grades a held-out word arriving intact. A flag keeps a second shape of one tool, which FIX-2081 just retired. So the model files an ordinary task with the routing settings and its own goal, and on a turn routing a message the server attaches that message, as written, with who wrote it and the recent lines, to every task the turn files with its result to the conversation |
Comment thread
jhoffner marked this conversation as resolved.
Resolved
| **Locks in** | `target` on `createTask`, the public field naming a workstream record, accepted only from a filer whose delegates have targets. The attached message is server-written and never an input field. The routing settings are the model's per task (the concept's *chooses per task*): a routed task is attempts 1 ([epic](../../epics/FIX-2056/DECISIONS.md)): the policies file 1, and the server stamps 1 on every conversation-result task whatever the model passes: a judgment model that leaves `maxAttempts` out gets 1, never the board's default, and one that passes 3 gets 1 |
| **Locks in** | `target` on `createTask`, the public field naming a workstream record: a filing setting, set only at filing and refused on `updateTask`, and refused from a filer whose delegates have no targets. The workstream session it resolves to is server-written, stored top level beside `session` (BP-031), never an input. The attached message is server-written and never an input field. The routing settings are the model's per task (the concept's *chooses per task*): a routed task is attempts 1 ([epic](../../epics/FIX-2056/DECISIONS.md)) by FIX-2080's rule for a conversation-result task: unset reads 1, so a judgment model that leaves `maxAttempts` out gets 1, never the board's default, and any other value is refused at filing, naming the rule. The policies file 1 |

![D1: how a judgment coordinator hands a message on. createTask with the routing settings and the message attached, chosen, beside a post flag on createTask. Decides it: what the delegate answers; both keep the user's words. The price: a field and a server-attached message on createTask. Locks in target on createTask; flips if the product wants coordinators to brief in their own words](figures/d1-createtask-as-written.svg)

Expand All @@ -43,7 +43,7 @@ words. Then nothing is attached, and the goal is the brief.
|---|---|
| **Instead of** | Today's timer, which each delegate's run keeps beside its turn and which wakes the coordinator at the deadline |
| **Because** | The timer lives in the delegate's process, so a restart loses it and the round waits for some other wake. FIX-2078's wake is the engine's one due-time source ([its D1](https://github.com/fixpoint-labs/flow-state-dev/pull/3594)), fired until a pass clears it, after a crash too. The deadline belongs to the coordinator's round, not to a delegate's run, which a routed task's `work` entry no longer special-cases |
| **Locks in** | A round's deadline is due time on the coordinator session's wake, cleared when every round is closed. This issue therefore lands after FIX-2078, as the epic already orders. `roundDeadline` stays the internal entry the wake runs |
| **Locks in** | A round's deadline is due time on a wake on the coordinator's session whose entry is `roundDeadline`, cleared when every round is closed. On a host where FIX-2078's start check finds no wake support, the round deadline keeps an in-process timer, as today, so rounds still close there, though not across a restart. This issue therefore lands after FIX-2078, as the epic already orders. `roundDeadline` stays an internal entry |

![D2: who closes a round at its deadline. A wake on the coordinator's session, chosen, beside a timer in each delegate's run. Decides it: a host restart before the deadline; the wake closes the round on time, the timer is lost. The price: one more due-time kind on the wake. Locks in that this lands after FIX-2078](figures/d2-round-wake.svg)

Expand Down Expand Up @@ -82,9 +82,14 @@ whether the lead can manage the workers under it. Then the vet keeps its own cal
pending in the user's list and cancellable there. The cost, from rules 5, 6 and 9 together: a
delegate waiting on work it filed holds later messages to it until that work ends. A waiting
task whose round has closed is still worked; its answer lands once, late, as today.
- **A routed turn is a task turn.** The `taskTurn: false` stopgap goes; the delegate may file work
and wait on it (rule 9), and its task stays open until that work ends (rule 6, FIX-2077). The
coordinator never waits on a routed task (FIX-2082's refusal).
- **A routed turn is a task turn.** The `taskTurn: false` stopgap goes; the delegate may file work,
and its task stays open until that work ends (rule 6, FIX-2077). Until FIX-2082 lifts the
task-turn wait refusal, a routed delegate files work and ends its turn, and rule 6 keeps its task
open; from FIX-2082 on it may also wait on that work (rule 9). The coordinator never waits on a
routed task (FIX-2082's refusal).
- **Routing never picks the coordinator itself.** Its candidates exclude the coordinator, whatever
its delegate list says, so no routed task lands on its own plan ledger. Best fit's self-pick
stays what it is today: the coordinator answers, and nothing is filed.
- **Endings.** One entry, `onTaskSettled`, through FIX-2078's path. A conversation-result ending
lands as a line under the delegate's name and feeds the rounds; nothing wakes a judgment turn
for it. A failure's error report rides it ([(f)](../../epics/FIX-2056/DECISIONS.md#f)).
Expand All @@ -101,11 +106,20 @@ whether the lead can manage the workers under it. Then the vet keeps its own cal
posts, and builds no read of its own (ER-6).
- **`dispatchTask`.** This issue removes its post form; if FIX-2082 has landed, the tool and its
action too (FIX-2081 D1).
Comment thread
jhoffner marked this conversation as resolved.
Resolved
- **Changeset lines**, removed outright under [(e)](../../epics/FIX-2056/DECISIONS.md#e):
`DELEGATED_POST_ENTRY`, `delegatedPostEntry`, `delegatedPostHistory`, `delegatedPostOnFinished`
and `delegatedPostSchema` (a delegate declares `work` only); `dispatchTask({ post, target })`
(`createTask` with the routing settings); `taskLedgers({ taskTurn })` (nothing). The epic's
`migration.md` names only the first; the others ride its row.
- **Changeset lines**, removed outright under [(e)](../../epics/FIX-2056/DECISIONS.md#e), each a
row in the epic's [`migration.md`](../../epics/FIX-2056/migration.md):
`DELEGATED_POST_ENTRY`, `delegatedPostEntry`, `delegatedPostHistory`, `delegatedPostOnFinished`,
`delegatedPostSchema` and `DelegatedPost` (a delegate declares `work` only);
`taskLedgers({ taskTurn })` (nothing); `defineCoordinatorFlow`'s `delegateFlows`,
`defineSessionBoard`'s `postFlows` and `posts`, and `posts`/`both` in `listDelegates`' takes
(a delegate is a worker whose flow takes tasks; FIX-2084's role check is the one answer). The
implementation's sweep checks they are gone. `dispatchTask({ post, target })` has no row of its
own: it is FIX-2081's `dispatchTask` row, whose routed-task line reads `createTask` with
`target` and the routing settings; whichever of #3596 and this PR merges second writes that.
- **The collection's dispatch verb.** If this lands after FIX-2082, it removes
`TaskCollectionRef.dispatch`, `TaskDispatchOptions`, `Task.dispatchCall` and the
`already-dispatched` decline with the tool, under the same row. If FIX-2082 lands later, it
does.
- **No POC and no checker.** The premises are read from code at `96404d25`, and no claim here
rests on a count.

Expand Down Expand Up @@ -138,8 +152,10 @@ Recorded for the implementer, not baked into the design. Round 1, on `48372389`.
`onPostSettled` or `postCancelled` in `packages/` or `apps/`, leaving `workerTaskEntry` and
`conversation-board/task-entry.ts` as the only entry and ending pair (`task-settled.ts`,
`notice-delivery.ts`, `board.ts`).
- **Merge order** (second look): this lands after FIX-2078, FIX-2080 and FIX-2081 merge (the
blocked-by relations); D2 rests on FIX-2078's sweeper-kept wake.
- **Merge order** (second look, cross-spec audit): this lands after FIX-2077, FIX-2078, FIX-2080
and FIX-2081 merge (the blocked-by relations); D2 rests on FIX-2078's sweeper-kept wake, and a
routed task stays open while its filed work runs only under FIX-2077's rule 6. No edge from
FIX-2082: the interim under *A routed turn is a task turn* covers either order.
- **D3 can be its own PR** (Cursor, second look): it shares no code path with the post removal.
It stays in this issue because the epic puts *one fit check* here
([SPEC](../../epics/FIX-2056/SPEC.md), set and debt); the implementer may land it separately.
Expand Down
Loading
Loading