← all features · evolve-loop explainers

Quality gates

EGPS predicates, coverage graduation, adversarial audit — the machinery that makes PASS mean something.

How it works today

EGPS: red_count==0 to ship. One increment point (acssuite.go:173-183); PASS ⟺ RedCount==0 with skips counting neither way; flaky single-retry absorb (cycle-468). Cycle predicates live in go/acs/cycle*/ + regression + red-team corpora.
Compiled-enforce defaults: eval_gate and contract_gate are StageEnforce in code (config.go:510, policy.go:1188-1189) — policy.json may override but the checked-in file doesn’t. TriageCap/TopN/PhaseIO gates are also compiled-enforce.
Adversarial audit: default-on framing "treat the build as guilty until proven innocent" (subagent/run.go:402); auditor defaults to the deep tier cross-family from the builder; confidence < 0.85 → WARN.
apicover graduation guard: go/.apicover-enforce lists packages at public-API DoD (0 uncovered exports, ≥85% tagged coverage, godoc, <800 LOC files). Two audit gates read it — enforce-changed and new-package graduation (phases/audit/ciparity.go:259-288): a new go/internal/* package absent from the list FAILS the cycle until enrolled.
CI parity (ADR-0069): the cycle audit runs the EXACT repo-wide CI commands (vet, tagged ACS suite, apicover-enforce) against the worktree — killing the recurring "per-cycle proof ≠ repo-wide CI" disease.

The gate that kept failing a lane — fleet-lane-provisioning-split failed 4× on the new-package graduation guard: the gate worked exactly as designed; the task’s acceptance criteria never told the builder to enroll internal/lanescope. The recurrence ledger (queued) exists for precisely this: repair the item, don’t re-dispatch it blind.

How it got built

ADR-0025→0042 (bash suite → Go predicate schema), v10 removed the WARN level, ADR-0050 phase-5 graduation (35 packages enrolled 2026-06-16), ADR-0069 after cycles 516-522 shipped green locally while repo CI was red.

Generated by /evo:explain · verified against code 2026-07-13 (file:line citations) · doc drift found during verification is queued in .evolve/inbox (docs-code-alignment-2026-07 campaign).