06 — Parallel Speedup Recommendations

Safe read-only work T2/T3 can run alongside T1's macro to remove rediscovery and shorten the critical path. None of these mutate anything; all are independent of T1's deploy/authority work.

Recommended parallel tasks (all READ-ONLY)

1. Read-only post-deploy smoke audit (DB-side rehearsal)

   • Run the DB-side acceptance/guard FUNCTIONS via ssh psql statement_timeout=0: fn_rp_ui_current_production_acceptance() (expect 15/15 PASS, 6/6 anti-false-green) and fn_rp_ui_deploy_final_readiness_guard() (expect db_side_ready=true).
   • Pre-stages the exact pass/fail signature so T1's post-deploy HTTP smoke just confirms parity.
   • Safe because functions isolate each gate (no OOM). Independent of the actual deploy.

2. Independent OOM watch

   • Periodically grep postgres container logs for signal 9: Killed / "all server processes terminated"; confirm none after 06:04:02 UTC. Confirm v_rp_guard_safety_status = OOM_SAFE and v_rp_oom_landmine_detector 0 CRASH_LANDMINE.
   • This is the single highest-value background watch — it catches a regression the moment any deploy/repoint or stray query reintroduces a landmine.

3. Authority-packet audit

   • Re-confirm PROC-OWN-01..05 are still pending with 0 votes, ownership 0, axis ACTIVE 0, real_run_enabled false. Confirm the handler functions still resolve BLOCKED_NO_PRESIDENT_VOTE.
   • Keeps doc 04 accurate so authority execution needs no rediscovery.

4. UI source stale-ref audit

   • Via ssh grep over /opt/incomex/docker/nuxt-repo/web: confirm 0 stale v_rp_ references and that the 11 routes bind _current only (no generated-view binding). Confirm prod is still on the legacy/pivot views until the branch merges.
   • De-risks the deploy by proving no route silently binds a landmine or a generated backbone.

5. Final-acceptance cross-check

   • Re-run the no-fake invariant cross-check (doc 00) and the births before==after check; confirm zero engineering drift. Produces the evidence block T1's final-acceptance checkpoint will need.

Sequencing / non-conflict notes

• All five are pure reads — they can run concurrently with each other and with T1's work.
• Keep each heavy view STANDALONE with statement_timeout=0; never combine two heavy views or add the smoke probe in one statement (OOM rule, doc 03). Prefer the function-backed guards.
• Use the MCP read tools for base tables (fast); use ssh psql for any composite/deep view.
• Do NOT let a parallel terminal write SQL/DDL, push git, or touch approvals — those belong to T1 under operator/authority. Parallel terminals produce audit docs only.

Suggested split

• T2: OOM watch (#2) + authority-packet audit (#3) + final-acceptance cross-check (#5).
• T3: DB-side smoke rehearsal (#1) + UI source stale-ref audit (#4).