Files

T

Jon Chery b054849a99 docs(P4): metrics catalog + NORTH_STAR integration + trust snapshot + no-humans thesis (REQ-186,191..195,204,210..213)

P4 (Wave 3, docs) — REQ-186, 191, 192, 193, 194, 195, 204, 210, 211, 212, 213

New docs:
- docs/METRICS.md — canonical KPI catalog (grounded/derived/deferred)
- docs/metrics/*.md — 13 per-KPI definition-of-success docs (D-127)
- docs/METRICS_DEFERRED_ROADMAP.md — 8 deferred metrics + hot-path plan + re-eval triggers (REQ-210)
- docs/NO_HUMANS_THESIS.md — thesis defensibility brief (REQ-213)

New tools:
- core/metrics/trust_snapshot.py — 5 trust metrics + chain-integrity verdict + snapshot hash (REQ-211)
- scripts/check_north_star_diff.sh — CI check for NORTH_STAR strategic section changes (REQ-204)

Modified:
- .ciagent/config.json — strategic_direction_file: .ciagent/NORTH_STAR.md (REQ-186)

---ci---
project: acdl
phase: 4
milestone: v1.17
status: execute
---/ci---

2026-08-04 20:05:06 +00:00

646 B

Raw Blame History

Confidence-Gate Halt Rate — Definition of Success

KPI: Confidence-Gate Halt Rate Target: not a committed target (operational signal)

What this number means: how often the confidence gate itself halted a run (band = block), independent of HITL blocks. The gate is the AI's self-halt; HITL is the human gate. This distinguishes the AI's self-regulation from human escalation.

How it's computed: count(runs WHERE confidence_band = 'block') ÷ total runs.

What "good" looks like: a low but non-zero rate means the gate is working (catching genuinely uncertain runs) without being overly conservative (blocking everything).

646 B Raw Blame History

Confidence-Gate Halt Rate — Definition of Success

646 B

Raw Blame History