13 — Next-Agent Prompt (consume results, no rediscovery)

Paste the following as the next macro. It assumes the safety net is already LIVE and does not re-discover channels or schema.

---

MACRO: BIRTH_ORPHAN_BACKLOG_REMEDIATION_AND_GATE_STAGE2_2026-06-XX

You are the production architecture/governance Agent for Agent Data. The minimum safety net is
ALREADY LIVE in prod `directus` (applied 2026-06-03). Do NOT re-author it. Live evidence wins.

CHANNELS (verified): query_pg(directus)=read-only; ssh contabo (root) → docker exec postgres
psql -U workflow_admin -d directus = superuser rw. read_file denies /opt/incomex/dot/bin (use ssh).

START:
1. Re-run the gate: ssh contabo 'bash -s' < operator_bundle/05_run_rp_dot_preflight_guard.sh
   Confirm the 4 BLOCK dimensions and current counts. Re-load fs snapshot first (03_load).
2. Read docs 05 (triage), 06 (gate readiness), 07 (OSPA packet), 11 (RP decision) of
   knowledge/dev/reports/architecture/birth-orphan-safety-net-operator-apply-backlog-triage-2026-06-03/.

GOAL — clear the four guard BLOCK dimensions LAWFULLY, then reconsider RP GO:
  A. dot_iu_command_catalog (54 unborn, triple-absent): DESIGN + (on owner-go) apply collection
     onboarding — register in collection_registry + meta_catalog(identity_class managed) + birth
     code strategy + birth trigger. Then birth its 54 rows via the lawful path. NEVER fabricate.
  B. pivot_definitions (27 unborn, 26 active): birth via lawful DOT (dot-pivot-declare/birth path).
     NEVER manual INSERT/UPDATE. Needs admin creds for the governed registrar (currently absent).
  C. 6 REAL_MISSING births (COL-171/172/173 collection_registry; SPE-NRC/NRM/NRR entity_species):
     owner decision — RETIRE stale birth rows or restore entities.
  D. 16 FILE_NO_REGISTRY scripts (incl dot-pivot-update): register via governed dot-dot-register
     (admin creds needed) or quarantine+accept in _preflight_accepted_exceptions. Do NOT register/
     execute dot-pivot-update outside the lawful governed route.

THEN (only after A–D zero): consider birth-gate Stage 2 (app.birth_gate_mode='blocking' for
dot_tools+collection_registry), with proven rollback (SET …='warning').

SEPARATELY (human L2/L4): OSPA seeding (ospa≥1) to open governance L2 rollout (doc 07 packet),
and/or authorize the read-only governance row-bridge views (P5, not yet applied).

FORBIDDEN: fabricate birth rows; manual pivot/dot_tools mutation; register/exec dot-pivot-update
outside governed route; delete/hide backlog; enable global blocking while backlog unknown;
disable triggers; bypass gate. RP cleanup stays NO-GO until the guard passes.

BLOCKERS likely to persist: admin creds for dot-dot-register (absent); human owner decisions for
C; human L2/L4 for OSPA. If blocked, extend the triage ledger and produce the exact owner/cred ask.

---

Quick re-orient facts for the next agent

• Live detector objects: v_birth_orphan, v_birth_phantom, v_birth_coverage_status, v_dot_fs_reconciliation, v_dot_registry_no_file, v_dot_pivot_update_status, fn_preflight_guard(), fn_assert_safe_for_dot_action(), _recon_dot_fs_inventory, _preflight_accepted_exceptions.
• Rollback: operator_bundle/99_rollback_minimum_safety_net.sql.
• Optional ledger view (not applied): operator_bundle/v_birth_backlog_triage.sql.