GPT Decision — One-Roof Governance + Anarchy Detection for Registries-Pivot

Date: 2026-06-01 Reviewer: GPT Council

Decision

All governance-related objects and actions must live under the central governance roof. Registries-Pivot must not create local governance. This applies to grouping, classification, threshold, label dimensions, registry pin, phantom definition, pivot coverage, Directus/API exceptions, render/display ownership, DOT scan/propose/apply/audit, cleanup workflow, and issue/event routing.

Key addition from user

The system must not rely on humans or future agents remembering governance principles. It must automatically detect "anarchic" objects/actions: anything that should be governed but has no central governance owner/approval/audit/issue path.

Recommended concept

Define governance-orphan / anarchic governance as a first-class system health condition.

A governed object is any object/policy/action/route/DOT/pivot/label/pin/phantom definition/change process that can affect system structure, classification, counting, display truth, execution authority, issue/notification, or cleanup.

A governance-orphan/anarchic object is a governed object that lacks one or more required central-governance links:

• owner_gov_code or central owner relation;
• capability_code;
• approval path when mutating/high-risk;
• audit path;
• rollback/retire path;
• DOT authority if executed by DOT;
• system_issue/event path if detected by scanner;
• law/design reference.

Reuse-first implementation direction

Do not build an isolated Registries-Pivot governance scanner. Extend the existing orphan/system-integrity pattern under GOV-SIV and Điều 31, with Điều 37 ownership rules and Điều 35 DOT execution.

Suggested central model:

• GOV-COUNCIL: policy owner and tie-breaker for cross-system policy definitions.
• GOV-SIV: health/integrity owner; owns governance-orphan detection, count-integrity, pivot coverage, orphan/phantom detection.
• GOV-DOT: execution owner for scan/propose/apply/audit DOTs.
• GOV-MOUT: render/display/API owner after activation/Đ28 ownership patch.

Required design patch

Before more UI work, patch Registries-Pivot design to include:

1. One-roof governance rule.
2. Governance-orphan/anarchy detection definition.
3. Governed object contract.
4. Governance coverage invariant.
5. Detection scanner/DOT lifecycle.
6. Issue/event routing for governance_orphan / local_governance_island / approval_path_gap / audit_gap / dot_authority_gap.
7. No local governance island rule.
8. Readiness gate: no new feature can reach production unless governance coverage passes or is explicitly exception-approved.

Immediate next macro

Run design-patch macro only: no PG mutation, no UI implementation. It should patch Registries-Pivot design and produce exact future implementation prompts for governance coverage scanner/DOTs.