05 — Next Macro Selector

Pick the next T1 macro by reading the current condition. Default starting point (today): operator deploy NOT completed, authority NOT landed, no new OOM, repoint allowed but DO-NOT-NOW.

Decision matrix

If operator deploy COMPLETED (UI pushed/merged/rebuilt)

→ RP_POST_DEPLOY_FINAL_ACCEPTANCE

• Run the 11-route HTTP smoke (doc 01), re-run DB-side acceptance/guard via functions, re-run OOM detector (doc 03), confirm no false-green on a known real-fail node.
• Then write the post-deploy/standby checkpoint that is currently missing (checkpoint-rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05.md).

If operator deploy NOT completed (creds still unavailable)

→ RP_OPERATOR_STANDBY (hold) — keep DB layer warm, do NOT mutate.

• Optionally do read-only parallel work (doc 06): post-deploy smoke dry-run via DB functions, OOM watch, UI source stale-ref audit. Re-confirm UI_DEPLOY_BLOCKED_BY_GIT is the only blocker.

If authority LANDED (president vote present / owner record present)

→ RP_AUTHORITY_EXECUTION per doc 04 order (PROC-OWN-01 → 02 → 03 → 05 → 04 → AX-PXT/AX-TRIGGER).

• Execute ONE PROC-OWN at a time; re-run the no-fake cross-check after each.

If authority NOT landed

→ stay in RP_OPERATOR_STANDBY / engineering-only. Do NOT fabricate votes/owners. All handlers remain fail-closed (BLOCKED_NO_PRESIDENT_VOTE) by design — that is correct, not a defect.

If a NEW OOM detected (signal-9 after 06:04:02 UTC, OR any CRASH_LANDMINE)

→ RP_OOM_INCIDENT_RESPONSE (highest priority, pre-empts everything).

• Stop all deploy/repoint. Identify the offending view via v_rp_oom_landmine_detector, neutralize it to function-backed, re-confirm v_rp_guard_safety_status = OOM_SAFE and 0 CRASH_LANDMINE, grep postgres logs for new signal-9. Only resume once clean.

If repoint ALLOWED (operator explicitly requests backbone swap, or authority unlocks no-hardcode)

→ RP_DECORATED_GENERATED_REPOINT per doc 02 (build non-circular view from _current_v2 → re-prove parity → stage rollback → repoint → full proof chain → detector 0 CRASH_LANDMINE).

If repoint NOT allowed (default today)

→ DO NOT repoint. Production _current is green; the only candidate is circular; no-hardcode is authority-gated. Leave _current/_current_v2/v1 sentinel untouched.

Composite condition guidance

• Most likely next state: operator deploy + post-deploy final acceptance (opts 1+2 of the newest checkpoint's NEXT), with authority execution (doc 04) runnable in parallel the moment a vote lands.
• The newest existing checkpoint declared NEXT = RP_POST_DEPLOY_FINAL_ACCEPTANCE_AND_DECORATED_GENERATOR_REPOINT. With repoint DO-NOT-NOW, the realistic T1 macro collapses to post-deploy final acceptance once the operator deploys, else standby.