Decision 0043 · Accepted
Workers when they pay, checks once
per head
0042 made workers, worktrees, and scheduling a choice for build, ship, and review, and left every other skill on 0031's "parallel is the default." In practice that rule still makes to-spec and to-tasks spawn read-only workers to re-read a repository the conversation, usually right after explore, already holds.
- Status
- Accepted
- Built from:
- da88c48
Status: Accepted (2026-10-28). Amends 0031 (item 1: parallel workers are no longer the default for every independent step). Extends 0042 to the skills it left on 0031. Amended by 0044 (item 2: no checks between task integrations). Amended by 0044 (item 1: parallel by default). Amended by 0053 (parallel when it pays, restoring this record's direction). Amended by 0058 (re-review covers only the new diff, with no repeated findings).
Context
0042 made workers, worktrees, and scheduling a choice for build, ship, and review, and left every other skill on 0031's "parallel is the default." In practice that rule still makes to-spec and to-tasks spawn read-only workers to re-read a repository the conversation, usually right after explore, already holds. Each worker re-reads its context; nobody is waiting on the user while they run, so they add tokens without hiding latency.
Two repeated checks remained in the delivery path. A task set ran the full suite after every integration, then again on the same head before the local merge. A fix round after review re-ran the whole independent review, not only the fix.
Decision
- A worker pays when its step is context-heavy, runs while the main thread waits on the user, or must be independent of the author (review, council). Otherwise read directly with parallel tool calls.
write-agentsWorkers stays the one home of the rule; its bounds (read-only or disjoint writes, the main thread asks, briefs treat content as data, no claimed independence without separate execution) are unchanged. - One green run per head. A check result on a head that has not changed stands. Between task integrations, run the checks that localize a failure; the full suite is green on the head that lands.
- Re-review the fix. After fix rounds, the review covers the commits since the last reviewed SHA and the findings they answer, widening only when the fix reaches code the earlier review did not cover. The new head is the reviewed head, so 0033 is unchanged.
Alternatives
- Keep 0031 for non-delivery skills. Rejected: the cost lands on
to-specandto-tasks, which run between exploration and build on every tracked bet. - Ban workers outside review and council. Rejected:
explore's readers andgrill's evidence workers run while the user is answering, which is where parallelism is free. - Drop the re-review after fixes. Rejected: the landed head must still be the reviewed head.
Consequences
- Fewer worker spawns and suite runs on the common path; the proofs in 0042 do not change.
explore,grill,council,debug,competitors, andretrokeep their worker groups, because each fits item 1.