Opus Review — Birth Coverage Classification PARTIAL — B3 Decisions Needed

Date: 2026-05-12 Report: reports/p3d-birth-coverage-classification-report.md

---

Agent compliance: PASS

12/12 output fields. 6 phases. Discovery-first. Compiled SQL logged. Weighted evidence (governance_role + schema shape + FK/PK profile + species mapping + birth rows + naming). 0 mutation.

---

Classification results

Status	Count	Description
BIRTH_REQUIRED	43	Primary entities needing trigger — B3 target
EXEMPT_JUNCTION	20	M2M junction tables — no own identity
EXEMPT_SYSTEM_LOG	11	Log/audit/changelog — append-only
EXEMPT_DERIVED_CACHE	4	Views/computed/derived
DEFERRED_NEEDS_REVIEW	58	Needs GPT/User decision
Total	136

---

5 decisions GPT needs for B3

1. 43 BIRTH_REQUIRED → immediate B3 trigger target

Agent identified 43 governed collections with own PK + business columns that should have birth trigger. B3 prompt will design bulk trigger installation for these.

2. 48 "excluded" collections → need explicit policy

48 collections have governance_role=excluded — fell to DEFERRED because the 5-status taxonomy lacks "user-excluded" status. Agent identified 2 sub-clusters:

• CMS content (GRP-CMS, ~20): block_*, pages, posts, categories, etc. Likely permanently exempt (Antigravity CMS, not Incomex business logic).
• Agency OS business (GRP-BUSINESS, os_*, ~28): os_deals, os_invoices, os_tasks, etc. Likely promote to BIRTH_REQUIRED when Agency OS enters governance.

Recommendation: Add 6th status BIRTH_EXEMPT_USER_EXCLUDED for CMS. Promote Agency OS to BIRTH_REQUIRED or keep DEFERRED until Agency OS governance activates.

3. 7 missing tables → cleanup pass

Registry rows exist for: billing, blocks, help, kb_audit_log, kb_documents_history, sales, website — but no physical tables. Need: DELETE orphan registry rows OR CREATE tables.

4. Hook tables (entity_labels, universal_edges) → birth trigger needed?

• entity_labels classified JUNCTION (6 cols, M2M purpose). But it's a design v3 hook table with 118,933 rows and existing birth_registry entries.
• universal_edges classified DEFERRED (2,617 birth rows, rich metadata).

Question: Do hook tables birth when a junction row is created? Or do they inherit birth from the source entity? If they need own trigger → move to BIRTH_REQUIRED.

5. unit_version → confirm subordinate policy

Classified DEFERRED. Current P3D IU policy = subordinate (no own birth trigger). Agent correctly flagged for confirmation.

---

Updated coverage picture

Already have trigger:     29 collections
BIRTH_REQUIRED (B3):      43 collections
TRUE EXEMPT:              35 collections (junction + log + cache)
DEFERRED (GPT decision):  58 collections (48 excluded + 7 missing + 3 special)
                          ─────────
Total governed:           165 (136 uncovered + 29 covered)

Note: 165 not 166 — 1 discrepancy may be from join dedup. Agent's 136 is authoritative.

---

Proposed B3 scope

After GPT decides:

B3-A: Bulk trigger installation for 43 BIRTH_REQUIRED
B3-B: Cleanup 7 missing-table registry rows
B3-C: birth_owner_ref column design + DDL (from B2 contract)
B3-D: Policy for 48 excluded (CMS exempt vs Agency OS deferred)
B3-E: Hook table trigger decision (entity_labels, universal_edges)

---

Status

classification = PARTIAL (DEFERRED bucket needs GPT decisions)
b3_immediate_target = 43 collections
phase5c2_migration_allowed = false
next_action = GPT_DECIDE_5_QUESTIONS → B3_DESIGN

---

Opus Review | Classification PARTIAL | B3 Decisions Needed | 2026-05-12