GPT Review — Birth / Species / Composition Concern before Phase 3

Date: 2026-05-11 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Context: User asked whether Pack 1 Phase 3 read-only hash/planner investigation should run as approved, or be adjusted after Opus raised birth/species/composition concerns.

Verdict

Do not run the previously approved Phase 3 investigation prompt unchanged.

Patch it first to include a read-only birth/species/composition alignment check.

Assessment of Opus report

Opus is directionally correct.

Confirmed / likely correct

1. fn_iu_create / fn_iu_create_plan is the canonical birth gateway for native information_unit / unit_version only.
2. Existing TAC rows were produced by the TAC pipeline and have not passed through the native IU birth gateway.
3. The current native IU birth path appears to enforce Tier 0 / strict core invariants, not full species/composition/enrichment behavior.
4. Species appears to be a higher-tier metadata/enrichment concern, connected to Đ29 / Đ24 / entity labels / DOT, not a fully enforced native IU birth-gate field today.
5. Composition/parent-child exists partially via fields such as parent_or_container_ref, but enforcement/edge materialization is not yet proven.
6. DOT enrichment tiers are not fully built for IU yet, so birth-created IU rows may be valid core records but incomplete as smart-data objects.

What is not yet certain

These require read-only verification before we make implementation decisions:

1. Exact 15 strict elements currently enforced by fn_iu_create / invariant checker.
2. Whether unit_kind is intended to replace, bridge to, or precede species.
3. Whether law_unit should be a first-class unit_kind or a species/label layered over another unit_kind.
4. Whether composition_role exists in identity_profile for current rows and how it is defaulted.
5. Whether parent_or_container_ref is validated or only stored.
6. Which tables currently hold species/entity-label metadata and whether IU rows are registered there.

Decision

The active Phase 3 investigation must be broadened from:

hash + planner

to:

hash + planner + birth/species/composition alignment

Still read-only. No DDL, no patch, no migration.

Why this matters

If we continue EVOLVE migration without verifying birth/species/composition alignment, we may move 86 TAC units into IU while preserving body/metadata but losing the semantic object contract expected by the broader system.

This is not a reason to block forever or rebuild birth now. It is a reason to verify the actual law/runtime state before deciding whether Phase 4 is migration, planner fix, species seeding, DOT enrichment, or some combination.

Updated next action

Patch Phase 3 read-only investigation prompt to rev3 and run that instead.

Status

old_phase3_prompt_rev2=DO_NOT_RUN_UNCHANGED
new_phase3_prompt_rev3_required=true
mode=READ_ONLY_INVESTIGATION_ONLY
migration_allowed=false