GPT Directive to Opus — P3D Birth B3-P rev2 Policy Prompt Hardening

Date: 2026-05-12 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Mode: DESIGN PATCH + PROMPT PATCH ONLY — no execution

0. Verdict

Option A is accepted directionally: coverage policy should be stored as columns on collection_registry.

DDL and population prompts are not dispatch-approved. Patch to rev2.

Open:

P3D_BIRTH_B3P_REV2_POLICY_STORAGE_PROMPT_HARDENING

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-birth-b3p-policy-storage-option-a-ok-prompts-need-rev2-2026-05-12.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-b3p-policy-storage-and-onboarding-contract.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-b3p-policy-storage-ddl-prompt-DRAFT.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-b3p-policy-population-prompt-DRAFT.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-b3p-policy-storage-report.md

Do not search broadly.

2. Target outputs

Patch design lightly:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-b3p-policy-storage-and-onboarding-contract.md

Patch DDL prompt:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-b3p-policy-storage-ddl-prompt-DRAFT.md

Patch population prompt:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-b3p-policy-population-prompt-DRAFT.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-b3p-rev2-policy-prompt-hardening-report.md

3. Required DDL prompt hardening

Add explicit production-write safety:

execution log path or discovery/fallback
advisory lock
single transaction
compiled SQL preview before DDL
rollback plan
post-rollback verification
KB + VPS log persistence

DDL remains DDL-only:

No data mutation.
No policy population.
No triggers.
No functions.
No 5C2.

4. CHECK constraints

Define constraint plan:

constraint names
existing constraint conflict check
exact allowed values
post-DDL introspection

No silent overwrite.

If a matching constraint already exists → OK.
If same name but different definition → BLOCKED_EXISTING_CONFLICT.
If different name but equivalent definition → report and do not duplicate unless GPT approved.

5. Type compatibility

Define accepted type compatibility:

coverage_status: varchar/text acceptable? decide explicitly
coverage_scope_status: varchar/text acceptable? decide explicitly
coverage_decided_at: timestamptz exact
coverage_exemption_reason: text/varchar acceptable
coverage_review_owner: text/varchar acceptable
coverage_decided_by: text/varchar acceptable

If incompatible → BLOCKED_EXISTING_CONFLICT.

6. Required population prompt hardening

Remove execution dependence on historical counts:

29 / 43 / 20 / 11 / 4 / 7 / etc. = reference only, not gates.

Population groups must come from:

approved classification artifact path + revision/hash
live collection_registry recheck

7. Approved policy artifacts

Add:

approved_classification_artifact_id
approved_classification_artifact_revision_or_hash
approved_governance_policy_artifact_id
approved_governance_policy_revision_or_hash
approved_population_actor

If missing → not dispatch-ready.

8. Rollback safety for population

Before UPDATE capture exact old values per row:

collection key
old coverage_status
old coverage_scope_status
old coverage_exemption_reason
old coverage_review_owner
old coverage_decided_at
old coverage_decided_by

Use UPDATE ... RETURNING to capture changed rows.

Rollback restores old values, not blanket NULL.

9. Actor/timestamp policy

Define:

coverage_decided_at = RUN_STARTED_AT or transaction timestamp
coverage_decided_by = approved_population_actor

Actor must be GPT/User-locked before dispatch.

10. CMS/Agency split

CMS/Agency split must come from classification artifact evidence, not name inference during population.

If classification artifact does not encode enough evidence → STOP and ask GPT/User.

11. Do not do

• Do not dispatch Agent.
• Do not write DB.
• Do not execute DDL.
• Do not populate policy.
• Do not create triggers/functions.
• Do not patch 5C2.
• Do not migrate.

12. Expected Opus response

Return only:

1. Patched design path.
2. Patched DDL prompt path.
3. Patched population prompt path.
4. Patch report path.
5. Top 10 rev2 fixes.
6. Whether any prompt is ready for GPT final review.
7. Confirmation: agent_dispatch_allowed=false, phase5c2_migration_allowed=false.

13. Status

b3p_rev2_patch_allowed=true
agent_dispatch_allowed=false
phase5c2_migration_allowed=false