09 — Production Verification Cycle

Applied-fix verification (this session)

• B applied: v_h11a_containment_status = CONTAINED.
• C applied & rehearsed: 3 identical fn_log_issue calls → 1 row, occurrence_count=3, 0 extra births.
• D applied & rehearsed: entity_labels (EXEMPT) insert → 0 births.
• Birth before==after across every DDL step = 1,210,724 (no net births from Agent work).
• No new births from entity_labels/registry_changelog after gateway D (verified before==after on the rehearsal insert).

Scheduled verification — v_birth_fix_verification_status

guards pass; scheduled_verification = PENDING_13:00_UTC_CYCLE. The decisive proof is the next executor run at 13:00 UTC (15:00 CEST).

Acceptance criteria — v_birth_next_cycle_acceptance_criteria

criterion	target
heal-driven entity_labels births next cycle	0
anti-loop system_issues births next cycle	0
exempt-collection births next cycle	0
repeated H11a detect findings create new rows	0 (coalesce via occurrence_count)

How to verify after 13:00 UTC

Read v_birth_explosion_top_sources_6h and v_birth_explosion_current_state right after the run: expect ~0 new entity_labels/registry_changelog births and last_10m well under the spike threshold. If any exempt births appear, gateway D regressed; if entity_labels births appear, H11a containment regressed.