11 — Current Repoint Decision

Decision: DO NOT repoint → DECORATED_GENERATED_REPOINT_READY_OPERATOR.

Rationale:

1. Circularity: the candidate sources decoration from v_rp_universal_node_ui_contract_current, which is itself a thin alias of v_rp_universal_node_ui_contract_current_v2. Repointing _current to the candidate would recurse. A real repoint must rewire decoration to _current_v2.
2. No no-hardcode benefit yet: decoration is still hand-built (_current_v2); registry-driven decoration (the 58 view-edits) is authority-gated (AX-PXT register + AX-TRIGGER owner/president). Repointing now adds indirection without removing hardcode.
3. Production is green (guard PASS, smoke 15/15); repoint is outward-facing with no immediate upside.
4. Backbone parity is PROVEN, so the repoint is engineering-ready as an operator step (rewire to _current_v2, re-prove parity, stage rollback, repoint, re-run guard/invariant/proof/smoke/anti-false-green/detector).

Guard PASS, full-column parity PASS, OOM-safe, rollback staged — all preconditions met except the operator action + (for no-hardcode) authority. See RUNBOOK §3.