KB-4643

02 — OOM Landmine Detector

2 min read Revision 1

02 — OOM Landmine Detector

v_rp_guard_safety_status = OOM_SAFE__NO_LIVE_SMOKE_COMBO_LANDMINE: live_crash_landmines 0, function_backed_guards 6 (7 after this macro added the non-circular parity function), slow_bounded_views 10, deploy_guard_fn_present true, acceptance_fn_present true.

v_rp_oom_landmine_detector classified 31 RP views (33 after this macro): 0 CRASH_LANDMINE. The two former landmines are neutralized and function-backed — v_rp_ui_current_production_acceptance_dashboard and v_rp_ui_deploy_final_readiness_guard both show deep_stack_refs 0, function_backed true, SAFE_FUNCTION_BACKED. The smoke probe v_rp_ui_current_smoke_probe is SLOW_BOUNDED_NO_SMOKE (slow alone, never combined). No view references the smoke probe (refs_smoke false across the board), which is why there are zero landmines.

Confirmed: the canonical guards are function-backed; no single-statement smoke-combo landmine view remains. The runbook continues to forbid combining the smoke probe with any other deep stack in one statement, and forbids EXPLAIN of any smoke-combo view.

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-post-deploy-final-acceptance-or-operator-standby-2026-06-05/02-oom-landmine-detector.md