closed-loop

1# Closed-loop execute (V-model right arm)
2 
3Mechanical verification pipeline. Every verify step emits **evidence rows** tied to acceptance criterion IDs (`AC-n`).
4 
5## When to use
6 
7The harness is opt-in. Run it when:
8 
9- Invoked as `/closed-loop <task>` or `/closed-loop <spec-path>`.
10- The user asks for the closed loop, proper verification, or an evidence trail.
11- `verification_harness: on` in `00-inbox/MY-PROFILE.md` and this is a build task.
12- Another skill that declares a `normal`+ lane reaches its verify step.
13 
14Do **not** run it on a request that did not ask for it. Notes, briefs, research, drafts, and ordinary edits are not harness runs, and a checkpoint ledger on those is pure overhead.
15 
16## Phase 0 — Lane + run folder
17 
18```bash
19bash .claude/lib/lane-classify.sh explain "<task>"
20bash .claude/lib/checkpoint.sh init 04-projects/harness/runs/<YYYY-MM-DD-HHmm>
21```
22 
23| Lane | Checkpoints |
24|---|---|
25| `tiny` | CP-3 → CP-5 (if mutating) |
26| `normal` | CP-1 → CP-2 → CP-3 → CP-3v → CP-5 |
27| `full` | + CP-4 + claim-verifier + CP-6 |
28| `bug` | root-cause ledger (CP-0) before CP-3 |
29 
30Record: `checkpoint.sh record <run-dir> CP-0 PASS|SKIP "<lane>"`
31 
32## Phase 1 — CP-1 Spec (acceptance criteria)
33 
34If spec exists, use its `## Acceptance criteria` + traceability matrix. Else write:
35 
36`04-projects/harness/runs/<id>/criteria.md` using `references/spec-template.md` (criteria + matrix sections only).
37 
38Each criterion: **falsifiable** + `AC-n` ID + verify method.
39…