05 — Monitoring & Guard Hardening (Track E)

Two consolidated views added this session.

v_birth_fix_operational_guard_dashboard (live)

guard	state	detail
birth_spike_guard	OK	last_10m=0 last_1h=3
exempt_birth_runaway_guard	NO_ACTIVE_RUNAWAY	exempt_births_last_10m=0
duplicate_issue_guard	ALERT	est_duplicates_24h=7,139 (pre-fix residue, ages out)
h11a_containment_guard	CONTAINED	check_kind=detect_only auto_fix=NULL
rp_object_hygiene_guard	POLLUTED_USE_MANAGED_COUNT	managed=2,927 raw=1,210,742 noise_pct=98.97
trigger_contradiction_guard	OWNED_AND_NEUTRALIZED	exempt29(neutralized)/deferred50/dup18/required5 — all owned

POLLUTED_USE_MANAGED_COUNT is an instruction, not a failure — it directs consumers to managed_object_count. duplicate_issue_guard=ALERT reflects the pre-fix 24h window only.

v_birth_fix_no_go_guard — 7/7 PASS (teeth)

1. H11a is detect_only and auto_fix_action IS NULL — true
2. fn_birth_registry_auto skips BIRTH_EXEMPT collections — true
3. fn_log_issue is idempotent (coalesce_key + occurrence_count) — true
4. no new exempt births in last 1h — true
5. no active runaway — true
6. RP truth contract exposes managed_object_count ≠ raw_birth_count — true
7. no trigger DDL applied this session (packet text-only) — true

These assertions read live function definitions and live birth windows (not cached), so they have teeth: if H11a were re-armed, or fn_birth lost its exempt-skip, or a new exempt-birth burst started, the corresponding assertion flips to false.

Pre-existing guards re-verified

v_birth_fix_verification_status (CONTAINED / NO_ACTIVE_RUNAWAY / PENDING_13:00), v_birth_gateway_no_go_guard (3/3), v_birth_exempt_trigger_guard (29 exempt-active enumerated), v_birth_explosion_active_runaway_gate.