KB-6957

GPT Directive to Opus — P3D Pack1 Phase4B Species Composition Registry Alignment

5 min read Revision 1
directiveopusp3dpack1phase4bspeciescompositionregistry-alignment2026-05-11

GPT Directive to Opus — P3D Pack 1 Phase 4B Species/Composition Registry Alignment

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 DISCOVERY PROMPT ONLY

0. Executive decision

Phase 4 vocab prep is PASS and accepted. The vocab gate is open for law_unit.

However, TAC→IU migration remains blocked until species/composition registry alignment is understood or explicitly deferred with traceability.

Open:

P3D_PACK1_PHASE4B_SPECIES_COMPOSITION_REGISTRY_ALIGNMENT

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4-v7-vocab-pass-and-next-directive-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-vocab-species-seed-implementation-report.md
knowledge/dev/laws/dieu44-trien-khai/followups/p3d-pack1-species-composition-registry-alignment-anchor-2026-05-11.md
knowledge/dev/architecture/species-taxonomy-complete.md
knowledge/dev/architecture/composition-level-law.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase3-hash-planner-birth-alignment-investigation-report.md

2. Mission

Create a Phase 4B design and a read-only discovery prompt to reconnect IU/TAC migration with the older registry/species/composition universe.

Do not seed, migrate, or patch functions.

3. Required outputs

3.1 Design

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4b-species-composition-registry-alignment-design.md

Required sections:

A. Why Phase 4B is needed
B. Existing pre-TAC registry/species/composition model
C. Current IU/TAC gaps from Phase 3 and Phase 4
D. Birth core vs registry alignment vs DOT enrichment distinction
E. Species mapping policy options
F. Composition-level / atom-to-building policy options
G. Birth registry policy options
H. Parent-child/edge implications
I. No-hardcode contract for species/composition
J. Recommendation and migration gate impact

3.2 Read-only discovery prompt

Create:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4b-readonly-species-composition-registry-discovery-prompt.md

The prompt must:

  • introspect entity_species columns before selecting fields;
  • introspect species_collection_map columns before querying mappings;
  • introspect collection_registry, birth_registry, entity_labels, universal_edges columns before deeper queries;
  • discover existing species/composition values from live registry, not fixed names/counts;
  • report IU/UV/TAC mapping candidates only;
  • label all counts as snapshots;
  • avoid fuzzy matching for executable policy; fuzzy matching may be candidate-only and labelled as such.

3.3 Report

Create:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4b-species-composition-design-and-discovery-prompt-report.md

Required fields:

phase_status=PASS|PARTIAL|BLOCKED
mode=DESIGN_AND_READONLY_PROMPT_ONLY
phase4_vocab_status=PASS_ACCEPTED
migration_allowed=false
species_seed_allowed=false
composition_seed_allowed=false
no_hardcode_contract=included|missing
read_only_prompt_created=true|false
next_required_action=GPT_REVIEW_PHASE4B_DESIGN_AND_PROMPT

4. Hard boundaries

  • No seed.
  • No migration.
  • No DDL.
  • No function/trigger patch.
  • No species_collection_map insert.
  • No birth_registry write.
  • No entity_labels write.
  • No universal_edges write.
  • No Directus/Nuxt/Qdrant.
  • No hardcoded species count, layer count, or composition value.

5. Key design rule

The final IU birth/migration system must not create a separate birth universe.

Birth should enforce core invariants. Species/composition should be resolved through registry contracts and/or DOT enrichment, not guessed or hardcoded in the birth function.

6. Final response expected from Opus

Return only:

  1. Design path.
  2. Read-only discovery prompt path.
  3. Report path.
  4. Top 7 design questions/decisions.
  5. Whether GPT/User review is required before any agent dispatch.

7. Status

phase4_vocab_prep=PASS_ACCEPTED
phase4b_design_allowed=true
agent_dispatch_allowed=false_until_GPT_USER_REVIEW
migration_allowed=false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase4b-species-composition-registry-alignment-2026-05-11.md