GPT Review — P3D Pack 1 Phase 5 Dry-Run Prompt rev2 Not Approved: Registry Field Gap

Date: 2026-05-11 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed:

• knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5-readonly-dryrun-tac-to-iu-migration-prompt.md rev2
• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5-dryrun-prompt-rev2-field-adaptive-patch-report.md
• prior GPT directive for Phase 5 prompt rev2

Verdict

Prompt rev2 is NOT approved for Agent dispatch yet.

Rev2 is a major improvement and the semantic candidate field registry is the correct structural pattern. However, it only covers TAC/IU source-target fields. The prompt still directly references registry/species fields in G7 without equivalent field resolution.

This is the same no-hardcode problem, now moved from TAC/IU fields to registry fields.

What rev2 fixed well

1. Introduced a semantic candidate field registry.
2. Replaced "or similar" with deterministic resolution: FIELD_ABSENT, RESOLVED, AMBIGUOUS_FIELD.
3. Converted body/hash/provenance references into semantic concepts.
4. Removed Agent interpretation of "simplest" / "allows containment".
5. Bounded G8/G9 function and trigger output.
6. Added UNREGISTERED_FIELD concept.
7. Preserved read-only/dry-run boundaries.

Remaining blocker

Registry/species fields still bypass semantic resolution

G7 directly uses or assumes fields such as:

composition_level
management_mode
governance_role

It also says:

query ALL distinct composition_level values from entity_species
management_mode matches target governance_role

But these concepts are not in §0.1 semantic registry, and no deterministic resolution rule exists for entity_species or collection_registry fields.

Earlier phases already showed why this matters: entity_species.species_name did not exist. Field names in registry tables must be treated with the same discipline as TAC/IU fields.

Required patch

Patch prompt to rev3.

Add either:

Option A — extend §0.1 semantic registry

Add registry concepts 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

and include tables to check:

entity_species
collection_registry
species_collection_map

Then update G7 to reference concept IDs only.

Option B — add a separate registry field-resolution section

Equivalent to §0.1, but dedicated to registry/species tables. It must use the same deterministic rule:

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

Additional rev3 requirement

G7 must not use composition_level, management_mode, or governance_role as required literal columns. It must say:

• if species composition concept is FIELD_ABSENT, species/composition grouping is UNKNOWN;
• if management/governance concepts are absent or ambiguous, PLAUSIBLE grouping becomes UNKNOWN, not guessed;
• all live species rows should still be dumped with SELECT * for evidence.

Status

phase5_design=ACCEPTED_DIRECTIONALLY
phase5_dryrun_prompt_rev2=NOT_APPROVED_FOR_DISPATCH
reason=registry_species_fields_bypass_semantic_resolution
agent_dispatch_allowed=false
migration_allowed=false
seed_allowed=false
backfill_allowed=false
next_action=OPUS_PATCH_PHASE5_DRYRUN_PROMPT_REV3_REGISTRY_FIELD_RESOLUTION