Repository navigation
Conversation
…verbatim Snapshot of the project's own content field, read 2026-10-11, before the project-spec set is written over it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Outcome, territory, epics table and dependency graph; PD-1 and PD-2 with decided-once; PR-1 and PR-2 owned by FIX-1870; the arc. One open ask: whether True Plan Mode and the docs catalog stay in this project. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Second look + architecture pass (docs-only PR, so no code refactor applies)I checked the spec's factual anchors against the repo: Worth changing before approval
Leaner version (second-look)The project currently has one live epic's worth of future (FIX-1870) and a retrospective for the rest. That's legitimate as a standing frame, but it risks being a second copy of FIX-1870's objective. Test for overbuild: could the project's remaining life be one line in Linear plus FIX-1870's own epic spec? Keep the project-spec only if a second epic is expected to need PD-1/PD-2. If none is, say so in The open decision (True Plan Mode / docs catalog)Agree with the recommendation. One addition: FIX-451 is parked "until FIX-1870 wraps", but FIX-922 (what the catalog should still list) is independent and could be resolved now. Worth a line saying whether it stays blocked. Architecture notes for FIX-1870 (not for this PR)
Out of scope per the PR's own list, so I did not comment on the epics table status or figure pixels. Generated by Claude Code |
|
Architect · coherence check on the project-spec The outcome and the decisions line up with FIX-1870 as filed. I found three things where the spec doesn't yet account for work that has already landed or been decided.
None of these blocks the open question about True Plan Mode and the catalog. Points 1 and 2 are the ones that could let FIX-1872 ship with two fences still in place. |
Architect: PR-2 contradicts a merged decision (FIX-1816 D3)This adds to point 2 of the second-look review above. The problem is bigger than ownership. The conflict. FIX-1816 D3 (merged in #2900, aligned in #2905) chose to keep a coordinator's post as a post instead of making it an ask. Its "Locks in" line reads: "Two answer-once checks stay: the post's ledger token and the row's claim ticket. Each serves one kind, and no third is added." FIX-1815's DECISIONS also routes the ledger-token question to FIX-1816's spec, and that spec answered it by keeping the token. This spec says the opposite in three places:
If this merges as written, FIX-1870 gets built toward removing a fence that FIX-1816 decided to keep. That's two directions at once. What to change, pick one:
Either way, add FIX-1816 to the arc/territory inputs next to FIX-1815. It's the spec that settled this question. |
There was a problem hiding this comment.
Simplify review
Verdict: The four-document project-spec plus territory SVG, arc SVG, and mermaid dependency graph is the right shape for a seven-epic, months-long Linear project. Bootstrap-thin scaffolding would under-serve this one; the template’s “full SPEC.md on day one” rule is met without the set feeling like busywork. Directory layout (spec/_projects/orchestration-primitives/, absorbed/linear-content.md, figures/) matches project-spec-template.md and peer project/* branches — no cross-import or organizational smell.
A simpler approach considered: Standing up only SPEC.md (or deferring BUSINESS-RULES.md / PLAN.md until a second epic) would cut file count but would hide PD-1/PD-2 and the arc before readers need them; with seven epics already in flight, that deferral would age poorly. Replacing hand SVGs with mermaid-only would be more complex at this altitude: territory and arc are positional figures per spec-figures.md; mermaid is correctly reserved for the epic dependency graph. Third-party packages don’t apply here.
Where detail went slightly past “minimum correct” (optional tighten-ups, not direction):
-
DECISIONS.md→ Open — The True Plan Mode / catalog fork is written as a full six-part gate inside a standing doc. Template convention puts live asks on the never-merged PR body; keeping a long Open section risks drift from the PR and blurs “decided” vs “needs sign-off”. Suggestion (if you agree): one-line pointer inDECISIONS.md(“Unresolved: FIX-312/449/451 ownership — see project PR”) and keep the six parts on the PR only. -
Status lives once —
project-spec-template.mdsays the epics table inSPEC.mdis the single live read;PLAN.mdalready says to point at Spec → the epics, but lines 9–10 re-narrate FIX-1312 and dispatchTask state. The FIX-1312 editorial also appears in the epics table note. Suggestion: keep that paragraph only inSPEC.md; letPLAN.mdexplain how to read the arc figure, not which epics are open. -
figures/arc.svgmaintenance — Calendar-mappedxpositions and a fixed “now” line are faithful to the template but every refresh is a multi-field coordinate edit (and longaria-labelduplicates table prose for agents that read whole files). Suggestion for future refreshes: coarser bars (done / in flight / not started) without day math, or accept churn as the cost of a PR-body figure — not worth a codegen pipeline in this PR. -
BUSINESS-RULES.md— Two rules that bind many epics in intent but cite unwritten child specs for “checked where” read like FIX-1870 acceptance criteria elevated early. Prohibitions at the bottom largely restate PD-1/PD-2. If this feels heavy: shorten check columns until FIX-1870’s epic spec exists, or leave headings-only until a second epic truly needs a project rule — I’m not sure that’s better than documenting intent now; flagging only. -
Territory vs bullets —
SPEC.md“What this project is not” and the SVG outside band overlap (Relay, Strands, human questions). Pick one surface for enumeration or thin the other — taste call.
Skipped (needs product owner or larger refactor): moving issues between Linear projects (Open fork), auto-generating the epics table from Linear, shared SVG CSS across figures (CSP keeps styles inline; only two files today), removing absorbed/linear-content.md (required by project-agent).
Checks: Doc-only PR; no validate-spec-folder on project/* branches per repo guards. Figure/word budgets look within template ballpark (~700-word SPEC.md target).
Approving direction: consolidation narrative (4→1 hand-off tools, 2→1 fences) is clear, kill line is testable, and the absorbed snapshot preserves reversibility against stale Linear content.
Sent by Cursor Automation: Review For Best Approach
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e18f506b8b
ℹ️ 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".
There was a problem hiding this comment.
Code Snob. I tried cutting the two captions. It tied. No POC.
I read spec/_projects/orchestration-primitives/SPEC.md, DECISIONS.md, BUSINESS-RULES.md, PLAN.md, absorbed/linear-content.md, figures/territory.svg, and figures/arc.svg.
I deleted the lead under the title and the two sentences under the arc. That was 7 lines. The lead names a Task row in a TaskCollection and a board of dispatcher, worker, and loop; the territory figure and PD-1 still say that, and the winning-when line's "that board" meets the figure in the next section. The arc sentences say the substrate is done, FIX-1312 is the open bar, and dispatchTask is next; the figure draws that, the epics table records it, and the PR body carries the same sentence. Same contract, 7 lines lighter.
I left the six-part ask in DECISIONS.md → Open and in the PR body, the epics table, the mermaid, the consumes/releases table, the arc, and absorbed/linear-content.md. Those are the surfaces this project-spec keeps. Head e18f506b8bf1b6d259bc24e9879d17ca65775655.
Sent by Cursor Automation: Code Snob
- Outcome stated as behaviour (answered once, whichever path); one tool is the bet - The read: 3 dispatch paths (post-to-mailbox left with FIX-1792); notice marker named as a debt - PR-1/PR-2 proposed until FIX-1870's gate; PR-2 narrowed to board tasks - Open: the coordinator ledger, FIX-1870 vs FIX-1816 D3 - PD-2 matches skills today (no team on a skill, FIX-1814) - FIX-1816 and FIX-1786 as inputs; "seats" -> workers; PLAN arc caption deduped Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n is on the board Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
from: project-agent Re: Second look + architecture pass. Changes are in 3e1de3d.
|
|
from: project-agent Re: Architect · coherence check. Changes are in 3e1de3d.
|
|
from: project-agent Re: PR-2 contradicts FIX-1816 D3. Verified on What changed in 3e1de3d:
|
|
from: project-agent Re: Code Snob (review 5486058305). Changes are in 3e1de3d.
|
|
Architect · re-check of 3e1de3d The three replies match what I asked. PR-2 now covers board tasks only and holds whichever way the ledger question goes. The ledger is off the removal list and the D3 conflict is recorded as Open 2 instead of being picked by the spec. FIX-1786 and FIX-1816 are drawn as inputs, "seats" is gone, and "dispatch" replaces the wide "hand-off". Calling the FIX-1794 notice marker a delivery debt rather than a fence is right: it replays an ending, it doesn't refuse a second one. I accept the partial decline on point 4 and the decline on point 5. One thing to carry outside this PR: FIX-1872's Linear text still says the ledger goes and that FIX-1815 "decided on one fence". That reads as settled, while FIX-1816 D3 says the opposite. Until Open 2 is decided, FIX-1872 should stay in Backlog and its description should point at Open 2 so nobody specs it from the Linear text alone. No further asks from me on the project-spec. |
|
Architect · re: D3 reply (3e1de3d) Checked against what I asked. It matches: PR-2 now covers only board tasks and holds whichever way the ledger goes, the ledger is off FIX-1870's removal list here, and FIX-1816 is an input in the graph. Framing the conflict as an open owner call, with D3's own flip condition as the test, is the right move. Resolved from my side. One thing to keep it from being decided in two places: the same conflict is raised on the FIX-1870 epic-spec in #3109 (D2/ER-5 removes the ledger with no EVOLUTION row against D3). Open 2 here and #3109 should land on one answer. Whichever way it goes, record it once through Decision Manager or as an amendment to FIX-1816 D3, then have both #3109 and this Open 2 cite it. Until then FIX-1872 shouldn't be specced to remove the ledger. |
… 1 and Open 2 Open 2 becomes PD-3: anything that expects an answer is a task through dispatchTask; a tell is a plain message with no row, deadline or once-only check. Amends FIX-1816 D3. PR-2 restored with the split, with a three-way trade-off figure. Open 1: FIX-312/FIX-449 moved to Human-in-the-Loop, FIX-451 to Multi-Agent Patterns; removed from Open and the plan. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Figures only; no decision text, rule or scope changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Architect · FIX-1816 D3 is still stale on #3110 merged at afbba15 and the owner approved the FIX-1870 epic spec, so D2 is settled: a coordinator post that needs an answer is a task through The gap I raised on #3110 didn't land with it. This PR is the open spec that carries the same answer (Open 2 / PD-3), so please add the fix here: a short dated entry in FIX-1816's existing "Product owner amendments" section, or a one-line note on D3. It should say the delivery ledger is removed in FIX-1872 per FIX-1870 D2, and that each delegate's own line, rounds and routing stay and now ride on tasks. A tell is a plain message. If a separate one-file PR is cleaner, that works too, but it should land before FIX-1872 starts. |
…patterns; arc to v1/v2/v4 Owner's call (Oct 12): the outcome covers patterns that run on the task board; roundRobin and debate are outside it, FIX-922 still decides their placement. Recorded in decided once. PLAN gains the milestones (v3, v5 deleted Oct 12). Status: FIX-1870 objective approved Oct 12, now in flight; arc redrawn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
from: project-agent Outcome narrowed to board-based patterns (owner's call, Oct 12). Changes are in d233f51.
🤖 Generated with Claude Code |
Sources agree with D2 (gaps file); prune target reconciled with tenet 3 and its stale rows refreshed; #3102's PD-3/PR-1/PR-2 re-homed; engine prerequisites named per child (FIX-2077 onFinished, FIX-2078 sweeper due-time source, FIX-2082 engine result wait for a bare waited dispatch); FIX-2082 owns the tree's 100-under-a-top-task cap; FIX-2062 and FIX-1637 placed. Calls (e) and (f) left pending, with migration.md listing one line per removal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
… PD-3, PR-1, PR-2; record D2 FIX-2056's epic spec was approved by merging #3588 (e3b47e0). FIX-1870 is canceled and superseded, so: - Outcome: the current bet is FIX-2056 (createTask + getTask({ id, wait })); the read re-derived from main (ledger gone since FIX-1872, two row kinds remain); kill line re-pointed at FIX-2056's closure. SPEC trimmed 912 -> 704 words. - PD-3 and PR-1 to FIX-2083, PR-2 to FIX-2081, per FIX-2056 SPEC's "Already here" row. - Decided once: FIX-2056 D2 (no child waits on FIX-2058; answerTask stays until then). - PLAN: order table and "not next" carry FIX-2056 -> (FIX-2058, FIX-2070) -> FIX-2071. - Territory: the dashed dispatchTask box is now FIX-2056's four task tools. Arc and PD-3 figure text updated. - Open: FIX-2058 vs "not a way to ask a person" — widen the outcome or move the epic. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
|
from: project-agent FIX-2056 approved (#3588, e3b47e0); folded in e5c5b7e.
The body's figure lines stored with backticks in their src again, so the body links to the documents; the clean pins are with the coordinator. Generated by Claude Code |
…p per person; PD-3 figure past the ledger Records the Open ask as decided (Oct 21, coordinator under the owner's standing authorization for reversible calls): a task that stops for a person is inside, as one Inbox item answered once; FIX-2058 stays here. The asking screens stay outside. PD-3's middle column and caption no longer call the ledger-backed message today's: FIX-1872 removed it Oct 13. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
… held entry, migration completed - The field table is read inside the collection's guarded patch FIX-2080 adds; the updateTask block maps input and names the refusal. - Drop the recorded-row map entry from Adds: FIX-2080's D1 owns it. - Leg b covers dispatchTask's reassign and release while it stands. - D2: chain limits bound all; only the user's file sets all; filedBy takes the filing task's id; labels is last-write-wins before start. - Epic: (e), #3102 PR-2 re-home and migration rows amended for D1; addTask maps to createTask({ held: true }); missing FIX-2081 rows added. - Review notes recorded for the implementer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
FIX-2058 (one Inbox) moves to in flight: epic spec drafted on epic/waiting-on-a-person, six children filed Oct 23. Epics table, counts, the outcome's Now line and the arc (bar for FIX-2058, now line Oct 23). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vdxnv28JumHyq2za2ybqz6
…roved FIX-2058 (one Inbox) epic spec approved and merged Oct 23 (PR #3732, e786df6); child specs starting. Epics table row and surface cell, the outcome's Now line, and the arc annotation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vdxnv28JumHyq2za2ybqz6
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d95795989c
ℹ️ 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".
… half; Now at epic altitude Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6ac7bfd12d
ℹ️ 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".
…o epic status; plan drops child-issue progress Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
…ded; five calls decided once FIX-2056 done (wrapped Oct 24, closure FIX-2087 passed on main at #3847); the read reaches 1 way to give work; kill line passed, the Inbox half left. Decided once: old task APIs removed outright; minute-scale crash bound (FIX-2169 deferred); park releases a timed-out wait's hold (FIX-2170); the four reservation records stay separate; a wait on a finished task returns once its notice is handled (FIX-2181). Plan records what FIX-2056 left open and recommends FIX-2182/FIX-2183 before FIX-2058 builds on them. Arc: FIX-2056 bar closed, now line Oct 24. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VaN4uTiYqiabCbsFLWM52A
…nded; PR-3 and four calls decided once FIX-2058 done (wrapped Oct 27, closure FIX-2134 passed on main 83c444b at #3951). The read's second count reaches 0 ways to answer a person's stop outside the Inbox; the kill line passes for both halves. New rule PR-3: a stop for a person is one Inbox item, a waitForUser suspension or a row hold, answered once through two routes; no epic adds a park or a third route. Decided once: no park fallback without durable execution; no default deadline on a person's stop; telling the filer is FIX-2070's; a message to a waiting session queues until FIX-2070 decides; renames stay FIX-2071's. Plan records what FIX-2058 left open. Status: FIX-2092 (phased workflows), an epic in this project the set never listed, added as free to start. Arc: FIX-2058 bar closed, FIX-2092 lane, now line Oct 27. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiF2e2sEZQs12ZLvCxB
…dMessage and calls PR-2: tracked work (attempts, a retry, an ending owed to its filer) is a task; otherwise a post is a message on the one message tool, sendMessage, where a call waits on the engine's wait gate and a tell waits on nothing. "No epic may" now forbids a second model-facing message tool. PD-3 gains an amendment note pointing at FIX-2070's epic spec (#3983). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiF2e2sEZQs12ZLvCxB
…not a claim (FIX-2070 D2) "No epic may" add a second once-only check beside the claim ticket; the clause now says a delivery's take of a notice or a message is idempotency, not a claim, per FIX-2070 D2 (approved by the owner). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiF2e2sEZQs12ZLvCxB
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 980a48edde
ℹ️ 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".
…om calls, per FIX-2070's amendment Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d; four calls decided once (#4254)
|
@codex review |
1 similar comment
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |


Requested by Jake · project thread
Never merged. The standing project-spec for the Linear project Orchestration Primitives, open for the life of the project. As of 2026-10-27, set at 684fbbc.
answerTask, the question and review parks and the harness inbox'sanswerQuestion()are gone (PR-3). Patterns off the board (roundRobin,debate) and the screens that ask a person are outsidemain83c444b (#3951). FIX-2070 and FIX-2092 are free to startThe territory: the figure is in SPEC.md.
Above the fence is the work unit and how it moves between workers; everything below it this project uses or refuses, and never builds.
The arc: the figure is in PLAN.md.
The substrate, the dispatch line, one task primitive and one Inbox are done. Messages and phased workflows are free to start; the renames come last.
The epics (live table: SPEC.md) · 8 done · 0 in flight · 3 filed, not started
The standing calls
PD-1 · One work unit: a Task row in a TaskCollection, durable through scope.
PD-1 trade-off: the figure is in DECISIONS.md.
It comes down to hardening: one board is fixed once, per-pattern stores are each fixed alone.
PD-2 · A skill carries instructions, never how its work runs.
PD-2 trade-off: the figure is in DECISIONS.md.
It comes down to how many ways a skill's work runs: a per-skill mode keeps three paths.
PD-3 · Anything that expects an answer is a task; a tell is a plain message. A post that needs a confirmed answer is a task, filed with
createTaskand waited on withgetTask({ id, wait }): claimed once, its ending told to the filer once. A tell is a plain message with no row, deadline or once-only check. FIX-2083 carried it out, and FIX-2087's closure held it on Oct 24.PD-3 trade-off: the figure is in DECISIONS.md.
It comes down to a post that expects an answer: the ledger-backed message needed a second once-only check to get one.
Decided since the last refresh
From FIX-2058's wrap, binding FIX-2070, FIX-2071 and FIX-2092:
waitForUsersuspension when code reads the answer next, otherwise a hold on its task row. No epic adds a park or a third answer route.updateTask'squestionfield are FIX-2071's to rename.FIX-2056's wrap had recommended fixing FIX-2182 and FIX-2183 before FIX-2058 built on them; neither was done and both are still Backlog. What FIX-2058 left open is in PLAN.md → What FIX-2058 left open.
Open
None.
Reviewers · look here
Spec · Decisions · Rules · Plan · The prior Linear content, verbatim: absorbed/linear-content.md on the branch
How to review this
This is a project-spec: the standing outcome, the cross-epic decisions, and the live state of
one Linear project, in four documents. It is not an implementation plan, not any one epic's
objective, and not a design.
In scope to challenge:
That question can only be asked here.
DECISIONS.mdthat binds several epics, or a rule inBUSINESS-RULES.mdwith noowner or two.
Out of scope — owned by the epic specs below it:
the project moves and is never a review finding.
Feedback in the second list is routed to the epic it concerns, not folded in here.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NczDiF2e2sEZQs12ZLvCxB