08 — Birth-Rate & Exempt-Birth Monitoring

All guards are thin base-table views (OOM-safe).

view	purpose	threshold
v_birth_operational_watch_dashboard	one-row roll-up: spike / runaway / duplicate / exempt-contradictions / h11a / births_last_1h	—
v_birth_spike_alert_guard	birth-rate watch	last_10m>200=SPIKE_ALERT; last_1h>2000=ELEVATED
v_birth_explosion_active_runaway_gate	exempt-collection births in 10m	>100=ACTIVE_RUNAWAY
v_birth_exempt_trigger_guard	collections EXEMPT-but-trigger-active	any row = contradiction
v_birth_duplicate_issue_guard	est. duplicate issues 24h	>500=ALERT
v_birth_explosion_top_sources_6h	top birthing collections	—
v_h11a_next_run_risk	H11a mode + next-run risk	—

Snapshot at session close

spike=ELEVATED, duplicate=ALERT — both are residue of the 10:00 run still inside the 1h/24h windows, not new activity; expected to clear after the windows roll and post-containment. runaway=NO_ACTIVE_RUNAWAY, h11a=CONTAINED.

Operational use

Poll v_birth_operational_watch_dashboard (e.g. each 3h cycle after the executor runs). A future +5k spike makes last_10m jump > 200 and active_runaway_gate flip to ACTIVE_RUNAWAY before RP is polluted — the signal that was missing during the original incident.