08 — Next Macro / RP Handoff

Owner direction: stop drifting into infrastructure. Recommended next = smallest credentialed operator action, not a build.

Option 1 (preferred) — credentialed close-out of RP cleanup

REGISTRIES_PIVOT_DOT_PIVOT_UPDATE_REGISTER_AND_COMMIT (operator-run). Precondition: operator has dot-dot-register creds. Steps: register+birth dot-pivot-update → dry-run → commit 3 composition fixes → verify mismatch=0 and dot_pivot_update_not_governed=0. Scope: RP only. No governance/pre-birth expansion.

Option 2 (if creds still absent) — resume IU work now

Proceed with miếng-thông-tin / IU work directly on the live RP view (Path 3). The 3 composition fixes stay queued for Option 1. No macro needed — just resume the actual product work the RP cleanup was clearing the way for.

Explicitly deferred / owner-gated (do NOT auto-start)

Pre-birth permit apply (rehearsed+proven; owner-gated). dot_tools enforcement pilot (owner-gated). Composite-unique (entity_code, collection_name) migration + birthing PIV-101..106 (one-way door; owner+DB-design). iu_cmd (54) onboarding, 6-phantom retire mechanism, 15 FS script registration. RP schema split (domain_facet+pivot_kind+drill_level). Governance L2 activation / OSPA seed. None block RP/IU resume.

Handoff statement

The minimum lawful path back to RP is one credential away for cleanup, zero blockers away for resuming work. Safety net intact and unweakened. Next actor: Option 1 if creds available, else Option 2.