GPT Status — Return to P3D Birth System Mainline — 2026-05-14

Context

Work temporarily diverted from P3D Birth System Completion to GPT/VPS MCP connector instability and then to dot-dot-health scheduler reuse/audit. Connector is currently healthy. Mainline returns to birth system completion.

High-level status

Birth system completion is substantially advanced but not complete.

Completed / accepted evidence

• B3-P policy storage: PASS. collection_registry has coverage policy fields populated for governed collections.
• B3-A trigger wiring: PASS after B3-A3 + B3-A4. All BIRTH_REQUIRED ∩ IN_SCOPE collections have accepted birth triggers; birth_registry exempted from self-birth recursion; sibling function policy materialized.
• B3-F0 dry-run: PASS after sibling policy materialized in dot_config.
• B3-F1b soft gate: LIVE in PG on collection_registry.
• B3-F1c-b full-scan function: installed in PG.
• B3-F1c-c/d Agent Data / Directus Flow scheduler path: paused after discovery of existing dot-dot-health generic executor.
• B3-F1c-e probe: dot-dot-health reuse viable only with wrapper function, but scheduler is currently broken.
• B3-F1c-f audit: PARTIAL accepted as evidence. Root cron runs dot-dot-health --local; script rejects --local, so existing scheduler is unreliable. Agent accidentally inserted 7 system_issues rows by sourcing script; no cleanup approved.

Core birth capabilities completed

• Species mapping gaps resolved to 0 during B3-A progression.
• Trigger coverage for BIRTH_REQUIRED ∩ IN_SCOPE resolved to 0 missing valid triggers.
• Birth registry self-recursion risk handled by exemption/policy, not trigger.
• Variant sibling function scope materialized in dot_config.
• Soft onboarding gate installed to detect registry mutations.
• Full-scan PG function exists for periodic detection, but automatic scheduling is not complete.

Known incomplete areas

• B3-F1c automation is blocked until dot-dot-health scheduler repair.
• dot-dot-health has hardcoded jurisdiction NRM-LAW-35-V5P2 and registry drift; wrapper/row design must wait until scheduler repair review.
• B3-A-DUP duplicate trigger cleanup remains deferred.
• B3-DESC description_policy unclassified workstream remains deferred.
• B3-F hard/soft progression beyond current soft gate/full scan scheduling remains incomplete.
• Entity Living DB / enrichment-layer placeholders need a focused verification pass against the original architecture design and live schema.
• Phase 5C2 information-unit migration remains paused; TAC UI remains preserved.

Next recommended action

Use Claude Code CLI xhigh / Opus to draft a focused continuity review: B3-MAINLINE-RESUME Birth System Completeness Verification.

The review should verify:

1. six composition layers and species taxonomy status;
2. 8 standard relationship hooks/placeholders;
3. Entity Living DB metadata/profile placeholders;
4. enrichment-layer placeholders for vector/Pivot/similar/peers/transitive downstream;
5. B3-F1c-g scheduler repair design status;
6. remaining workstream ranking before returning to Phase 5C2.

Governance flags

phase5c2_migration_allowed=false
ui_cutover_allowed=false
b3f_complete_allowed=false
wrapper_design_allowed=false_until_scheduler_repair_review
system_health_checks_insert_allowed=false
connector_currently_healthy=true
next_recommended_action=OPUS_CLAUDE_CODE_XHIGH_MAINLINE_COMPLETENESS_REVIEW