06 · Final Summary — T2 UI-Current / Autoscale-Generator / Deploy-Risk Audit

Status: PARTIAL (T1 newest checkpoint absent → AWAITING_T1_FINAL; audit advances; next macro writable without rediscovery). Mode: READ-ONLY. Mutations: NONE except this KB doc set (7 docs + checkpoint). DB: directus.public.

Verdicts

• UI current binding: NOT_READY (P0) — _current exists, 87 rows, exposes all reliability fields; but no UI package binds it (existing packages bind v1/v2), and the bound contract under-labels the 2 real FAILs as CANDIDATE (false-green) unless the renderer also binds invariant_status.
• Generator / auto-scale: PARTIAL / NEEDS_REGISTRYIZATION — binding metadata externalized (v_rp_axis_source_binding, …_registry_driven), but UNION bounded not killed: 58/87 nodes requires_view_edit, 3/5 axes synthetic, _current does not resolve through the registry-driven view. Real risk of moving the hardcode into the registry-driven view's synthetic branches if _current is repointed prematurely.
• Deploy risk: HIGH — no _current package, no deploy-guard view, no _current smoke set, divergent git, no push creds. Engineering blockers are T1-fixable; deploy itself is operator/authority.
• Regression risk: MANAGEABLE IF GUARDED — tests well-defined; but the guard view that wires them does not exist and 2 FAILs are live with no gate.

Findings by severity

P0 (block UI productionization)

• UI-BIND-1: No UI package binds _current; deploying existing packages renders stale v1 (12 false-affordance nodes).
• UI-BIND-2: False-green — 2 live invariant FAILs (PROC:new_candidates, PROC:residual_reconcile) carry reliability_label=CANDIDATE; renderer status branch MUST bind invariant_status.

P1 (fix before deploy)

• DEPLOY-GUARD: v_rp_contract_current_guard missing — no machine gate for rowcount/null/FAIL/identity. (T1 build.)
• GEN-1: 58/87 requires_view_edit; do not bind _current→registry_driven until 87@false.
• BADGES: renderer must expose reliability_label/source_scope/confidence/invariant_status/next_action + SYNTHETIC/CANDIDATE/OFFICIAL/PARTIAL/STALE (data present; render unverified).
• DIVERGENCE: 10 v1↔v2 drill divergences; any route still on v1 renders stale.
• STALE-LABEL: _current reports residual_reconcile as ledger_backed/CANDIDATE though detector knows it's STALE (8 vs live 2).

P2 (label & continue)

• Version sprawl (v1/v2/reliability/computed/current coexist; no _vN lint).
• 2 FAIL nodes' CANDIDATE-vs-STALE label mismatch — pending T1 substrate-fix.
• Phantom pivots / MTX-TEST in AX-BASE headline.
• Derived axes (AX-BASE/AX-PXT/AX-TRIGGER) cannot be pure-view-generated — design decision needed.

P3 (authority/operator only)

• Git convergence + push/PR/merge (no creds); Nuxt deploy; real_run_enabled flip; president votes; axis owners; UI-source grep (needs repo access).

What T1 MUST fix before UI productionization

1. Resolve the 2 invariant FAILs (substrate-fix-v2 — the absent checkpoint) or allow-list them with on-node STALE labels. No silent CANDIDATE on FAIL nodes.
2. Build v_rp_contract_current_guard (the missing deploy gate).
3. Author the _current-bound UI route package (routes + render model binding invariant_status + badges + smoke).
4. Keep _current→reliability; do not repoint to registry_driven until it yields 87@requires_view_edit=false.

What can be labelled and proceed

• 3 synthetic axes → SYNTHETIC/DERIVED badge.
• 58 requires_view_edit → auto-scale PARTIAL / NEEDS_REGISTRYIZATION banner.
• 2 FAIL nodes → render FAIL/STALE from invariant.
• UI source unverifiable → UNVERIFIED_SOURCE_ACCESS; ship as SUPERVISION/CANDIDATE surface with visible warnings; 0 official is correct.

Safety / no-fake

PASS. Read-only confirmed; official RP 0 / votes 0 / ownership 0 / real_run false / guard 129 preserved; birth_registry untouched (no writes); no Nuxt math introduced; all divergences labelled.

Mismatch with T1 framing

T1's "UI production closeout / drill PROVEN" holds for the non-deployed v2/reliability twins on a curated proof set. The deploy-intended path still lacks a _current UI package and a deploy guard, carries 2 live FAILs, and is not registry-driven for 58/87 nodes. T1's authority framing is correct; the engineering gaps above are T1-fixable without authority and are exactly the absent checkpoint's scope.

Next macro

RP_UI_CURRENT_PRODUCTIONIZATION_WITH_RELIABILITY_BADGES_AND_SMOKE — execute checklist in doc 05. Gate on v_rp_contract_current_guard PASS + grep-0-non-current + false-green test.