P3D — Birth System B3-P Policy Storage Report
P3D — Birth System B3-P Policy Storage Report
Date: 2026-05-12
Status
status=PASS
mode=DESIGN_AND_PROMPT_DRAFTS_ONLY
policy_storage_designed=true
ddl_prompt_created=true
population_prompt_created=true
agent_dispatch_allowed=false
phase5c2_migration_allowed=false
Artifacts
| # | Path |
|---|---|
| 1 | design/p3d-birth-system-b3p-policy-storage-and-onboarding-contract.md |
| 2 | prompts/p3d-birth-b3p-policy-storage-ddl-prompt-DRAFT.md |
| 3 | prompts/p3d-birth-b3p-policy-population-prompt-DRAFT.md |
| 4 | This report |
Top 8 decisions
-
Option A recommended — columns on collection_registry. Gate reads NEW.coverage_status directly. No JOIN. PG-first.
-
6 policy columns — coverage_status, coverage_scope_status, exemption_reason, review_owner, decided_at, decided_by. CHECK constraints enforce valid values.
-
2-pass pattern for PG functions standardized — Agent generate → GPT review → User GO → Agent execute. Applied to all future B3-F function creation.
-
Governance role → policy mapping = GPT decision — Not data discovery. Agent does not infer which governance_role needs birth gate.
-
Population cross-checks live vs classification — Unclassified new collections → STOP, report, don't assume.
-
DDL prompt = low risk — Only ADD COLUMN, no data mutation. Conflict handling: absent→add, exists-same→skip, exists-different→CONFLICT.
-
Population prompt = medium risk — UPDATE coverage_* columns only. Don't overwrite existing decisions. Rollback by exact captured list.
-
Sequence locked — B3-P-DDL → B3-P-POP → B3-A triggers → B3-F gate → B3-HC health check.
GPT decisions needed
- Approve Option A (columns on collection_registry) or choose B/C
- Approve governance_role → policy mapping (§5 of design)
- Review DDL prompt → approve dispatch
- After DDL: review population prompt → approve dispatch
agent_dispatch_allowed=false
phase5c2_migration_allowed=false
B3-P Report | 2026-05-12