KB-773D

10 — Remaining Blockers & Owner Decisions

3 min read Revision 1

10 — Remaining Blockers & Owner Decisions

Every remaining BLOCK now has a row/file-level cause and an exact next action.

BLOCK dimension → blocker → owner/action

# Dimension Residual Root cause Who unblocks Exact action
1a birth_orphan_critical_active 54 dot_iu_command_catalog triple-absent; no fitting species, no canonical code, governance role undecided Owner/taxonomy + Admin Decide species+role+code strategy (or classify EXEMPT/DEFERRED) → register via dot-dot-register → install trigger → backfill 54 (doc 02)
1b birth_orphan_critical_active 5 PIV-101/103/104/105/106 codes globally taken by pivot_results; birth_registry unique is on entity_code alone Owner/DB design Migrate unique → (entity_code, collection_name) + update trigger ON CONFLICT → re-run backfill (doc 03)
2 birth_phantom_real 6 COL-171/172/173, SPE-NRC/NRM/NRR: entity gone, birth row stranded; no retirement mechanism exists Owner Decide retire vs restore (recommend RETIRE — no restore signal); first define a governed retire path (doc 04)
3 fs_dot_file_no_registry 16 15 live operational scripts + dot-pivot-update; only lawful registration path is the credentialed registrar Admin Get dot-dot-register creds → register the 15 scripts; handle dot-pivot-update via full path (docs 05, 06)
4 dot_pivot_update_not_governed 1 staged file, unregistered, unborn, ungoverned Admin + Human L2/L4 Full lawful path: register → birth → governance → health → dry-run (doc 06)
governance_gate_ospa 0 (CLOSED) no ownership seeded Human L2/L4 Seed OSPA ≥ 1 (doc 07)

Credential / authority inventory

  • Present: root ssh, superuser psql (workflow_admin) → enables lawful DB remediation in scope.
  • Absent: admin credentials for the governed registrar dot-dot-register (Directus-API); human L2/L4 OSPA approval; owner taxonomy decisions; design sign-off for the constraint migration.

What is explicitly NOT a blocker for the work that was done

The pivot backfill (22 rows) needed none of the above — it used only the proven in-DB birth mapping on a fully-onboarded collection, which is why it was the one lawful mutation applied.

Back to Knowledge Hub knowledge/dev/reports/architecture/birth-orphan-backlog-remediation-gate-stage2-2026-06-03/10-remaining-blockers-and-owner-decisions.md