P3D — Birth B3 rev3 Self-Expanding Infra No-Hardcode Patch Report

Date: 2026-05-12 Patched: rev2 → rev3

---

Top 10 fixes

1. Policy storage defined — coverage_status + coverage_scope_status + exemption_reason + review_owner columns on collection_registry (design recommendation, DDL separate). Gate reads policy from storage, not inferred from shape alone.

2. B3-A and B3-F SEPARATED — Two distinct prompts. B3-A = trigger install only (medium risk). B3-F = onboarding gate (higher risk, needs policy storage first). Never merged.

3. Periodic health check designed — birth_coverage_gap_check query scans ALL governed collections. Catches: pre-existing gaps, disabled triggers, delayed tables, policy changes outside trigger path. Complement to row trigger.

4. Species queue uses RETURNING PKs — Rollback by exact captured IDs, not timestamp/category.

5. Trigger verified by function OID binding — pg_trigger.tgfoid matched against fn_birth_registry_auto OID. Not trigger name pattern alone.

6. ZERO PL/pgSQL body in prompts — Gate prompt §2 = behavioral contract (5 conditions, inputs, outputs). Agent derives compiled PL/pgSQL from live concept resolution. Compiled body logged in report for review.

7. Concept registry for gate — 19 concepts across collection_registry + system_health_checks + system_issues + species_collection_map. All resolved before any DDL.

8. Approved policy artifact with revision — B3-A requires approved_policy_artifact path + revision number. STOP if revision mismatch.

9. DDL conflict handling — absent→create, exists-same→OK, exists-different→CONFLICT. No CREATE OR REPLACE.

10. Governance role values NOT hardcoded — Gate reads distinct governance_role values from live data to determine "governed-like" set. Not hardcoded list of 'governed','locked','law_artifact'.

---

Confirmation

b3_design_rev=3
b3a_trigger_prompt_rev=3
b3f_gate_prompt_rev=1
prompts_separated=true
no_plpgsql_in_prompts=true
agent_dispatch_allowed=false
phase5c2_migration_allowed=false

---

B3 rev3 Patch Report | 2026-05-12