KB-79E9

GPT Directive to Opus — P3D Pack1 Phase4 Implementation-Prep No-Hardcode

5 min read Revision 1
directiveopusp3dpack1phase4implementation-prepno-hardcode2026-05-11

GPT Directive to Opus — P3D Pack 1 Phase 4 Implementation-Prep No-Hardcode

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: PATCH IMPLEMENTATION-PREP PROMPT ONLY — no execution

0. Executive decision

Phase 4 discovery is accepted as PARTIAL and sufficient for decision-making.

No migration is allowed. No seed execution is allowed yet. No hardcoded seed list is allowed.

Opus must patch the Phase 4 implementation DRAFT into a safe implementation-prep prompt that GPT/User can review later.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-governance-vocab-discovery-report.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4-discovery-and-decisions-no-hardcode-2026-05-11.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/prompts/p3d-pack1-phase4-governance-vocab-species-prep-implementation-prompt-DRAFT.md

2. Mission

Patch or rewrite the Phase 4 implementation-prep prompt so it can later be reviewed for agent dispatch.

Target path:

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

Also create a short patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-implementation-prep-prompt-patch-report.md

3. Mandatory design decisions to encode

D1 — Vocab seed policy

Allowed only as live delta:

live discovery query → compute delta → seed only computed delta → report exact rows inserted

Forbidden:

INSERT fixed list copied from report/design/memory

The prompt must recompute missing:

  • vocab.unit_kind.* needed by active migration contract;
  • vocab.section_type.* from live TAC-used section types;
  • vocab.publication_type.* from live TAC-used publication types.

D2 — Species mapping policy

Allowed only if live resolution is unique:

  • target collections discovered live from collection_registry;
  • law species resolved live from entity_species;
  • use discovered species/composition fields, not typed constants.

STOP if zero or multiple plausible law species are found.

D3 — Parent/composition policy

  • Parent pointer mapping is approved for future Phase 5 design.
  • No universal_edges materialization in Phase 4.
  • composition_role must be deferred unless a live registry/contract source is found.

D4 — Hash provenance target

Use JSONB contract, not a new column:

unit_version.content_profile.source_hashes.tac_v1

Required conceptual fields for future migration:

algorithm
input_recipe
value
source_table
source_id

Do not backfill anything in Phase 4.

4. Hard boundaries for the DRAFT prompt

The prompt may prepare governance/vocab/species only, but must still be DRAFT until GPT/User approval.

Must prohibit:

  • TAC→IU migration;
  • collection_registry promotion to governed/active;
  • edge materialization;
  • birth-gate expansion;
  • direct species/composition enforcement at birth;
  • any hardcoded seed list;
  • any seed execution before GPT/User approval;
  • Qdrant/vector changes;
  • Nuxt/Directus changes.

5. Required safety gates in the DRAFT prompt

The implementation-prep prompt must include:

  1. read-only preflight and schema introspection;
  2. live delta recomputation;
  3. conflict checks for existing dot_config keys;
  4. unique law species resolution check;
  5. target collection resolution check;
  6. transaction-wrapped seed if later approved;
  7. rollback plan deleting only rows inserted by this pack;
  8. report all inserted rows;
  9. no hardcoded counts or fixed value lists.

6. Expected Opus final response

Return only:

  1. Patched implementation-prep prompt path.
  2. Patch report path.
  3. Top 7 no-hardcode safeguards added.
  4. What remains blocked.
  5. Whether GPT/User review is required before agent dispatch.

7. Status

phase4_discovery=ACCEPTED_PARTIAL
implementation_prep_prompt_patch_allowed=true
agent_dispatch_allowed=false_until_GPT_User_review
migration_allowed=false
hardcoded_seed_lists_forbidden=true
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase4-implementation-prep-no-hardcode-2026-05-11.md