KB-48C0
Registries-Pivot Final RP Acceptance Guide
2 min read Revision 1
Registries-Pivot — Final RP Acceptance Guide
Acceptance = the conditions under which the RP (Registries-Pivot) system is considered "officially live" across both axes.
Acceptance checklist (with live status)
| Criterion | Target | Live | Blocker |
|---|---|---|---|
| AX-PROCESS official visible | ≥1 official | 0/453 | PROC-OWN-01..03 |
| AX-TRIGGER official visible | axis_registry row + owned | not in registry | AX-TRIGGER owner |
| Process×Trigger cross-check visible | actionable | DONE (ledger live) | — |
| job:cut official | registered | verified, not registered | PROC-OWN-03 |
| dot:kg verified or blocked | REAL_RUN or documented block | BLOCKED (multi-gate) | PROC-OWN-04 + flips |
| events active or blocked | 7/7 or documented | 0/7, packet ready | PROC-OWN-05 |
| UI deployed | live page | branch ready | operator push/PR |
| scanners active | timer active | active (next 04:10) | — |
| production dashboards green | live | live | — |
How acceptance progresses
Each criterion maps to exactly one authority action (above). Engineering contributes nothing more — every "DONE/ready/active" row is engineering; every "blocked" row is authority. Full acceptance = president votes (01–05) + AX-TRIGGER owner + UI operator deploy + dot:kg config flips.
Self-check query
SELECT * FROM v_total_final_acceptance_scorecard ORDER BY sort; — the single-pane acceptance scoreboard (11 dimensions).