GPT Directive to Opus — P3D Pack 1 Phase 5 TAC→IU Migration Design

Date: 2026-05-11 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Workstream: P3D_INFORMATION_UNIT_TEXT_AS_CODE Mode: DESIGN + READ-ONLY/DRY-RUN PROMPT ONLY

0. Executive decision

Phase 4D decision memo is accepted. GPT chooses Option 2:

Defer all species mapping/backfill to Phase 5 migration design.

Reason:

nesting decision → composition level → species choice → mapping → QT-001 backfill

Species/composition must not be decided before TAC nesting is designed.

Open:

P3D_PACK1_PHASE5_TAC_TO_IU_MIGRATION_DESIGN

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4d-decision-memo-accepted-phase5-next-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4d-species-mapping-decision-memo.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4d-execution-options-design.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4c-species-mapping-dryrun-report.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-vocab-species-seed-implementation-report.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4b-legal-alignment-addendum.md
knowledge/dev/laws/dieu44-trien-khai/operating-notes/design-after-repair-implementation-rule-2026-05-11.md

2. Mission

Create Phase 5 design and a read-only/dry-run prompt for TAC→IU migration.

No migration. No seed. No backfill. No DDL. No function patch.

The first design question must be the nesting strategy:

preserve TAC parent-child vs flatten vs hybrid by live evidence

Only after nesting strategy is analyzed may the design discuss composition/species/backfill.

3. Required outputs

3.1 Design

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase5-tac-to-iu-migration-design.md

Required sections:

A. Phase 5 purpose and non-goals
B. Completed prerequisites from Phases 1–4D
C. Live TAC→IU source/target model summary
D. Nesting strategy options: preserve / flatten / hybrid
E. Consequences of each nesting option for composition
F. Consequences of each nesting option for species mapping and QT-001 backfill
G. Migration mapping: TAC logical_unit → information_unit and TAC unit_version → unit_version
H. Hash/provenance policy: IU body hash + original TAC hash provenance
I. Parent/child mapping and render_order preservation
J. Batch strategy and pilot-first plan
K. Verification gates: 0 drift render, row accounting, no duplicate canonical addresses, gateway/invariant checks
L. Rollback/restore strategy
M. Post-implementation design requirement
N. Recommendation and next executable pack boundaries

3.2 Read-only/dry-run prompt

Create:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5-readonly-dryrun-tac-to-iu-migration-prompt.md

The prompt must compute, but not execute:

• row accounting for TAC logical units and versions;
• mapping candidates TAC→IU;
• parent-child translation candidates;
• render_order preservation checks;
• canonical address collision checks;
• content hash/provenance projection;
• species/composition consequences under preserve/flatten/hybrid nesting options;
• QT-001 backfill target projections;
• pilot document selection options;
• rollback/restore inputs.

It must be read-only and introspect-first.

3.3 Report

Create:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5-tac-to-iu-migration-design-report.md

Required flags:

phase5_status=PASS|PARTIAL|BLOCKED
mode=DESIGN_AND_DRYRUN_PROMPT_ONLY
phase4d_option=OPTION_2_DEFER_SPECIES_TO_PHASE5
nesting_decision_locked=false
species_decision_locked=false
migration_allowed=false
seed_allowed=false
backfill_allowed=false
read_only_prompt_created=true|false
post_implementation_design_rule_included=true|false
next_required_action=GPT_REVIEW_PHASE5_DESIGN_AND_DRYRUN_PROMPT

4. No-hardcode constraints

• Do not hardcode TAC row counts as gates. Use live counts; previous 86 count is historical context only.
• Do not hardcode section_type values; derive live.
• Do not hardcode species/composition values; derive live or present as options from evidence.
• Do not hardcode parent column; detect live column if prompt queries it.
• Do not hardcode publication count; derive live.
• Scope constants are allowed only if explicitly declared: target collection information_unit, target collection unit_version, committed vocab value law_unit, and Pack 1 target family.
• Distinguish scope constants from live-derived values.

5. Hard boundaries

• No agent dispatch from Opus.
• No DB write.
• No migration.
• No seed.
• No backfill.
• No DDL.
• No function/trigger patch.
• No species/composition decision locked.
• No dropping/replacing TAC tables.
• No Directus/Nuxt/Qdrant changes.

6. Future executable requirement

If Phase 5 later executes any migration/seed/backfill, after Agent report is accepted it must create a concise post-implementation design per:

knowledge/dev/laws/dieu44-trien-khai/operating-notes/design-after-repair-implementation-rule-2026-05-11.md

7. Final response expected from Opus

Return only:

1. Phase 5 design path.
2. Phase 5 read-only/dry-run prompt path.
3. Phase 5 report path.
4. Top 7 migration design decisions/questions.
5. Confirmation GPT/User review is required before agent dispatch.

8. Status

phase4d=ACCEPTED
phase5_design_allowed=true
agent_dispatch_allowed=false
migration_allowed=false
seed_allowed=false
backfill_allowed=false