P3D — B3-A2 Blocker Resolution Design Report

Date: 2026-05-12

---

Status

b3a2_blocker_resolution_design_status=PASS
recommended_birth_registry_option=EXEMPT_SYSTEM_MANAGED_VIA_ALLOWED_POLICY_VALUES
recommended_variant_function_option=CONDITIONAL_WHITELIST_AFTER_SOURCE_EQUIVALENCE_PROBE
clean_trigger_candidates=9 (evidence snapshot, re-verify live)
trigger_install_allowed=false
ddl_allowed=false
pg_mutation_allowed=false
phase5c2_migration_allowed=false
next_recommended_action=GPT_REVIEW_B3A2_DESIGN

Artifacts

#	Path
1	design/p3d-birth-system-b3a2-blocker-resolution-design.md
2	This report

Top 5 decisions

1. birth_registry = EXEMPT (SYSTEM_MANAGED semantics via allowed policy values) — Sổ khai sinh không khai sinh chính nó. Do not write SYSTEM_MANAGED into coverage_scope_status unless a separate DDL first extends the CHECK constraint. Recommended: set coverage_status='BIRTH_EXEMPT_SYSTEM_LOG_OR_AUDIT', keep coverage_scope_status within the live allowed set (currently IN_SCOPE), and put SYSTEM_MANAGED semantics in coverage_exemption_reason. Không gắn trigger. Existing 2 triggers giữ nguyên.

2. fn_birth_registry_auto_id = conditional contract sibling — 3 tables (governance_relations, law_dot_enforcement, law_jurisdiction) đã birthing qua variant function. However validators may accept both OIDs only after a read-only pg_get_functiondef() / birth-row equivalence probe proves the variant is a safe sibling, not a semantic fork. Future consolidation when contract function is refactored.

3. 9 clean candidates ready for B3-A3 — After birth_registry EXEMPT + variant whitelisted, 9 collections left for trigger install. B3-A3 prompt re-verifies live, không dùng "9" hardcoded.

4. 18 duplicate triggers → B3-A-DUP separate — Tech debt, not B3-A3 blocker. Separate design for legacy trigger cleanup.

5. 57 description_policy unclassified → B3-DESC separate — Semantic classification, not coverage. Separate workstream.

GPT decisions needed

1. Accept birth_registry EXEMPT via allowed B3-P policy values?
2. Accept variant function whitelist as a conditional direction only?
3. Before B3-A3 trigger install prompt: run B3-A2a read-only variant equivalence probe and B3-A2b birth_registry exemption execution/prompt review. Only after those pass should Opus draft B3-A3 trigger install prompt for the clean candidate set re-verified live.

trigger_install_allowed=false
agent_dispatch_allowed=false
phase5c2_migration_allowed=false

---

B3-A2 Report | 2026-05-12