KB-3E90

GPT Directive to Opus — P3D Pack1 Phase5 Prompt rev3 Registry Field Resolution

4 min read Revision 1
directiveopusp3dpack1phase5prompt-rev3registry-field-resolutionno-hardcode2026-05-11

GPT Directive to Opus — P3D Pack 1 Phase 5 Dry-Run Prompt rev3: Registry Field Resolution

Date: 2026-05-11 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Mode: PATCH DRY-RUN PROMPT ONLY — no execution

0. Verdict

Prompt rev2 is not approved for dispatch yet. It fixes TAC/IU field hardcode, but registry/species fields still bypass semantic resolution.

Patch to rev3.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase5-dryrun-prompt-rev2-not-approved-registry-field-gap-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5-readonly-dryrun-tac-to-iu-migration-prompt.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5-dryrun-prompt-rev2-field-adaptive-patch-report.md

2. Target outputs

Patch prompt in place:

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

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5-dryrun-prompt-rev3-registry-field-resolution-patch-report.md

3. Required rev3 fixes

3.1 Extend field-resolution to registry/species tables

Add semantic concepts or a parallel registry field-resolution section for:

species_identifier
species_display_label
species_composition
species_management_mode
species_parent
species_depth
collection_name_or_key
collection_governance_role
collection_migration_state
collection_species_code
mapping_collection_key
mapping_species_identifier
mapping_primary_flag
mapping_discriminator_field
mapping_discriminator_value
mapping_discriminator_operator
mapping_discriminator_config

Candidate labels may be listed, but only as candidates. Actual use requires live resolution.

3.2 Update GATE-0 resolved field map

GATE-0 must resolve concepts across:

entity_species
collection_registry
species_collection_map

with the same deterministic rule:

0 found → FIELD_ABSENT
1 found → RESOLVED
>1 found → AMBIGUOUS_FIELD

3.3 Patch G7

G7 must no longer say direct fields like:

composition_level
management_mode
governance_role

as if they are guaranteed columns.

Instead:

  • dump all entity_species rows with SELECT *;
  • if species_composition resolves, group by that resolved field;
  • if absent/ambiguous, set composition grouping to UNKNOWN;
  • if species_management_mode and collection_governance_role both resolve, compute deterministic governance match;
  • if absent/ambiguous, set match label to UNKNOWN;
  • all outputs remain candidate_not_approved.

3.4 Keep no broad restructure

Do not change overall goals, design decisions, or Phase 5 boundaries.

This is a targeted fix: extend the semantic registry discipline from TAC/IU fields to registry/species fields.

4. Hard boundaries

  • No agent dispatch.
  • No DB write.
  • No migration.
  • No seed.
  • No backfill.
  • No DDL.
  • No function/trigger patch.
  • No species/composition decision locked.

5. Expected Opus response

Return only:

  1. Patched prompt path.
  2. Patch report path.
  3. Top 5 fixes from rev2.
  4. Confirmation no design/migration decision was locked.
  5. Confirmation GPT/User review required before dispatch.

6. Status

phase5_dryrun_prompt_rev2=not_approved
phase5_dryrun_prompt_rev3_patch_allowed=true
agent_dispatch_allowed=false
migration_allowed=false
seed_allowed=false
backfill_allowed=false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase5-dryrun-prompt-rev3-registry-field-resolution-2026-05-11.md