KB-135A

00 — Overview & Control: Governance Alignment Follow-up Fact-Finding (Registries-Pivot)

6 min read Revision 1
governanceregistries-pivotfact-findingread-onlydieu372026-06-01

00 — Overview & Control

Mission: GOVERNANCE_ALIGNMENT_FOLLOWUP_FACT_FINDING_FOR_REGISTRIES_PIVOT Class: narrow read-only fact-finding. No design patch. No implementation. Run date: 2026-06-01 · Host: contabo VPS · DB: directus (Docker postgres, PG 16.13). Read channel: Agent-Data/Incomex KB + live PG read-only (context_pack_readonly) + enacted law text. Apply channel: KB report only. Zero PG / Directus / Qdrant / Nuxt mutation.

Follows the completed audit …/full-stack-governance-alignment-audit-registries-pivot-grouping-2026-05-31/ (17 docs) + the GPT review (gpt-review-…-2026-06-01) + GPT direction (gpt-direction-…-2026-05-31). Its open points (GPT review §"Open points needing more evidence") are exactly Q1–Q7 below; this package closes them against live PG, not prior assertions.


Hard Gate 0 — result: PASSED

# Check Result
1 KB read access mcp__…_Incomex_KB__* list/batch_read/search working (17-doc prior pack confirmed)
2 Live PG read-only access query_pg AST-validated, READ ONLY tx, 5s timeout, LIMIT 500
3 Read-only role current_user = session_user = context_pack_readonly
4 No apply channel ✅ only query_pg (read-only) + KB; no ssh / docker exec available or used
5 No mutation ✅ SELECT / information_schema / pg_catalog only
6 Fact-finding only, not design-patching ✅ no design doc modified; this is a new evidence package
7 All conclusions evidence-backed ✅ ~30 live queries; every verdict cites a live value

The four governance owners — live status (one-line each)

Code gov_type status domain created_by_law relations edges capability
GOV-COUNCIL council active governance NRM-LAW-37 (Đ37) owner→Đ37, approver_tbox→Đ39 NULL
GOV-SIV system active monitoring.integrity NRM-LAW-31 (Đ31) owner→Đ31 NULL
GOV-DOT system active monitoring.dot NRM-LAW-35 (Đ35) owner→Đ35, owner→Đ36 NULL
GOV-MOUT factory/mother draft assembly.output NRM-LAW-07 (Đ7) none {can_create:[design_templates]}

(Full registry: 9 agencies — 5 active [GOV-COUNCIL, GOV-SIV, GOV-DOT, GOV-KG-SYS, GOV-NRM-SYS] + 4 draft factory mothers [GOV-MOIT, GOV-MOT, GOV-MOUT, GOV-MOW].)


Headline verdict

The recommended federated model (POLICY→GOV-COUNCIL, HEALTH→GOV-SIV, DOT→GOV-DOT, RENDER→GOV-MOUT) is PARTIALLY implementable now. Three of its four owners (Council, SIV, DOT) are live, active, law-backed, and DOT-equipped and can be assigned their roles via the existing Đ32 approval spine + Đ37 §4.12(d) Council minute — no new agency, no per-table gov columns (the GPT-direction's owner_gov_code field set exists on zero tables system-wide; ownership is recorded relationally). The render owner (GOV-MOUT) is the weak link: it is still draft, has zero relation edges, and is born of the Assembly law (Đ7), not the Display law (Đ28) — and Đ28 itself is agency-orphaned. Separately, three policy objects (threshold, phantom, pin) still have no law home, the direct-PG API exception is unratified and un-ledgered, and the governance audit loop is not closing (governance_audit_log = 1 stale row).

Verdict summary (detail in docs 01–10)

Q Topic Verdict
Q1 GOV-SIV GOV_SIV_READY (active; usable for count-integrity/orphan/drift/verification today; pivot-coverage + phantom need scope-extension approval/law-patch)
Q2 GOV-MOUT GOV_MOUT_DRAFT_OR_INCOMPLETE (draft mother, no edges, born of Đ7 not Đ28; Đ28 agency-orphaned; no agency owns display/API/render today)
Q3 GOV-COUNCIL GOV_COUNCIL_NEEDS_CAPABILITY_PATCH (assignor authority §4.12(d) READY now; classification policy assignable now; threshold/phantom/pin need law clauses first)
Q4 GOV-DOT GOV_DOT_READY (active; Đ35 A/B tiering + ops + pairing fully reusable; only additive gap = author grouping/pivot DOTs + coverage rows)
Q5 Audit spine USE_EXISTING_AUDIT_SPINE_INSTEAD for operational change-logs (registry_changelog 68k + event_outbox 180k + system_issues); governance_audit_log = structurally ready but DORMANT (1 row) for ownership minutes
Q6 Approval spine APPROVAL_SPINE_READY for object changes (reclassify/rule_change/schema_add/new_dot + create/update/add_field handlers); exception: law-clause enactment (amend_law/enact_nrm) handlers are RESERVED/unimplemented → law patches need council_review + manual enact
Q7 Direct-PG API DIRECT_PG_EXCEPTION_UNRATIFIED_BLOCKER (no approval, no vps_deploy_log entry, host law Đ41 enacted but agency-orphaned); long-term fix = ratify read-only adapter under Đ41 or add view PK + route via Directus

Model implementable now? PARTIAL. Confirmed-assignable today: GOV-SIV (health), GOV-DOT (execution), GOV-COUNCIL (classification policy + assignor). Blocked/needs-patch: GOV-MOUT activation + Đ28 ownership; threshold/phantom/pin law clauses; direct-PG ratification; governance-audit activation.

Package contents

00 control · 01 GOV-SIV · 02 GOV-MOUT · 03 GOV-COUNCIL · 04 GOV-DOT · 05 audit spine · 06 approval spine · 07 direct-PG exception · 08 capability gap matrix · 09 issue/event type gap · 10 design impact + recommendation · 11 next actions · 12 self-review.

Forbidden-compliance statement

No PG mutation · no Directus mutation · no Qdrant/vector write · no Nuxt/UI implementation · no route change · no law enactment · no approval creation · no self-approval · no new governance owner created · no table created · no schema change · no event/job/notification emit · no hardcode · no design doc patched. All findings evidence-backed from live PG + enacted law.

Back to Knowledge Hub knowledge/dev/reports/architecture/governance-alignment-followup-fact-finding-registries-pivot-2026-06-01/00-overview-control.md