GPT Directive to Opus — P3D Pack 1 Phase 4: Governed Migration Readiness + No-Hardcode Contract

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 Pack: P3D_PACK1_PHASE4_GOVERNED_MIGRATION_READINESS_AND_NO_HARDCODE_CONTRACT Mode: DESIGN + READ-ONLY DISCOVERY PROMPT + DRAFT IMPLEMENTATION PROMPTS ONLY

0. Executive decision

Phase 3 investigation is accepted as BLOCKED. Do not migrate TAC→IU yet.

The next phase must resolve migration readiness and enforce a no-hardcode contract.

User directive is now binding: hardcoded species counts, layer counts, table counts, DOT counts, vocab lists, and registry assumptions must not appear in implementation logic or prompts except as clearly marked snapshots with live re-verification.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase3-hash-planner-birth-alignment-investigation-report.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase3-investigation-blocked-and-no-hardcode-directive-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase2-ddl-extend-implementation-report.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-design-addendum-post-inventory-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/operating-notes/gpt-agent-dispatch-prompt-after-approval-rule-2026-05-11.md

2. Mission

Produce one coherent Phase 4 readiness pack, not many micro-prompts.

The pack must decide what must be prepared before any authoritative TAC→IU migration, but must not execute migration.

3. Required outputs

3.1 Design

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4-governed-migration-readiness-no-hardcode-design.md

Required sections:

A. Phase 3 blocker summary
B. No-hardcode contract
C. Hash reconciliation policy options and recommendation
D. Vocab seeding policy using live discovery, not hardcoded lists
E. Species/composition/governance policy
F. Parent-child / edge materialization policy
G. Collection governance promotion policy
H. Phase 4 allowed implementation sequence
I. Phase 5 migration gates
J. Risks, rollback, and observability

3.2 Read-only discovery prompt

Create:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4-readonly-governance-vocab-discovery-prompt.md

Purpose:

• derive live TAC section/publication types from tables and used data;
• derive live IU vocab config;
• derive live species/entity label/collection registry state;
• derive live parent-child hierarchy from TAC rows;
• derive edge/vocab tables dynamically from registry patterns;
• no mutation.

3.3 Draft implementation prompt(s), not dispatch-ready unless clearly marked DRAFT

Create one draft prompt if possible:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4-governance-vocab-species-prep-implementation-prompt-DRAFT.md

This should draft safe preparation steps such as vocab seed / species map / governance promotion / traceability, but it must remain DRAFT until GPT/User review.

If not safe to draft implementation yet, create a not_ready note explaining why.

3.4 Report

Create:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-readiness-design-report.md

Required fields:

phase_status=PASS|PARTIAL|BLOCKED
mode=DESIGN_DISCOVERY_AND_DRAFT_ONLY
phase3_status=BLOCKED_ACCEPTED
migration_allowed=false
no_hardcode_contract=included|missing
read_only_discovery_prompt_created=true|false
implementation_prompt_draft_created=true|false
hash_policy_recommendation=<summary>
vocab_policy_recommendation=<summary>
species_composition_policy_recommendation=<summary>
governance_promotion_recommendation=<summary>
no_mutation_performed=true
next_required_action=GPT_REVIEW_PHASE4_READINESS_PACK

4. Non-hardcode requirements

Every future query/prompt/design must avoid fixed counts and fixed enumerations unless marked snapshot.

Must use discovery

• Section types: query tac_section_type_vocab and distinct live tac_logical_unit.section_type.
• Publication types: query tac_publication_type_vocab and distinct live tac_publication.publication_type.
• Unit kinds: query dot_config keys matching vocab.unit_kind.% and compare to needed discovered values.
• Section vocab: query dot_config keys matching vocab.section_type.% and compare to needed discovered values.
• Species/composition: query entity_species, species_collection_map, collection_registry, birth_registry, entity_labels.
• Parent-child: query TAC rows for parent_id, not assumed hierarchy depth.
• Edges: query universal_edges actual columns and edge types, not assumed edge vocabulary.

Avoid

• Do not write “17 section types” as a constant in logic; write “current snapshot found N section types”.
• Do not write “10 publication types” as a constant in logic; discover and compare.
• Do not write “6 layers” or “33 species” as implementation constants.
• Do not hardcode table behavior in UI/agent logic where registry metadata can drive it.

5. Design constraints

• Keep EVOLVE as working direction unless evidence rejects it.
• No migration in Phase 4.
• No DDL in Phase 4 design.
• No manual seed values typed from memory.
• If seed is proposed, values must be generated from discovery query results at execution time and recorded.
• Treat TAC source hashes as provenance; do not overwrite or discard without explicit policy.
• Do not require species/composition to be birth-enforced unless the design justifies moving them from DOT enrichment into birth gate.
• Prefer staged governance: prepare registry/vocab/species contract first, then pilot migration, then authoritative promotion.

6. Final response expected from Opus

Return only:

1. Design path.
2. Read-only discovery prompt path.
3. Draft implementation prompt path or not_created with reason.
4. Report path.
5. Top 7 decisions/recommendations.
6. What remains blocked.
7. Whether GPT/User review is required before any agent dispatch.

7. Status

phase3_blocked=true
migration_allowed=false
phase4_design_allowed=true
implementation_allowed=false_until_GPT_User_review