Success and proof
This page shows what the reader gets at the end: inspectable artifacts, closure markers, or an honest handoff.
Done means audited, not stopped
AUDIT_VERIFY per-phase status, deliverable existence, and trusted or rerun evidence reviewedAUDIT_COMPLETE every in-scope item has final checkable evidenceIMPLEMENTAUDIT_RUN_COMPLETE valid only after AUDIT_COMPLETEAUDIT_HANDOFF not complete: blocker and next owner action are namedOpen the files. Check the markers.
A work record you can inspect
Phased or larger work uses a run folder with plan, phase checklists, state, and evidence. Compact work may not have a run folder; locate its bound work record through the final response, final audit ledger, cited artifacts, and marker order.
Formal:planning + run trackingL1-L2
work record / run rootArtifact:roadmap
phase specsSTATE.md when a run folder is used
Before/after checks
Each phase records the baseline before edits and compares the result after edits.
Formal:phase check loopL3Smoke A/BArtifact:before/after evidence
A failure log, not hidden retries
When evidence fails, the log records class, cause, countermeasure, rerun evidence, escalation or handoff reason, and outcome.
Formal:failure interruptL4AndonArtifact:Andon log
A final audit ledger, not vibes-based done
The review artifact collects closure status, transcript markers, and evidence references so reviewers can inspect the run.
Formal:final fix-and-verify loopL5audit-fixArtifact:closure record
(final audit ledger)
Reviewer checklist
- Open the bound work record; for compact work, use the final response, final audit ledger, cited artifacts, and marker order; for phased work, the run folder exists and can be opened.
STATE.mdrecords phase state and closure state when a run folder is used.- Before/after evidence exists for edited scope.
- Failures, if any, have a recorded stop, cause, countermeasure, rerun, escalation, or handoff.
AUDIT_COMPLETEappears beforeIMPLEMENTAUDIT_RUN_COMPLETE. If blocked, an honest handoff names the blocker instead.