No seat is spawned without a verification line
Why the fleet missed the bar: under-specified acceptance (spec, ~60%) plus silent substitution and receipts-instead-of-URLs (execution, ~40%). The rule that came out of it gates every spawn since.
The decision
plan/decisions.json, verbatimUnder-specified acceptance (3 of 50 modules had a verification line) + Shaan's standards installed only for Claude + peer traffic on the one UI seat = spec (~60%); silent substitution and receipts-instead-of-URLs = execution (~40%). Rule from now: no seat is spawned for a module without a one-line 'you will open X and see Y' verification, and the ui-bank/console/atlas skills go into the Codex home before the next Astra wave.
His words that caused it
was that a speccing problem on our end, or was that an execution problem on their end?Shaan → REVIEW-ZERO · 6 Sep 14:30
What it changed
files, modules, plays it gates- 1Every module row carries a verification line landedplan/modules.json: 51 rows, each 'open X and see Y' (before: 3 of 50)
- 2Every brief carries a done-when landedbriefs/TEMPLATE-BANK-ZERO.md: one done-when line per family; the gallery detail pages show it
- 3ui-bank / console / atlas skills into the Codex home leftbefore the next Astra wave (P3 second half; absent from ~/.codex/skills on both machines at 15:19)
- 4atlas/SPEC-OR-EXECUTION-2026-09-06.html landedthe reading page behind the ratio
What reverses it
Shaan saying so. Or evidence that seats with a verification line miss the bar at the same rate as those without (the ratio is REVIEW-ZERO's reading of 12 closed seats, not a measurement).
Mind map
→ modules, projects, plays it gatesEach leaf links to its record. Branches are laid out by subtree size, not by hand.
Decided · reaffirmed · applied
Agent entry
jq '.decisions[]|select(.id=="D-25")' 00_AGENT_ZERO/plan/decisions.json
- Read first
00_AGENT_ZERO/plan/decisions.json- Owner
- AGENT-ZERO
- Done when
- Open this page and see the D-25 call verbatim, the 14:30 words that caused it, and the modules it gates.