GPT Decision — Expand Birth/Governance Automation Audit to Orphan Detection

Date: 2026-06-03 Reviewer: GPT Council

Verdict

The proposed audit must be expanded. The key risk is not merely whether dot-pivot-update has a birth record. The deeper constitutional requirement is: every new object must be automatically born or immediately detectable as an orphan/unborn object; if already born, governance onboarding/backfill must automatically detect whether it is governance-covered or a governance orphan. If a new object can exist outside both birth and orphan detection, the birth/governance control system has a systemic hole.

Required audit expansion

The next Agent prompt must test four surfaces:

1. Automatic birth enforcement: new DB/catalog/DOT entities must get birth records through the official system.
2. Unborn/orphan detection: objects created outside the birth path must be detected, labelled, and prevented from silently operating.
3. Governance onboarding/backfill: born governance objects must enter coverage/candidate/gap detection automatically or be explicitly blocked as not-live.
4. Bypass resistance: manual, file-only, direct DB, Directus, and DOT script paths must be audited so intentional mistakes are blocked or caught.

Decision

Pause RP/DOT update progress. Run a root audit that answers: can any object appear in the system without birth, without orphan label, and without governance onboarding? If yes, identify the exact hole and produce hardening patches before continuing DOT registration/cleanup.