Brummel/Skills
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

audit: clarify clean means drift-clean, not milestone close

Browse Source 
Reword the green-exit row, annotate the carry-on commit body, and add a
red flag: an audit-clean never licenses closing a milestone — that needs
a green milestone fieldtest (gate in pipeline.md).
This commit is contained in:
Brummel
2026-05-31 12:25:27 +02:00
parent d59d3ba3be
commit 4430c46419
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
audit/SKILL.md
+11 -4
View File
@@ -70,7 +70,7 @@ The exit code of each script is the gate:
| Exit | Classification | Action |
|------|----------------|--------|
| `0` | Green | All metrics within tolerance vs. the script's baseline. Audit can close. |
| `0` | Green | All metrics within tolerance vs. the script's baseline. The cycle's drift gate is clear (drift-clean, not a milestone close — see `../docs/pipeline.md` § Milestone-close gate). |
| `1` | Drift / regression | At least one metric regressed past tolerance. Treat like a drift item. |
| `2` | Infrastructure failure | Script-output format changed, fixture missing, or harness can't spawn. **Fix the infrastructure FIRST**, re-run. Never claim a regression on exit 2. |
@@ -105,9 +105,12 @@ The orchestrator picks per item:
reason (semantic cost, intentional trade-off).
- **carry-on path:** the audit-close commit body says
`cycle <X> tidy (clean)` and ratifies whatever the
regression check drove. Audit commits always exist at cycle
close — they carry the architect findings, the regression
numbers, and the resolution.
regression check drove. Here `clean` means *drift-clean* —
the cycle's code matches the ledger; it is **not** a milestone
close, which additionally requires a green milestone fieldtest
(see `../docs/pipeline.md` § Milestone-close gate). Audit
commits always exist at cycle close — they carry the architect
findings, the regression numbers, and the resolution.
## Handoff Contract
@@ -139,6 +142,10 @@ not self-resolve.
- Treating exit code 2 as a regression to fix
- Closing a cycle with drift items in `pending` state
- "We'll re-run after the holidays" without a dated backlog issue
- Declaring a milestone closeable on the strength of an
audit-clean while the milestone fieldtest has not run green —
audit proves drift-clean, never functional (see
`../docs/pipeline.md` § Milestone-close gate)
## Cross-references