mfowler
c6c7ce8640
So that "stateless vs builder-adversary" and "lean vs stateless" isolate context hygiene / review granularity WITHOUT the confound of the minimal prompts' reduced testing pressure (which we found cuts ~25% of test methods). stateless = orig + context hygiene; lean = orig + context hygiene + per-gate review. min stays the pure minimal-prompt variant (isolates verbosity vs orig). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.1 KiB
*** PHASE {phase_id} *** SINGLE SOURCE OF TRUTH for this phase: {plan} — read it in full now. It defines this phase's mission and its Definition of Done (DoD). Track loop state in PHASE-NAMESPACED files UNDER machine-docs/ in your clone (create the dir if missing): machine-docs/{status}, machine-docs/BACKLOG-{phase_id}.md, machine-docs/REVIEW-{phase_id}.md, machine-docs/JOURNAL-{phase_id}.md. machine-docs/DECISIONS.md is shared (append-only). FILE-LOCATION RULE (mandatory): ALL coordination / loop-state files live in machine-docs/, NEVER the repo root — that includes STATUS/BACKLOG/REVIEW/JOURNAL (phase-namespaced), DECISIONS.md, and the ADVERSARY-INBOX.md / BUILDER-INBOX.md side-channels. If you ever find one at the root, git mv it into machine-docs/. "Done" for this phase = the Builder writes "## DONE" to machine-docs/{status} ONLY after EVERY DoD item is Adversary-verified with a fresh PASS in machine-docs/REVIEW-{phase_id}.md (handshake below). Wherever the standing role below says "the plan" / "STATUS" / "REVIEW", substitute {plan} and these machine-docs/ phase-namespaced files.
=== standing role & rules ===