KB-6252

GPT Directive to Opus — P3D Pack1 Phase4C Prompt rev3 Field-Adaptive No Fuzzy

4 min read Revision 1
directiveopusp3dpack1phase4cprompt-rev3no-hardcodefield-adaptive2026-05-11

GPT Directive to Opus — P3D Pack 1 Phase 4C Prompt rev3: Field-Adaptive, No Fuzzy Selectors

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 fixed species selector hardcode, but field-level hardcode and fuzzy selector language remain.

Patch to rev3.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4c-prompt-rev2-not-approved-field-hardcode-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4c-readonly-dryrun-species-mapping-qt001-prompt.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4c-prompt-rev2-no-hardcode-selector-patch-report.md

2. Target outputs

Patch prompt in place:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4c-readonly-dryrun-species-mapping-qt001-prompt.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4c-prompt-rev3-field-adaptive-no-fuzzy-patch-report.md

3. Required rev3 fixes

3.1 Top-level scope preflight

Add preflight goal/check to verify:

  • information_unit table exists;
  • unit_version table exists;
  • both scoped collections exist in collection_registry;
  • information_unit.unit_kind exists before using discriminator logic;
  • vocab.unit_kind.law_unit exists in dot_config if referenced as committed contract.

If a scoped target is absent, status becomes BLOCKED. If only unit_kind is absent, discriminator strategy collapses but other dry-run may continue.

3.2 Field-adaptive G3

Do not require fixed fields such as display_name, prefix, parent_id, depth.

Use:

  • all columns from entity_species verbatim;
  • semantic field presence map: which of [code, species_code, display_name, species_name, name, composition_level, management_mode, prefix, parent_id, depth] exist;
  • if a semantic field is absent, report FIELD_ABSENT.

3.3 Remove fuzzy “subordinate-like”

Replace with deterministic exact comparison:

  1. read the scoped subordinate collection row from collection_registry;
  2. extract its exact birth_code_strategy value if the column exists;
  3. use that exact value to find other collections with the same strategy;
  4. if the column is absent, report STRATEGY_FIELD_ABSENT and skip.

No “subordinate-like” inference.

3.4 Deterministic plausibility labels

G8/G9 candidates must be labelled by deterministic rules:

PLAUSIBLE       = required fields present and no direct conflict detected
CONFLICT        = direct governance/composition conflict detected from fields that exist
UNKNOWN         = required comparison field absent or ambiguous

Never silently exclude a candidate. If a candidate cannot be evaluated, include it with UNKNOWN.

3.5 Self-audit wording

Clarify:

  • Live species names/codes may appear in outputs.
  • Forbidden: using names/codes from memory or prompt as selectors.

4. Hard boundaries

  • No agent dispatch.
  • No DB write.
  • No seed.
  • No backfill.
  • No migration.
  • No DDL.
  • No function patch.
  • No species decision locked.
  • No 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 recommendation was locked.
  5. Confirmation GPT/User review required before dispatch.

6. Status

phase4c_prompt_rev2=not_approved
phase4c_prompt_rev3_patch_allowed=true
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase4c-prompt-rev3-field-adaptive-no-fuzzy-2026-05-11.md