07 — Return-to-RP Packet

For the next session/Agent/operator. No rediscovery needed.

Current RP state (live, 2026-06-03)

v_rp_classification_governance_map LIVE, 37 active rows. 3 composition mismatches (PIV-001→atom, PIV-016→meta, PIV-021→molecule) born, flagged, awaiting tool. 9 drill_overload law-valid (keep). 4 no_ref (rp_local/retire candidate). 5 unborn pivots (PIV-101..106) separate birth-collision, NOT cleanup targets.

Safe RP path chosen

RP/IU work: RESUME NOW (Path 3, no mutation). RP cleanup (3 fixes): WAIT on one credential, then run the authored tool.

Exact tool path (when creds arrive)

1. dot-dot-register → register+birth dot-pivot-update (governed).
2. dot-pivot-update --auto-from-species (DRY-RUN) → shows PIV-001/016/021 fixes.
3. Verify dry-run reports exactly 3 mismatches → 0.
4. dot-pivot-update … --commit (or apply_composition_fixes.sh --commit).
5. Re-run fn_preflight_guard() + RP view to confirm mismatch count = 0.

Guard output to expect

Before: 4 BLOCK (59/6/16/1). After register+birth of the tool: dot_pivot_update_not_governed→0, fs→15. The 3 other dims are non-RP and remain until their own owner/admin actions — must NOT be cleared by exception to pass.

Rollback requirements

Tool registration reversible via governed retire. Composition --commit has authored BEGIN…ROLLBACK rehearsal + rollback script proven (entry-hash==exit-hash method). Always dry-run first.

Exact forbidden actions (carry forward)

Do not execute/manually register dot-pivot-update without the full lawful registrar path. Do not psql-UPDATE pivot_definitions. Do not add a global accepted exception to pass the guard. Do not apply the pre-birth permit, alter birth_registry constraints, or flip the birth gate. Do not treat the 9 drill_overload rows as errors.

dot-pivot-update status

STILL INVALID — STAGED_FILE_ONLY / UNBORN / NOT_VALID_DOT (sha256 3313c057…effc5).

RP cleanup decision

NO-GO for the 3 fixes (tool-gated). GO for RP/IU resume (Path 3, no mutation).