P3D Pack 1 Phase 5 — Dry-Run Prompt rev3 Registry Field Resolution Patch Report

Date: 2026-05-11 Author: Opus 4.7

---

Status flags

phase5_dryrun_prompt_rev3_status=PATCHED
registry_species_fields_in_semantic_registry=true
g7_uses_concept_ids_not_field_names=true
gate0_includes_registry_tables=true
no_direct_field_references_remaining=true
requires_GPT_User_review_before_dispatch=true

Paths

Prompt rev3: ...prompts/p3d-pack1-phase5-readonly-dryrun-tac-to-iu-migration-prompt.md (rev 7)
Report:      ...reports/p3d-pack1-phase5-dryrun-prompt-rev3-registry-field-resolution-patch-report.md

3 changes from rev2

1. §0.1 registry extended with 16 registry/species concepts — species_identifier, species_display, species_composition, species_management, species_hierarchy_parent, species_hierarchy_depth, collection_key, governance_role, migration_state, birth_strategy, mapping_primary, disc_field, disc_value, disc_operator, disc_config, birth_entity. Each has candidate labels + tables to check. Same deterministic resolution rule (0=ABSENT, 1=USE, >1=AMBIGUOUS).

2. GATE-0 Phase 1 extended — P8b-P8e verify registry tables exist: entity_species, species_collection_map, collection_registry, birth_registry. Fail → STOP (same as source/target tables).

3. G7 rewritten to use concept IDs — composition_level → species_composition concept. management_mode → species_management concept. governance_role → governance_role concept. Each must be RESOLVED before use; if ABSENT/AMBIGUOUS → that dimension = UNKNOWN. Agent groups and labels but does NOT interpret.

What this fixes

rev2 had direct field references in G7: composition_level, management_mode, governance_role. These bypassed the semantic registry — same pattern as species_name (which didn't exist). rev3 routes ALL field references through the concept registry, including registry/species table fields.

Confirmation

phase5_dryrun_prompt=REV3_READY_FOR_GPT_REVIEW
next_action=GPT_REVIEW_PHASE5_DRYRUN_PROMPT_REV3