Jon Chery
b054849a99
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---
746 B
746 B
MTTR (Platform-Run) — Definition of Success
KPI: MTTR (p95) Target: < 60 seconds
What this number means: the time from a platform-run failure (apply.failed) to a successful retry. This is platform-run MTTR, not infra-incident MTTR (which requires an incident detection system that Nova doesn't have yet — deferred).
How it's computed: p95 of successful_retry.time − failed_run.time
across all runs that failed then succeeded.
What "good" looks like: < 60 seconds means the platform recovers from a failed run in under a minute, 95% of the time.
What's deferred: infra-incident MTTR (anomaly detected → healed) requires an incident detection/remediation system (self-healing velocity). That's a future emitter.