GPT Directive to Opus — P3D Birth B3 Trigger Design + Governance Decisions

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

0. Verdict

Birth coverage classification is accepted as PARTIAL. B3 design may start, but no execution is allowed.

Open:

P3D_BIRTH_SYSTEM_COMPLETION_B3_TRIGGER_DESIGN_AND_GOVERNANCE_DECISIONS

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-birth-classification-partial-b3-decisions-2026-05-12.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-coverage-classification-report.md
knowledge/dev/laws/dieu44-trien-khai/reviews/opus-review-birth-classification-partial-b3-decisions-needed-2026-05-12.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-b2-contract-design.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-standard-relationship-rules-8-confirmed-2026-05-12.md

Do not search broadly.

2. Mission

Create B3 design and implementation prompt draft for completing birth coverage, but do not execute anything.

B3 must stay PG-first, PG-native, PG-driven.

3. Target outputs

3.1 B3 trigger + governance design

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-b3-trigger-design-and-governance-decisions.md

Required sections:

A. B3 problem statement
B. 43 BIRTH_REQUIRED trigger design target
C. Coverage scope policy for 48 excluded collections
D. ORPHAN_REGISTRY_REVIEW for 7 missing tables
E. HOOK_TABLE_POLICY for entity_labels, universal_edges, and other hook tables
F. unit_version subordinate policy
G. Owner resolution + birth_owner_ref design direction
H. PG-native governance artifacts
I. Trigger implementation strategy
J. Backfill strategy
K. Rollback and verification strategy
L. Phase 5C2 impact

3.2 B3 implementation prompt DRAFT

Create:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-system-b3-trigger-implementation-prompt-DRAFT.md

DRAFT only. Must not be dispatch-ready until GPT review.

3.3 B3 report

Create:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-b3-trigger-design-report.md

4. B3 decisions to apply

4.1 43 BIRTH_REQUIRED

Design trigger installation for the 43 BIRTH_REQUIRED collections.

Do not execute.

4.2 Excluded collections policy

Do not add a sixth core coverage status. Instead add a separate governance/scope dimension:

coverage_scope_status = IN_SCOPE | USER_EXCLUDED | FUTURE_SCOPE | ORPHAN_REGISTRY | SYSTEM_MANAGED

Apply:

• CMS / Antigravity currently excluded → likely USER_EXCLUDED or SYSTEM_MANAGED; not immediate trigger target.
• Agency OS business currently excluded → FUTURE_SCOPE or BIRTH_REQUIRED_CANDIDATE; not immediate trigger target unless GPT/User promotes.

4.3 Missing tables

Do not delete registry rows or create tables yet.

Design ORPHAN_REGISTRY_REVIEW with decisions:

DELETE_REGISTRY_ROW
CREATE_TABLE
KEEP_AS_PLANNED_PLACEHOLDER

4.4 Hook tables

Design HOOK_TABLE_POLICY.

Rules:

• If hook row is first-class/auditable relationship entity → may need birth trigger.
• If pure junction/mechanical mapping → may be exempt.
• Decide per hook table.

4.5 unit_version

Confirm current policy:

unit_version is subordinate/hạ-nguyên-tử-like for birth/species purposes.
No standalone birth trigger in B3.

4.6 Owner resolution

Design, not execute, owner resolution:

source record owner-like field
→ collection owner policy
→ governance/system owner
→ UNKNOWN_OWNER

If proposing DDL, mark as DRAFT and do not dispatch.

4.7 PG-first governance

Use existing PG artifacts:

collection_registry
dot_config
universal_rule_registry
birth_registry
species_collection_map
entity_species
entity_dependencies
universal_edges
system_health_checks
system_issues
PG functions/triggers

No external tools.

5. Implementation prompt draft requirements

The DRAFT prompt must be self-contained and anti-hardcode:

• no fixed DB credentials;
• no fixed schema assumption;
• no hardcoded column names;
• no hardcoded counts as gates;
• no hardcoded function signature assumptions;
• no broad trigger creation;
• table-family and concept resolution before SQL;
• advisory lock if write prompt later becomes dispatchable;
• exact-key rollback design;
• post-rollback verification;
• report all compiled SQL/function calls before execution;
• STOP on any unresolved required concept.

The DRAFT may include the 43 BIRTH_REQUIRED collection names as classification evidence, but final execution must re-verify live and compare to approved target set before writing.

6. Do not do

• Do not dispatch Agent.
• Do not write DB.
• Do not create triggers.
• Do not add columns.
• Do not patch functions.
• Do not install external tools.
• Do not patch 5C2.
• Do not migrate.

7. Expected Opus response

Return only:

1. B3 design path.
2. B3 implementation prompt DRAFT path.
3. B3 report path.
4. Top 10 B3 decisions.
5. Whether implementation prompt is ready for GPT review.
6. Confirmation: agent_dispatch_allowed=false, phase5c2_migration_allowed=false, external_tool_install_allowed=false.

8. Status

b3_design_allowed=true
b3_execution_allowed=false
agent_dispatch_allowed=false
phase5c2_migration_allowed=false
external_tool_install_allowed=false