KB-1C21

03 — Canonical _current Aliases

2 min read Revision 1

03 — Canonical _current Aliases

Stable UI-facing names that point at the best live version, so the UI never hardcodes v1/v2/reliability/computed selection. Old views are retained (not deleted).

_current alias points at rows rationale
v_rp_universal_node_ui_contract_current …_reliability 87 reliability is the CURRENT contract (Phase 2)
v_rp_node_final_substrate_contract_current v_rp_node_final_substrate_contract 87 sole substrate-resolution contract
v_rp_dynamic_drill_proof_matrix_current …_proof_matrix_computed 6 computed-from-invariant proof (Phase 7), not curated v2
v_rp_dynamic_drill_acceptance_dashboard_current …_acceptance_dashboard_v2 1 best live acceptance dashboard
v_rp_count_reliability_dashboard_current v_rp_count_reliability_dashboard 1 reliability rollup

Key choice: proof_matrix_current deliberately points at the computed matrix (Phase 7), not the curated v2 (which has partly-literal PASS). The UI gets a proof surface that can actually fail.

All 5 verified live via both paths. CREATE OR REPLACE only (no DROP) → fully reversible via 99_rollback.sql.

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-contract-canonical-registry-driven-fullpop-nohardcode-closeout-2026-06-05/03-current-aliases.md