KB-6065

01 Dual-path + OOM baseline (Phase 1)

2 min read Revision 1

Phase 1 — Dual-path baseline + OOM stability

Dual-path = MCP query_pg (RO, 5s, LIMIT 500) + ssh→docker exec postgres psql. Both paths agree.

OOM

  • v_rp_guard_safety_status = OOM_SAFE__NO_LIVE_SMOKE_COMBO_LANDMINE, live_crash_landmines 0, 7 function-backed guards.
  • v_rp_oom_landmine_detector CRASH_LANDMINE = 0.
  • postgres logs: no signal 9: Killed since 06:04 UTC; only routine checkpoints through 09:19 UTC (covers all this macro's DDL + the controlled scan). OOM rule honored: no smoke-probe + RP-stack combo, no EXPLAIN on combo views.

Baseline (matches prior SSOT)

  • Adapter coverage 94; scanner_automation 100; drift 100; no_blind_spot PASS; open_blind_spots 9; p0_p1 2.
  • Scanner = REAL_AUTOMATION (orchestrator_pipeline + scanner_v2_functions, age 6.7h at start).
  • no-blind-spot-as-zero guard 7/7; adapter automation regression 8/8.
  • Action queue: 7 EXECUTABLE / 132 HANDLER_READY / 15 OWNER_BLOCKED (11 orphan+2 candidate+2 residual) / 7 AUTHORITY_BLOCKED (2 candidate+5 PROC-OWN).
  • Runtime flags ALL false: real_run_enabled, execute_enabled, emit_enabled, operator_runtime_enabled; dry_run_only=true.
  • No-fake: births 1,205,461 (start) ownership 0, axis_active 0, official RP 0, events 30, guard 129.
Back to Knowledge Hub knowledge/dev/reports/architecture/rp-automation-actuation-realrun-closeout-2026-06-05/01-dual-path-oom-baseline.md