07 — Final Summary

T2 read-only acceleration pack for the next T1 RP macro. The next macro can be CHOSEN and EXECUTED without rediscovery. Status PARTIAL only because T1's newest post-deploy/standby checkpoint does not exist yet (the pack itself is complete and live-verified).

Readiness classifications

• UI operator deploy: READY. Exact Path A (push) + Path B (git am patch onto origin/main), rebuild (docker compose -f docker-compose.local.yml build/up incomex-nuxt), 11-route smoke, function-backed deploy guard, rollback, no-go — all pinned (doc 01). Sole blocker = operator GitHub creds (UI_DEPLOY_BLOCKED_BY_GIT). Minor AMBIGUOUS: exact compose flags + curl base-URL host.
• Decorated-generated repoint: READY_OPERATOR_GATED → DO-NOT-NOW. Full non-circular rebuild sequence + rollback pinned (doc 02). Gated by: production green (no upside), candidate is circular (rebuild from _current_v2), true no-hardcode is authority-gated.
• OOM safety: VERIFIED / OOM_SAFE. All five rules present in runbook; live 0 CRASH_LANDMINE, guard_safety OOM_SAFE, no signal-9 since 06:04:02 UTC (doc 03).
• Authority execution: MAPPED (not executable). PROC-OWN-01..05 codes/titles/gates/expected RP deltas + AX-PXT/AX-TRIGGER pinned (doc 04). All fail-closed on president vote (0) + owner (0).

Next macro selector (doc 05)

• deploy completed → RP_POST_DEPLOY_FINAL_ACCEPTANCE (+ write the missing checkpoint)
• deploy not completed → RP_OPERATOR_STANDBY (read-only parallel work ok)
• authority landed → RP_AUTHORITY_EXECUTION (PROC-OWN-01→02→03→05→04→AX register)
• authority not landed → standby / engineering-only (handlers stay fail-closed)
• new OOM → RP_OOM_INCIDENT_RESPONSE (pre-empts all)
• repoint allowed → RP_DECORATED_GENERATED_REPOINT (non-circular)
• repoint not allowed (default) → do not repoint

Safe parallelization (doc 06)

Read-only: DB-side smoke rehearsal, independent OOM watch, authority-packet audit, UI stale-ref audit, final-acceptance cross-check. Suggested split: T2 = OOM watch + authority audit + drift cross-check; T3 = smoke rehearsal + UI stale-ref audit.

Missing / ambiguous commands

• AMBIGUOUS: exact docker compose up flags and the live host/base-URL for the 11 curl routes.
• MISSING_COMMAND: no scripted one-shot curl smoke harness (routes run manually).
• Wrapper nuance: function-backed guard can statement-timeout (not crash) under the MCP 5s wrapper on the smoke gate → call via ssh psql statement_timeout=0.

What T1 must update

1. Write the missing checkpoint checkpoint-rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05.md after the next deploy-or-standby decision (its absence is the only reason this pack is PARTIAL).
2. Pin the exact docker compose up invocation and the curl base-URL/host into RUNBOOK_v2 §1–§2.
3. (Optional) add a scripted 11-route curl smoke harness.
4. Add the "guard fn can timeout under the 5s MCP wrapper → use ssh psql statement_timeout=0" nuance to RUNBOOK_v2 §0 (T2 discovered it live; doc 03).

Live evidence (T2 read-only cross-check, 2026-06-05; zero drift)

ownership 0 · axis_registry 2 / 0 ACTIVE · AX-PROCESS RP 0 · PROC-OWN 5 pending / 0 votes · guard_alerts 129 · events active 30 · real_run_enabled false · 0 CRASH_LANDMINE · guard_safety OOM_SAFE · no signal-9 since 06:04:02 UTC.

Mutations

NONE except the eight KB docs (00–07) + the checkpoint. No DB / FS-source / UI / Git / approvals / owners / events / REALRUN / production-service changes.