Documentation
README
/retro — CP-7 close the V
Every non-tiny shipped or escalated run gets a retro. Retro is advisory but strongly expected: it is how the harness improves.
When to run
- After CP-6 ship (approved publish, merged PR, vault deliverable done)
- After escalate (capture why verifier failed)
- End of an
/ultragoalphase (one retro per phase) - Manual:
/retro <run-dir or spec path>
Phase 1 — Gather evidence bundle
Read:
- Spec or card description + acceptance criteria
04-projects/harness/runs/<id>/evidence/(ledger, checkpoints.tsv, CP-* files).claude/logs/loop-ledger.tsv(last rows for this run)04-projects/<goal>/STATUS.mdif an ultragoal phase
Phase 2 — Checkpoint audit
For each CP the lane required, mark Expected vs Actual vs Gap:
This is the opening of the README. Read the full README on GitHub.