Skip to content

spec(FIX-2083): Routed tasks replace posts: a coordinator hands a user's message to a delegate by filing a task - #3598

Merged
jhoffner merged 8 commits into
mainfrom
spec/FIX-2083
Oct 21, 2026
Merged

jhoffner merged 8 commits into
mainfrom
spec/FIX-2083

Conversation

@jhoffner

@jhoffner jhoffner commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator
Someone who… Today After
sends a message that a coordinator routes It becomes a post. She can cancel it and do nothing else. A crash during the answer ends it with no answer It is a usual task in her list: the delegate's ongoing session, result to this conversation, one try
asks a delegate that gives part of the job to a different worker She gets the first reply. The result of the other work goes to the delegate's session, not to her She gets one answer, under the delegate's name, after the other work is complete
sends a second message while the delegate still works The two run at the same time in the delegate's session The second waits. It starts in the same session when the first ends
uses rounds on a host that restarts A round after its deadline closes only when a different event wakes the conversation It closes in seconds after its deadline, also after a restart
maintains the framework A post row kind, its own entry, an ending entry, a cancel action, a stopgap, and two fit calls One task, one entry, one ending path, and one fit check

Goal: every message that a coordinator routes becomes a task that its user can see and cancel. The task runs in the delegate's ongoing session. Its one complete answer lands in her conversation under the delegate's name. No part of the framework writes or works a post; a post row stored before the upgrade is read only through FIX-2080's map, until FIX-2071.

flowchart LR
  A["a Workforce app · real engine · durable store · scripted delegates"] --> L1["leg a · everyone and best fit"]
  A --> L2["leg b · rounds · host killed past a deadline"]
  A --> L3["leg c · a delegate files work and ends"]
  A --> L4["leg d · judgment and a workstream"]
  A --> L5["leg e · a post row stored before upgrade"]
  L1 --> T["what Alice sees · her task list and her conversation"]
  L2 --> T
  L3 --> T
  L4 --> T
  L5 --> T
  T -->|"each answer once · complete · on time"| P["PASS · goal met"]
  C["control · round deadline on an in-process timer"] -.-> L2
  L2 -.->|"under the control"| F["must FAIL · round still open"]
Loading

The check reads Alice's task list and her conversation. It does not read the coordinator's calls. Check: goals/coordinators/routes-each-message-as-a-task/, no model. Control: GOAL_CONTROL=round-timer must FAIL leg b. Today's main must FAIL leg c. The coordinator goal and the FIX-2005 hand-off leg must also pass. Why this goal: SPEC.md.

Today against after: the post row, its own entry, its deadline timer, its ending entry and two fit calls are removed; a task with three settings, the work entry, a wake on the coordinator, the one ending path and one fit check replace them

The six parts of a post go. The settings of a task, its one entry and its one ending path do the job.

How: routing files a usual task with three settings from FIX-2080. The delegate works it on work. The ending comes back on the one path from FIX-2078 and lands under the delegate's name.

Sign off

The goal, at that size. If wrong: FIX-2084 builds the worker contract on an entry that must go.

The debt: net down. Posts and their six parts go. target on createTask and one due time arrive. If wrong: createTask keeps a field that only coordinators use.

A judgment coordinator files with createTask and the routing settings; the delegate reads the user's words as written · D1

<img src="https://raw.githubusercontent.com/fixpoint-labs/flow-state-dev/48372389c1e022b2effee8ac3f6acf03d50224c0/specs/issues/FIX-2083/figures/d1-createtask-as-written.svg" width="940" alt="D1: createTask with the message attached, chosen, beside a post flag on createTask. Decides it: one shape of the tool against two. Price: a target field and an attached message" />

It comes down to the shape of the tool: a flag makes two shapes of createTask. If wrong: a field and an attached message on createTask that only coordinators use. This is the one to weigh.

The deadline of a round is a wake on the coordinator's session · D2

D2: a wake on the coordinator, chosen, beside a timer in each delegate's run. Decides it: a restart before the deadline. Price: one more due-time kind

It comes down to a restart: the wake closes the round on time, and the timer stops with the process. If wrong: one more due-time kind for the sweeper.

One fit check; it refuses a lead only when it says "none fits" · D3

D3: one fit check, chosen, beside two calls. Decides it: two verdicts on one worker. Price: a borderline lead can change verdict

It comes down to agreement: two calls can give one worker two verdicts. If wrong: a lead that opens today is refused, or the opposite.

Open: none. D1 is the one to weigh. Reasons and what lost: DECISIONS.md.

Reviewers · look here

  • Spec → people, row 3. Rule 5 makes a second message to a busy delegate wait. Today it runs at the same time. Is this cost correct for best fit's hold?
  • Decisions → D1. Is an attached message, with the goal of the model next to it, better than a post flag on createTask?
  • Decisions → decided, not asked. A routed turn is a task turn, so the answer waits for the work that the delegate filed. Does a coordinator need the early reply?

Not here: steer (FIX-2086), the names respond and dispatch (FIX-2084), messages to a coordinator (FIX-2070).

Spec · Decisions · Linear FIX-2083 · epic FIX-2056 · builds on FIX-2078 (#3594), FIX-2080 (#3595), FIX-2081 (#3596) · supersedes FIX-1872 D1 · merges after human approval and required checks, per Merging and amending a spec

How to review this — altitude, what's in scope, what's deliberately unsettled

This is a direction set, not an implementation and not a build plan. Reviewing it well means
answering one question: is this the right approach?

In scope to challenge:

  • The goal and the problem framing in SPEC.md — is the goal the real need at full size,
    for the people named, or a smaller goal that would let us call this done early? Would the
    named check fail if the goal were not met?
  • The approach — will it work, does it fit the architecture and docs/philosophy.md?
  • Any numbered decision in DECISIONS.md — that's the sign-off surface.
  • The debt in SPEC.md → What's already here, and the debt — an existing primitive,
    method or prior design the change overlaps and doesn't name; something it adds that is debt
    and isn't listed; a net verdict the tables don't support.
  • A case a person would hit that the people table misses, when it would invalidate the
    design.
  • Scope — a deliverable that shouldn't ship, or one that's missing.

Out of scope — deliberately unsettled here, and owned by the implementing agent:

  • The build plan. Order, file-level changes, the test list, the PR split. The set has no
    plan on purpose: the implementer works it out against the real code.
  • Names, signatures, file paths, and module layout, beyond the few a decision locks.
  • Local structure: which helper, how a function is decomposed, error-message wording.
  • Edge cases that don't change the approach. The implementer's tests own them.
  • Documentation wording. It is written at implementation, against what shipped.
  • Micro-optimizations and style preferences.
  • The figures, at the pixel level. A figure is right when it reads right. A misplaced label
    or a colour you'd have chosen differently is not a finding; a figure that shows a shape the
    decisions don't say is.
  • POC implementation polish. Experiments under the owning spec's poc/ are retained,
    not production code. Read them for directional evidence, not production completeness.
    Their isolation from production/default discovery and absence of secrets or generated
    dependencies are in scope; retention is not permission to weaken repository checks.

One request, if you are an automated reviewer: the two lists above are the whole difference
between a useful review of this document and a long one. Volume is not signal here — a single
finding above the line is worth more than twenty below it.

Feedback in the second list is welcome and gets recorded verbatim in
DECISIONS.md → Notes from review
for the implementer to weigh against real code. It will not
be argued with, and it will not be folded into the design prose. Please don't re-raise it: one
mention is enough.

The one exception is the POC. Line-level feedback on it is dropped, not recorded — there
is nothing for an implementer to weigh about code that isn't shipping. Feedback about its
direction is not line-level and is treated like any other above-the-bar finding.

Direction approval does not waive merge-time required checks, approvals or thread policy.
Optional comments do not require another design round merely to reach zero comments.


Generated by Claude Code

````<source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right">`````````<source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewInGreptileDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewInGreptile.svg?v=2"><img alt="View in Greptile" src="https://greptile-static-assets.s3.amazonaws.com/badges/ViewInGreptile.svg?v=2" align="right">`````Confidence Score: 5/5

The spec appears safe to merge as a direction-setting change.

Summary

This spec replaces routed posts with ordinary tasks. It changes no runtime code.

  • Routed messages become tasks that return through the delegate’s session.
  • Round deadlines use a wake on the coordinator’s session.
  • Best-fit routing and lead checks share one fit check.

jhoffner explicitly accepts queued messages, possible changed verdicts for borderline leads, and the added target field and attached message. These trade-offs were not raised as defects.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  M["User message"] --> C["Coordinator"]
  C --> T["Task on delegation board"]
  T --> W["Delegate's ongoing session"]
  W --> D["Filed work ends"]
  D --> S["onTaskSettled"]
  S --> A["One answer in the user's conversation"]
  K["Durable deadline wake"] --> R["Close overdue rounds"]
Loading

Reviews (1) · Last reviewed commit: "spec(FIX-2083): routed tasks replace pos..." · Reviewed by Greptile


Generated by Claude Code

Retained spec set: a coordinator hands a user's message to a delegate by
filing a task with the routing settings; one ending path; a round's
deadline on the coordinator's wake; one fit check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
@jhoffner jhoffner added the spec label Oct 21, 2026 — with Claude
@linear-code

linear-code Bot commented Oct 21, 2026

Copy link
Copy Markdown

FIX-2083

@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 21, 2026 6:06pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 21, 2026 6:06pm UTC
flow-state-dev-ui Ignored Ignored Preview Oct 21, 2026 6:06pm UTC

Request Review

Copy link
Copy Markdown
Collaborator Author

The D1 trade-off figure did not render in the description: the stored src has backticks in it. You can see the figure here: figures/d1-createtask-as-written.svg.``

To fix the description, a person can paste this clean line under the D1 heading in place of the broken one:

<img src="```https://raw.githubusercontent.com/fixpoint-labs/flow-state-dev/48372389c1e022b2effee8ac3f6acf03d50224c0/specs/issues/FIX-2083/figures/d1-createtask-as-written.svg"``` width="940" alt="D1: createTask with the message attached, chosen, beside a post flag on createTask. Decides it: one shape of the tool against two. Price: a target field and an attached message" />

Generated by Claude Code

@jhoffner

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-21T04:45:39.361435Z 4837238 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Copy link
Copy Markdown
Collaborator Author

Second look + architecture pass (direction check, not a build review)

I read SPEC.md and DECISIONS.md and checked their premises against main (96404d25). The direction is sound: one row kind and one entry, the round deadline moved onto FIX-2078's durable wake, and the net-down debt table all hold up. The post machinery is real (coordinator/delegated-post.ts, 523 lines, with a setTimeout deadline watch at ~L337). Four findings are above the line.

1. D3 should not ride in this PR, and its mechanism isn't settled (scope)

Folding the two fit calls into one has nothing to do with posts becoming tasks. It could land before or after this change without either one noticing. It also changes behavior, and the spec doesn't say how.

  • projects/lead-fit.ts asks two questions: does the work say its sort (says) and does this one lead fit (fits). It refuses only when both are true. This is what lets a bare-name lead through.
  • Best fit's evaluator asks a different question: which of N candidates, and how confident.
  • D3 says "work that names no sort lets the open through, as today", but the one check has no says output. Nothing in the spec shows how a single pick plus none fits keeps that guarantee. Without it, a bare-name lead may start being refused.
  • The leanest option is to cut D3 into its own issue and give it its own goal leg. Fold the calls in only if one check can keep both answers. The leadFit record and lead-doesnt-fit stay as they are in the meantime.
  • If D3 stays in, "Not done if: best fit and the lead vet still make different calls" needs a leg that feeds a no-sort lead and expects it to pass. Today's legs a–e don't cover it.

2. Rule 5 queueing interacts with rounds and with rule 9, and the spec doesn't say how

The spec accepts "a second message waits" for best fit's hold. It misses two harder cases:

  • Rounds and everyone. A busy delegate's queued task can't start before the round deadline, so it always answers late. The spec says a late answer lands once and goes no further. Say what the user sees. Is a queued task for a round that already closed still worth running? Cancelling it at close would be cheaper than working it.
  • Head-of-line blocking. "The delegate may file work and wait on it (rule 9); its task stays open until that work ends." A delegate that files long work blocks every later chat message to it until that work ends. Today a chat reply is never held behind background work. Leg c checks the happy path but nothing checks this cost. Weigh "does a coordinator need the early reply?" against this blocking, and not only against the late reply. At minimum, name what Alice sees while she waits (a queued task in her list?) and that cancel works on a queued row.

3. D1: attach a reference to the message, not a copy (BP-042, restraint)

"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."

  • A row that records the full message plus recent lines is an unbounded payload stored on every task. BP-042 says a recorded return should not carry unbounded payloads.
  • The conversation already holds those lines. The delegate's turn already shows recent lines as data. The only new fact a routed task needs is which message. Store the message id on the task and let the delegate's turn resolve it from the conversation.
  • "Every task the turn files" is implicit magic. A judgment model that files a side task with resultTo: conversation gets Alice's message attached too. Say whether that is intended, or tie the attachment to the routing settings (session: ongoing and resultTo: conversation) so it isn't ambient.
  • This still keeps FIX-1872 D2 (the user's words go as written), with less on the row and no createTask input shape change.

4. In-flight posts: leg e vs. "no entry", please state the mechanism

Leg e requires "a seeded post row is worked and answered once". The same spec removes the post entry and builds "no read of its own (ER-6)". The only path is FIX-2080's map entry turning the old row into a routed task at claim time. Name that dependency explicitly. Make leg e fail if FIX-2080's map is absent, so it can't pass on something the post entry still does. Dual-read of round state and routing records naming a post id (BP-030) is stated, and good.

Dependencies (process)

FIX-2078, FIX-2080 and FIX-2081 are all still-open spec PRs (#3594–#3596), so every "builds on" claim (the map entry, the single ending path, the wake, createTask) rests on unmerged text. That is fine if this merges last. Make sure the merge order is enforced, since D2 flips if FIX-2078 lands without a sweeper-kept wake.

Architecture opportunity tied to this change

Deleting delegated-post.ts is the right moment to confirm that workerTaskEntry and conversation-board/task-entry.ts end up as the only entry/ending pair. Today they co-exist with the post pair in conversation-board/task-settled.ts, notice-delivery.ts and board.ts. Add one sweep line to the goal check: grep for no remaining reference to isPostRow, onPostSettled or postCancelled in packages/ or apps/ (the current sweep names entries and fields, not these helpers). No other refactor is worth bundling.

Housekeeping

  • The D1 figure in the PR description has stray backticks in the <img src> (already noted above in the thread). That is a description fix, not a spec fix.

Generated by Claude Code

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplify review (spec only)

Problem this spec solves: coordinators still route user messages through a parallel post row kind (its own entry, timer, cancel path, and settlement hooks) while the epic is converging on one task primitive. The direction here—routed work is an ordinary task on work with routing settings, one onTaskSettled path, and a public sweep that no longer writes posts—is aligned with FIX-2056 and reads net down on framework surface. Rejecting “drop the kind only, keep the post entry” is coherent: the entry is where the timer and taskTurn: false stopgap live.

Where complexity may be higher than necessary is mostly bundling, not the core post→task bet:

  1. Three sign-off decisions in one issue (D1 + D2 + D3). Each has its own goal leg, failure mode, and dependency (2078 for D2; prompt/schema change for D3). The epic line item already names “one fit check,” so D3 isn’t out of left field—but D3 is the strongest candidate to peel out if you want a thinner implementation PR and a cleaner direction gate: it is largely orthogonal to “nothing knows a post,” shares no code path with delegated-post.ts, and the SVG already admits borderline lead verdict drift. If you keep D3 here, I’d still tag goal legs in SPEC as core (a,c,e + sweep) vs D2 (b) vs D3 (d) so implementers know what can ship in slices without re-litigating the whole goal.

  2. D1 bundles two API expansions: server-attached user message (the real FIX-1872 D2 carry) and public target on createTask. The product fork in D1 is briefing in the coordinator’s words vs Alice’s words—not workstream addressing. Policy filing already had target on the post form; judgment + workstream might be satisfiable by reusing resolveWorkstreamTarget on the routing filing path without widening createTask in the same gate as attachment. Worth weighing at sign-off, not a definite “must split.”

  3. Two filing writers in DECISIONS (“routing’s filing step” and judgment createTask). That’s the right convergence point for FIX-2080’s guard, but the spec should make implementers reach for one internal fileRoutedTask (or extend today’s deliverTo / filePost migration) so brief assembly (recent lines × N on an everyone turn) isn’t duplicated. Performance-wise, attaching the same context per task in one turn is real amplification; “build once per routing turn, reuse across filings” is an implementation must, not spelled out today.

  4. Editorial / reader cost (minor): SPEC debt table, DECISIONS “Decided, not asked,” and per-D SVGs restate the same invariants; sign-off repeats D1–D3 “if wrong” lines. Trimming duplication would not change the design.

Reuse (implementation, not spec defects): existing deliverTo / post idempotency, workerTaskEntry + taskTurnMessage, delegate session keying from post rows, and collapsing task-settled.ts post vs task branches are the right cuts—no new packages, and patterns stays out of scope. Third-party packages don’t apply.

Verdict: I’m not requesting changes to the core approach (post→task + D2 wake tied to removing the delegate timer is justified). I’m not approving yet because I think sign-off should explicitly consider unbundling or tagging D3 and whether target must ride D1—if you confirm both belong in FIX-2083 as written, this is directionally ready to merge as a spec.

Automation: simplify pass; read-only subagent review + codebase spot-check.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread specs/issues/FIX-2083/SPEC.md Resolved
Comment thread specs/issues/FIX-2083/SPEC.md Resolved
Comment thread specs/issues/FIX-2083/SPEC.md Resolved
Comment thread specs/issues/FIX-2083/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2083/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2083/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2083/DECISIONS.md Resolved

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 48372389c1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread specs/issues/FIX-2083/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2083/SPEC.md Resolved
…the no-sort pass, queue cost named

Folds Codex's attempts and post-free-goal findings and the second look's D3
mechanism, queueing and leg-e findings; the rest recorded in Notes from review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A

Copy link
Copy Markdown
Collaborator Author

Review round 1, folded in c85f8aa

Answering the Cursor simplify review, the Codex review, and the second look above.

Folded (these change the spec):

  • Attempts 1 on every routed task (Codex P1). A judgment model that leaves maxAttempts out on a conversation-result task now gets 1, not the board default. This matches the epic's "FIX-2083 only uses it (attempts 1)".
  • Goal narrowed (Codex P2). Nothing writes or works a post. A row stored before the upgrade is read only through FIX-2080's map, until FIX-2071.
  • D3 keeps the bare-name pass (second look 1). On a lead vet the one check has three choices: the pick, none fits, and the work doesn't say its sort. It refuses only none fits. Leg d now opens a lead on no-sort work and expects it to pass.
  • The queueing cost is named (second look 2). A second message waits as a pending task in Alice's list, and she can cancel it. A delegate waiting on work it filed holds later messages to it until that work ends; that cost comes from rules 5, 6 and 9 together. A waiting task whose round has closed is still worked, and its answer lands once, late, as today. Leg a now cancels a waiting task.
  • Leg e names FIX-2080's map (second look 4). The control says leg e must FAIL with the map's post entry off.
  • The D1 figure in the description renders now.

Not folded:

  • D3 stays in this issue (Cursor and second look 1). The epic puts one fit check on FIX-2083 (its set row and its debt line), so moving it out would amend an approved epic. Notes from review says it may land as its own PR.
  • Attach a reference, not a copy (second look 3). Dropped. Today's post row already carries the same copy (delegated-post.ts, recent on the post schema), and it is bounded at 10 lines and 4,000 chars (coordinator-lines.ts). A reference would need the delegate's session to read the coordinator's conversation, which it can't today. "Every task the turn files with its result to the conversation" is intended: FIX-2080 refuses that result from anything but a conversation, so such a task is routed.
  • target stays on D1 (Cursor). Today a judgment coordinator addresses a workstream through the model's target on the post form. Without the field, that goes away.
  • Merge order, the helper sweep, building the brief once per turn, and dropping the post branch of task-settled.ts are recorded in DECISIONS.md → Notes from review.

Spec review rounds: 1 of 2.


Generated by Claude Code

…the model passes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
@jhoffner

Copy link
Copy Markdown
Collaborator Author

Architect: not approving yet. I found no fork with the sibling specs:

  • The post form leaves dispatchTask the way FIX-2081's D1 says.
  • Routed rows written before the upgrade read through FIX-2080's map.
  • The round deadline is a FIX-2078 wake.

The label waits on Jake's sign-off:

  • D1: a judgment coordinator files with createTask, the routing settings and target. This is the one to weigh.
  • D2: a round's deadline is a wake on the coordinator's session.
  • D3: one fit check, which refuses only a clear "none fits".

— FSD Architect

@jhoffner

Copy link
Copy Markdown
Collaborator Author

Sign-off (2026-10-21), all three as the spec proposes:

  • D1: accepted. A judgment coordinator files with createTask plus the routing settings and the new target field, and the delegate reads the user's words as written.
  • D2: accepted. A round's deadline is a wake on the coordinator's session.
  • D3: accepted. There is one fit check, and it refuses a lead only on a clear "none fits".

Copy link
Copy Markdown
Collaborator Author

from: fsd-claude
session: cross-spec-audit
kind: review

Cross-spec coherence audit: what FIX-2083 (#3598) needs

The owner asked for one coherence audit across all twelve FIX-2056 specs (merged FIX-2077 #3592 and open #3593–#3604), read against each other, the epic and main. 66 conflicts survived an accuracy check and a materiality check (or a tie-break); 13 of them call for an edit here. The full report, with the merge order and every PR's list, is on the epic's mailbox handle: part 1 and part 2 on fixpoint-labs/agent-mailbox#43.

One item below (F1) waits on the owner's call before anyone edits for it.

High

Medium

Low

Merge order that touches this PR


Generated by Claude Code

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

Copy link
Copy Markdown
Collaborator Author

from: fsd-claude
session: audit-fix-2083
kind: reply

Cross-spec audit edits applied in ee0f497

  • F5: the goal check row now says hands-each-post-to-its-delegates, the FIX-2005 leg and routes-a-follow-up-by-its-conversation get rewritten on routed tasks before they must pass, and one-fence-answers-each-post-once is retired into routes-each-message-as-a-task (legs a and b keep what it checked).
  • F18: D2 says the round deadline is a wake on the coordinator's session whose entry is roundDeadline.
  • F19: D2 and the six-people row: on a host with no wake support, the in-process round timer stays as it is today. The Removes row scopes the timer's removal to hosts with wakes.
  • F28: new "Decided, not asked" bullet: routing never picks the coordinator itself as a candidate. Best fit picking itself still means the coordinator answers.
  • F32: D1: target can be set only at filing, is refused on updateTask, and is refused from a filer whose delegates have no targets. The workstream session it resolves to is written by the server, top level beside session. The epic's tool-list seam row now lists target.
  • F33: D1 now cites FIX-2080's rule instead of a server stamp. Leg a expects maxAttempts: 3 to be refused at filing.
  • F38 / F57: migration.md: the DELEGATED_POST_ENTRY row is widened to the post exports, plus rows for taskLedgers({ taskTurn }) and for delegateFlows / postFlows / posts / posts-and-both. The changeset bullet no longer says "the others ride its row", and the sweep now checks these too.
  • F39: a conditional Removes line and migration row for the collection's dispatch verb, its types and the already-dispatched decline, removed by whichever of FIX-2082 and FIX-2083 lands later.
  • F43: FIX-2077 is added to the blocked-by footer, the merge note, the epic set row and the graph edge. One correction to the audit: this edge alone leaves the longest chain at four. It becomes five only together with F42's FIX-2081 to FIX-2077 edge (spec(FIX-2081): Five task tools with one rule per field, as public actions, and delegates as authority #3596), so the line now reads "five once FIX-2081 blocks FIX-2077; four until then".
  • F44: "A routed turn is a task turn" now states the interim: until FIX-2082 lands, a routed delegate files work and ends its turn.
  • F61: dispatchTask({ post, target }) now points at FIX-2081's dispatchTask row, and whichever of spec(FIX-2081): Five task tools with one rule per field, as public actions, and delegates as authority #3596 and this PR merges second writes target and the routing settings into it.
  • F1: not applied; it waits on the owner's call.

Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A

Copy link
Copy Markdown
Collaborator Author

from: fsd-claude
session: audit-fix-2083
kind: reply

F1 applied in 3d454ae (owner approved the carve-out at 17:15Z)


Generated by Claude Code

…ne into FIX-2081's dispatchTask row

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A

Copy link
Copy Markdown
Collaborator Author

Merged main now that FIX-2081's spec (#3596) has landed. What changed:

No decisions changed. validate-spec-folder passes.


Generated by Claude Code

@jhoffner

Copy link
Copy Markdown
Collaborator Author

@claude resolve conflicts

…IX-2087 specs)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A

Copy link
Copy Markdown
Collaborator Author

@claude resolve conflicts

Done. The branch now includes the latest main, which has the FIX-2076, FIX-2078, FIX-2080 and FIX-2087 specs. There were two conflicts:

  • Epic DECISIONS.md, task-tool-list seam: kept main's row, which has FIX-2080 landing first, and added FIX-2083's target on createTask back into its after-FIX-2081 list.
  • Epic SPEC.md, the line under the flow chart: kept main's start-at-once set (FIX-2076, FIX-2080, FIX-2085). FIX-2078 now waits on FIX-2080. Also kept this branch's chain length as a plain statement: the longest chain is five (FIX-2080, FIX-2081, FIX-2077, FIX-2083, FIX-2084).

migration.md merged without conflicts and still has one Changed table. In FIX-2083 DECISIONS.md, the FIX-2078 D1 citation now links to ../FIX-2078/DECISIONS.md#d1. It linked to PR #3594 before. No rulings or audit edits changed. validate-spec-folder passes.


Generated by Claude Code

@jhoffner
jhoffner merged commit a7ef882 into main Oct 21, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants