09 — Apply Strategy and Done Definition

"Registries-Pivot done enough" criteria — scorecard

Criterion	State
Layer definition canonized + KB-readable	✅ DONE (doc 01)
parent graph live / apply-ready	✅ APPLY-READY, rehearsed-clean 24/6/0 (doc 04); commit = operator
top counts pivot-backed	✅ LIVE (all L1 totals; doc 05)
missing pivots bundle live / apply-ready	◑ APPLY-READY/HELD (PIV-500 needs engine ext; PIV-30x/31x need ratified defs; doc 05)
backend tree contract live / apply-ready	✅ LIVE (v_registries_pivot_node_contract + existing views; doc 06)
final substrate resolution live / apply-ready	✅ LIVE (fn_registries_pivot_node_substrate)
UI handoff matches old Registries concept	✅ DONE (doc 07)
no reliance on dot-pivot-update cleanup	✅ confirmed (doc 03)
remaining blockers exact + minimal	✅ (below)

Done-enough decision: DONE ENOUGH at the contract + apply-ready-graph tier.

The RP layer engine is complete as a backend contract and is one operator UPDATE away from a live hierarchical tree. What remains (grand-total / orphan / phantom aggregate pivots) is genuinely gated by pivot-engine extension + law ratification, not by RP design.

What was applied live (safe, reversible)

1. v_registries_pivot_node_contract — additive read-only view (DROP to reverse). (That is the only mutation. pivot_definitions byte-identical.)

What was rehearsed live then rolled back (net 0)

2. The 13-edge parent_code wiring — proven hierarchical + reversible.

What is held for operator (exact, minimal)

3. COMMIT the parent_code wiring (1 UPDATE; fires the designed count refresh; owner accepts the refresh side-effect). → makes the tree hierarchical live.
4. PIV-30x/31x view-backed pivots (orphan/phantom/drift/IU/KG/system-issues) — owner-gated; need pivot-engine support for view-backed counts + ratified orphan/phantom/unmanaged definitions.
5. PIV-500 grand total — needs cross-table pivot semantics (engine extension).
6. registry_pin + label-by-facet pivots — next phase (doc 08).

Apply guardrails (for operator)

• BEGIN..ROLLBACK rehearse first (already proven for step 3).
• No composition cleanup. No dot-pivot-update. No birth-gate change.
• Keep the one-line rollback ready (doc 04 / doc 10).
• Re-verify pd_hash before/after; verify tree shape 24/6/0.