GPT Review — Full-Stack Governance Audit for Registries-Pivot: Model Recommendation (2026-06-01)
GPT Review — Full-Stack Governance Audit for Registries-Pivot: Model Recommendation
Date: 2026-06-01 Reviewer: GPT Council
Verdict
The audit confirms the central governance spine exists and should be reused. The current problem is not absence of governance, but incomplete owner assignment, schema/law drift, and missing governance homes for grouping/threshold/pin/phantom/pivot-coverage concepts.
Recommended model
Adopt a federated-but-central governance model, using existing governance owners and the central approval spine:
- GOV-COUNCIL: owns cross-system policy definitions such as classification/grouping/threshold/label-dimension, phantom definition, pin policy.
- GOV-SIV: owns health/integrity detection such as count-integrity, orphan/phantom detection, pivot coverage, drift findings.
- GOV-DOT: owns DOT execution under Điều 35, including scan/propose/apply/audit semantics.
- GOV-MOUT: owns render/display/API surface policy for Registries-Pivot, under render-shell/no-hardcode constraints.
Do not mint a new governance owner unless reuse-first proves absence and Điều 32 approval exists.
Important distinction
Governance ownership does not mean all work is done by one agency. Policy, health detection, DOT execution, and UI rendering should have different owners, but all must use the same governance_registry and approval spine. This avoids a Registries-only local governance island.
Open points needing more evidence
- Whether GOV-SIV is already a live governance row and what exact scope/capability it has.
- Whether GOV-MOUT is already enacted/active or still draft in governance_registry.
- How governance_audit_log should be activated or replaced if currently stale/unused.
- Whether direct-pg API exception should be temporary or ratified as a sanctioned read-only adapter.
- Exact patch wording for Đ24/Đ29 threshold, Đ31 phantom, and Đ37 live-schema drift.
Next recommended action
Do not implement grouping yet. First run a focused council/design ratification step for the ownership model and law/design patch drafts. After that, build the governed grouping framework and DOT lifecycle.