Follow-up Anchor — P3D Pack 1 Species/Composition Registry Alignment

Date: 2026-05-11 Source: User concern during P3D Pack 1 Phase 4 after vocab prep dispatch Status: MUST RETURN AFTER VOCAB PREP REVIEW

Why this anchor exists

The User raised a structural concern: TAC is recent, but before TAC the system already had registry/species/composition-level infrastructure, including species and composition layers from atom upward. If IU birth/migration ignores that older registry universe, the system will again produce multiple incompatible birth styles.

This concern is accepted as valid.

Current evidence

• P3D Phase 3 investigation found native IU birth currently enforces Tier-0/core only.
• information_unit / unit_version are in collection_registry but still observed/pilot and not fully species/composition wired.
• species_collection_map lacks IU/UV mapping.
• birth_registry IU rows have NULL species/composition values.
• entity_labels has no IU/UV labels.
• TAC tables are outside the birth_registry/species_collection_map/collection_registry universe.
• Phase 4 v7 vocab prep has now committed IU vocab keys, but species/composition alignment is still unresolved.

Principle

The final IU birth/migration system must not create a separate birth universe.

It must align with existing registry/species/composition infrastructure using registry-driven discovery, not hardcoded species/layer values.

Required future work

Open a dedicated pack after vocab prep review:

P3D_PACK1_PHASE4B_SPECIES_COMPOSITION_REGISTRY_ALIGNMENT

Purpose:

1. Introspect live entity_species schema before querying species fields.
2. Re-run species candidate discovery safely after entity_species.species_name mismatch found in v7 Section D.
3. Determine how IU/UV collections should map into species_collection_map.
4. Determine how composition_level should be resolved from registry, not hardcoded.
5. Decide whether species/composition are birth-gate requirements, birth_registry fields, post-birth DOT enrichment, or staged policy.
6. Keep TAC→IU migration blocked until this is explicitly reviewed or intentionally deferred with traceability.

Hard constraints

• No hardcoded species counts.
• No hardcoded layer counts.
• No hardcoded subordinate / atom / molecule / building values in executable logic.
• No fuzzy species matching for production seed.
• All species/composition values must be derived from authoritative live registry or reviewed contract.

Status

vocab_prep=PASS_COMMITTED
species_composition_alignment=OPEN
migration_allowed=false_until_review_or_explicit_deferral
next_recommended_pack=P3D_PACK1_PHASE4B_SPECIES_COMPOSITION_REGISTRY_ALIGNMENT