KB-170A
13 · RP Final Acceptance Criteria
2 min read Revision 1
13 · RP Final Acceptance Criteria (2026-06-05)
Final acceptance = all criteria green. Each maps to exactly one authority/operator action. Engineering contributes nothing further.
| # | Criterion | Target | Live status | Exact blocker |
|---|---|---|---|---|
| 1 | AX-PROCESS official visible | ≥1 official RP | 0/453 | PROC-OWN-01→02→03 (president) |
| 2 | AX-TRIGGER official visible | axis_registry row + owned | not in registry | AX-TRIGGER owner (Dieu-39) |
| 3 | Process×Trigger cross-check | actionable single-pane | DONE (ledger live) | — |
| 4 | job:cut official | registered first process | verified, not registered | PROC-OWN-03 |
| 5 | dot:kg verified or blocked | REAL_RUN or documented | BLOCKED multi-gate (4 GO/5 BLOCK) | PROC-OWN-04 + 4 flips + contract |
| 6 | events active or blocked | 7/7 or documented | 0/7, packet ready | PROC-OWN-05 |
| 7 | UI deployed | live page | branch ready (614b668) | operator push/PR/deploy |
| 8 | scanners active | timer active | active (next 04:10) | — |
| 9 | production dashboards green | live | green | — |
Acceptance math
- Engineering-complete criteria: 3, 8, 9 (DONE) + every "ready/blocked" item's engineering half.
- Authority/operator-gated: 1, 2, 4, 5, 6 (votes/owner) + 7 (operator deploy).
- Full acceptance requires: president votes 01–05, AX-TRIGGER owner, dot:kg config flips, UI deploy. Zero engineering work remains.
Self-check
SELECT dimension, status, note FROM v_total_final_acceptance_scorecard ORDER BY sort;