diff --git a/audit/SKILL.md b/audit/SKILL.md index d30873c..185272d 100644 --- a/audit/SKILL.md +++ b/audit/SKILL.md @@ -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 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