CHECKPOINT — RP Post-Deploy Final Acceptance OR Operator Standby + OOM Watch (2026-06-05)

20-phase Program Macro executed. Context was cleared at start; state rebuilt from MCP checkpoints + live production. Live evidence wins.

Final status: PARTIAL

Verdict: RP_DB_SUPERVISION_READY__OOM_STABLE_NO_NEW_CRASH__NONCIRCULAR_REPOINT_CANDIDATE_PREBUILT__UI_AND_REPOINT_AND_OFFICIALIZATION_OPERATOR_AUTHORITY_GATED.

Deploy has NOT happened, so this run took the operator-standby branch: verified operator-ready state, proved OOM stability live, and advanced the decorated-generated repoint from "operator must first author a non-circular view" to "non-circular candidate pre-built and parity-proven; repoint is a single staged statement." All safe engineering is now exhausted. Remaining work is operator (UI git push/deploy; optional repoint apply) and authority (official RP, synthetic-axis registration, REALRUN). No engineering blocker remains.

Execution mode

EXECUTION. Live DB mutation = YES but birth-free, additive, reversible (one new candidate view + one parity function + one parity view). No source-IU edit, no canon, no birth, no event activation, no REAL_RUN, no UI push/deploy, no production current repoint.

Live mutation: YES (additive / reversible / birth-free / OOM-safe)

New objects (RP_POST_DEPLOY macro): v_rp_decorated_generated_candidate_noncircular (backbone generated_v2 + decoration from _current_v2 directly), fn_rp_decorated_generated_parity_v2(), v_rp_decorated_generated_full_column_parity_v2. Applied twice: first apply hit a 64-char identifier truncation, was dropped and recreated with the clean name. birth_registry equal before and after BOTH applies (1,205,419 == 1,205,419). SQL and rollback at /opt/incomex/docs/mcp-writes/rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05/01_noncircular_candidate.sql and 99_rollback.sql. Runbook frozen at RUNBOOK_v3.md in the same directory.

OOM stability — the headline safety result

Live postgres logs confirm the LAST signal-9 was 2026-06-05 06:04:02 UTC (the combo deploy-guard view query). The full window 06:04:02 through ~08:09 UTC shows ZERO signal-9 and ZERO crash recovery — only healthy checkpoints and pre-existing benign background errors (meta_catalog S129-A guard, fn_log_issue varchar overflow, and this session's own harmless typo errors). The 06:23 UTC log shows fn_rp_ui_deploy_final_readiness_guard() hitting a statement-timeout on the smoke gate and TIMING OUT rather than crashing — direct proof the function-backed fix is crash-safe. v_rp_guard_safety_status = OOM_SAFE__NO_LIVE_SMOKE_COMBO_LANDMINE with 0 live_crash_landmines (now 7 function-backed guards, 10 slow-bounded views). v_rp_oom_landmine_detector: 0 CRASH_LANDMINE across all RP views; the two former landmines (acceptance dashboard, deploy-guard view) are function-backed SAFE; the new candidate is SAFE and the new parity view is SAFE_FUNCTION_BACKED. The OOM pause-condition (any new OOM after 06:04) was NOT triggered. All this macro's DDL and queries were OOM-clean.

Dual-path verification

PASS. query_pg read-only (5s timeout) was used for fast base-table and detector reads; ssh to docker exec postgres psql with statement_timeout=0 was used for the crash-safe-but-slow function-backed guards. They agree. Function-backed guards and standalone deep views only; never a smoke-plus-deep-stack combo; never EXPLAIN of a smoke-combo view.

Deploy state

NOT_DEPLOYED_OPERATOR_BLOCKED. Main repo (deployed source) is on branch main at c3b353a with zero rp-current routes in its worktree; d04d8e5 exists only in feat/rp-current-supervision. The running incomex-nuxt container is image nuxt-ssr-local:s174, up 17 hours, built 2026-05-31, and its .output bundle contains none of the rp-current routes. No push, no rebuild, routes not serving.

HTTP smoke / staged smoke

No deploy, so no HTTP smoke run (not faked). The staged 11-route smoke set in the runbook was re-validated against the actual worktree route files (1:1 match: deploy-guard, acceptance/contract/invariant/proof/count-reliability/static-literal-current, axes, node/axis/node plus children plus substrate). DB-side proxy GREEN: fn_rp_ui_current_production_acceptance() = PASS, routes 11, smoke 15/15, anti-false-green 6/6, stale 0, invariant real-fail 0, static stale 0, badges ready, UI_CURRENT_READY_FOR_OPERATOR_DEPLOY.

UI package finality

INTACT. Branch feat/rp-current-supervision at d04d8e5 (tracked tree clean). Routes bind only _current aliases plus the deploy guard — zero v1/v2/v3 direct bindings (verified by grep of the route handlers). 38 _current references across 12 files. Page current/index.vue is fail-closed: it fetches the deploy guard first and renders the supervision body only when verdict equals PASS, else withholds the body. Patch rp-current-supervision.patch applies CLEAN onto origin/main (260ed7b), re-verified this macro via a throwaway detached worktree that was then cleanly removed.

Repoint feasibility (decided)

The original candidate is circular (decoration from the _current alias, which a repoint would redefine). This macro built the NON-CIRCULAR fix: v_rp_decorated_generated_candidate_noncircular sources decoration from _current_v2 directly. Parity proven: v_rp_decorated_generated_full_column_parity_v2 = DECORATED_GENERATED_FULL_COLUMN_PARITY_PASS_NONCIRCULAR (87/87, gen_only 0, cur_only 0, count diffs 0, decoration_missing 0, route/action/reliability 87/87, substrate 81/87 by-design, noncircular true). Repoint decision: DO NOT APPLY. _current is a pass-through alias of _current_v2 and the candidate decoration IS _current_v2, so the repoint produces byte-identical output (proven) and does NOT advance no-hardcode (decoration stays hand-built). Zero functional upside now; swapping the live contract backbone derivation is an operator-authority decision. The repoint is now a single staged CREATE OR REPLACE (exact SQL plus rollback in RUNBOOK_v3 section 3); rollback restores the pass-through alias.

Final acceptance dashboard

v_rp_final_operating_acceptance_dashboard (function-backed, refreshed live): ui_deployed false, db_supervision_ready true, current_guard PASS, generator_replacement DECORATED_GENERATED_REPOINT_READY_OPERATOR, no_hardcode_ready false, official_rp_count 0, AX-PROCESS and AX-TOPIC CANDIDATE, AX-TRIGGER not registered, automation_realrun_enabled false, oom_safety OOM_SAFE, live_crash_landmines 0, final_verdict RP_DB_SUPERVISION_READY__UI_AND_REPOINT_AND_OFFICIALIZATION_OPERATOR_AUTHORITY_GATED. No new deep composite view was created (OOM rule honored).

Monitoring / watch package

Documented in RUNBOOK_v3 section 5 as read-only, OOM-safe, single-statement checks: OOM watch (v_rp_guard_safety_status, expect OOM_SAFE/0), landmine detail (detector where risk_level CRASH_LANDMINE, expect empty), deploy-guard watch (fn_rp_ui_deploy_final_readiness_guard), RP acceptance/smoke (fn_rp_ui_current_production_acceptance), final acceptance (v_rp_final_operating_acceptance_dashboard), and birth-drift interpretation (drift is background; DDL is birth-free). No new composite watch view created, to avoid OOM risk.

Regression package

6/6 PASS with teeth (v_rp_generator_parity_regression_v2): RGT1 AX-PROCESS 22==22, RGT2 teeth v1 generator still misses 3, RGT3 AX-PXT residual 2==2, RGT4 teeth v1 still emits stale 8, RGT5 anti-false-green 6/6, RGT6 v1 generator sentinel exists. Circular decorated parity still PASS (sentinel). Non-circular decorated parity PASS_NONCIRCULAR. Deploy guard PASS, smoke 15/15, anti-false-green 6/6, OOM detector 0 CRASH_LANDMINE.

Authority state (NOT landed; not faked)

PROC-OWN 5 requests / 0 votes; governance_object_ownership 0; axis_registry 2 (AX-PROCESS, AX-TOPIC, both CANDIDATE, 0 ACTIVE); AX-TRIGGER not registered (synthetic surface only); official AX-PROCESS RP 0; dot_config real_run_enabled false (execute/emit/operator_runtime all false/dry); event_type active 30 (no activation). Authority has not landed; all officialization remained blocked, not faked.

Safety / no-fake audit (UNCHANGED)

births 1,205,419 (session start 1,205,410; +9 background; DDL-attributable 0) · ownership 0 · PROC-OWN votes 0 · axis_active 0 · official AX-PROCESS RP 0 · events active 30 · trigger_guard_alerts 129 · real_run_enabled false · all DDL birth-free · v1 sentinels retained · production _current/_current_v2/v1 untouched · no source-IU edit · no UI push/deploy · no OOM-risk guard introduced.

Exact blockers

Operator/git: push feat/rp-current-supervision at d04d8e5 (https remote, credential.helper empty, no agent creds; divergent git 17 ahead / 13 behind) then rebuild incomex-nuxt then run the staged 11-route HTTP smoke.
Operator/repoint (engineering pre-built): apply the single CREATE OR REPLACE repointing _current to v_rp_decorated_generated_candidate_noncircular (RUNBOOK_v3 section 3) with rollback staged — only if the operator wants the generator-driven backbone (no functional change to output, does not advance no-hardcode).
Authority: president PROC-OWN vote (official RP); AX-PXT register plus live-ledger refactor; AX-TRIGGER owner plus president register (unlocks the 58-view-edit no-hardcode registryization); REALRUN flip.

Next macro

SESSION_HANDOFF_AND_PAUSE_UNTIL_OPERATOR_AUTHORITY — every remaining branch requires operator or authority action the agent cannot perform. The moment the operator deploys, the active macro becomes RP_POST_OPERATOR_DEPLOY_SMOKE_AND_FINAL_ACCEPTANCE (run the 11-route HTTP smoke plus updated final acceptance); if the operator instead authorizes the repoint, RP_DECORATED_GENERATOR_REPOINT_APPLY; the authority track (RP_SYNTHETIC_AXIS_AND_OFFICIALIZATION_AFTER_AUTHORITY, then RP_REALRUN_AUTOMATION_CLOSEOUT) proceeds when president/owner act.

Artifacts

Report dir: knowledge/dev/reports/architecture/rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05/00..19. SQL plus runbook: /opt/incomex/docs/mcp-writes/rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05/ (01_noncircular_candidate.sql, 99_rollback.sql, RUNBOOK_v3.md). Prior SSOT: checkpoint-rp-ui-operator-deploy-decorated-generator-final-acceptance-2026-06-05.md.