Boringoperator Wo

---
name: boringoperator-wo
description: Author a work order for a boringoperator lane (terra build or sol review) with proper context loading, per James's professional-process directive
---

# boringoperator WO authoring

Every codex WO for ~/Code/boringoperator follows this contract:

1. FIRST LINE of every prompt: "Read dev-docs/wo-context-pack.md at the repo
   root FIRST — it is binding context (mission, laws, dialect, loop, hygiene)."
   Never re-paste pack content into prompts; reference it. Add ONLY:
   - the lane's goal in one paragraph
   - verified defects/evidence (file:line, DB audit results) — never vibes
   - lane-specific constraints (files owned by other unmerged waves, migration
     number claimed after checking main AND open branches, gates that stay off)
   - the proof contract and output shape
2. Builder lanes: terra ultra, fresh worktree, npm ci first. Reviewer lanes:
   sol, high for product surfaces, xhigh when migrations/custody in scope;
   sol writes REVIEW-<LANE>.md and is the only one who touches it.
3. Fix rounds: reference the review file by name, quote nothing that the
   review already states — "read Round N in full" + clear-condition list.
4. After every lane lands: Claude live-films, records the design verdict,
   then dispatches sol. Merge order: one train at a time; capability-map
   conflicts resolve by regeneration on the merged tree; hosted migrations
   apply BEFORE app deploys that read them.
5. SIMPLICITY COUNTERWEIGHT (James, Sep 1): codex tends to overengineer.
   Every builder WO carries the context pack's "Solution style" section as
   binding; when reviewing terra's output, treat unrequested abstraction,
   knobs, layers, or breadth as findings to strip, not bonuses. Ask of every
   diff: is there a smaller true change?
6. WO IS A FILE (Sep 1): every WO lives at dev-docs/wo-<lane>.md and is
   committed to main BEFORE dispatch; "ready to dispatch" in memory alone is
   not ready (the readback-truth WO had to be re-derived from scratch).
   Evidence rows the WO cites go to dev-docs/evidence/<lane>-<date>.json.
7. EVIDENCE-FIRST DIAGNOSIS (Sep 1): before a root-cause lane, Claude pulls
   the hosted rows read-only (Management API `database/query` as postgres,
   wrapped in `begin; set transaction read only; …; commit;`; token =
   keychain "Supabase CLI" go-keyring-base64 decoded) and states in the WO
   what is VERIFIED, what is NOT a defect, and what is NOT evidence. Two of
   three checkpointed hypotheses were wrong on the readback lane; a codex
   lane dispatched on them would have chased phantoms. When live provider
   reads are needed, D0 of the lane = a read-only diagnostic script Claude
   runs with creds — codex never sees creds.
8. MERGE TRAIN READS THE WORKTREE, NOT MEMORY: migration list, conflict
   dry-run (`git merge-tree --write-tree --name-only main <branch>`), and
   the recovery drill on the MERGED chain (main's newer migrations + the
   branch's have never been applied together). Design verdict gates the
   merge alongside sol's; the merge itself is mechanical → Sonnet seat,
   Fable reviews the merge diff and pushes.
9. Zoom-out check before dispatching any lane: does this serve the mission
   (finished work, one gesture, Main Street)? Is it dollar-ranked? Is it
   class-1 (ceremony) or product-speed (no ceremony)? Would James call it
   overengineering?
7. LESSONS COMPOUND IN THE PACK (James, Sep 2): after every certification,
   distill any NEW blocker class into dev-docs/wo-context-pack.md
   "Standing lessons" (binding; builders report against it, reviewers attack
   it first). A lesson that lives only in Claude's memory never reaches a
   lane. Keep the list short; retire items that stop recurring.
8. READ RESULTS BEFORE STAMPING: assert `gh pr view --json state` == MERGED
   before any "merged" record line or worktree removal; stamps from
   `date -u`; one proof run per worktree at a time; never
   `codex exec resume --last` with parallel lanes.