P3D Pack 1 Phase 5C2 — rev2 Complete Schema Concepts Patch Report

Date: 2026-05-12 Author: Opus (Claude) Patched: rev1 → rev2

---

Top 6 rev2 fixes

1. Added 12+ missing concepts to §3 registry

Rev1: §3 had 16 concepts. Executable sections used p.<doc_code col>, row.<owner col>, <identity_profile col>, birth_registry columns — none declared in registry.

Rev2: §3 expanded to ~30 concepts across 4 groups (3A source, 3B target, 3C governance, 3D verification). Every column used in executable SQL is now traceable to a declared concept. New concepts include: tac_pub_doc_code, tac_pub_publication_type, tac_lu_owner_ref, iu_identity_profile, iu_pk, iu_canonical_address, uv_pk, birth_entity_ref, birth_species_identifier, birth_collection_key, birth_composition, birth_pk.

2. All executable references use resolved concepts

Rev1: Mixed — some used <config_key>, some used literal canonical_address, identity_profile, etc.

Rev2: Every executable SQL reference replaced with concept placeholder. Examples: p.<tac_pub_doc_code>, row.<tac_lu_owner_ref>, <iu_identity_profile>, <birth_collection_key>. Zero literal column names in executable sections except table names (which are scope-block constants, not schema-sensitive).

3. Birth registry verification strengthened (D4a–D4d)

Rev1: Single check — species IS NULL count = 0.

Rev2: Four checks:

• D4a: birth row count for captured IDs = inserted_iu_count (existence)
• D4b: null species count = 0 (non-null)
• D4c: species value = information_unit_atom (correctness)
• D4d: composition value = atom if concept resolved; UNKNOWN + GPT flag if FIELD_ABSENT (graceful handling)

4. fn_iu_create shape discovery clarified

Rev1: "Use fn_iu_create_plan if available, else SAVEPOINT."

Rev2: Explicit requirement: after SAVEPOINT test, verify 0 residual rows exist (including birth_registry side effects). If residual rows remain or shape cannot be determined → ABORT to GPT. No silent continuation with uncertain shape.

5. Authority vocab lookup uses resolved concepts

Rev1: G0-10 referenced dot_config but mixed resolved/literal column names.

Rev2: G0-10 explicitly uses <config_key> and <config_value> — both resolved from §3C.

6. Concept resolution verification step (§3D)

Rev1: No explicit verification summary.

Rev2: §3D requires Agent to produce a concept_name → table → resolved_column → resolution_status summary table. Any FIELD_ABSENT or AMBIGUOUS_FIELD on required concept → ABORT before write. Added concept_registry_fully_resolved to final response format.

---

What stayed the same

• D3a hybrid, atomic IU, hierarchy in identity_profile JSON
• fn_iu_create as canonical writer
• Single transaction + advisory xact lock
• 12 GATE-0 checks + 8 preflight checks
• Verify-before-COMMIT (now 8 D-assertions instead of 7)
• Post-COMMIT render fidelity RF-1..4
• Exact-key rollback, no pattern matching
• TAC NEVER written
• incomex_council authority value unchanged

---

Status

phase5c2_prompt_rev=2
concepts_declared=~30
concepts_used_without_declaration=0
birth_verification_checks=4 (existence + non-null + value + composition)
fn_iu_create_shape_residual_check=explicit
dispatch_status=CANDIDATE_PENDING_GPT_FINAL_REVIEW
agent_dispatch_allowed=false
migration_allowed=false_until_APPROVED
next_action=GPT_FINAL_REVIEW_5C2_REV2

---

Phase 5C2 rev2 Patch Report | Complete schema concepts | 2026-05-12