GPT Direction — One-Roof Governance Clause Hardening Before Technical Design

Date: 2026-06-01 Reviewer: GPT Council

Decision

Before moving to technical design, the One-Roof Governance decision pack must undergo strict clause hardening. The law/design layer must be reviewed sentence by sentence to prevent ambiguity, over-breadth, under-definition, hidden local governance, excessive noise at scale, or implementation traps.

Scope

Review only. Do not implement. Do not patch canonical design docs yet. Do not enact law. Do not bump versions. Do not mutate PG/Directus/Nuxt/Qdrant.

Review targets

• One-Roof Governance principle.
• Governed Object Contract.
• Governance-orphan / anarchic object definitions.
• Governance Coverage Invariant.
• Scalable detection architecture.
• GOV-SIV/GOV-DOT lifecycle.
• Issue/event/notification model.
• Draft clauses for Điều 37, Đ31, Đ35, Đ24/29, Đ26, Đ28, Đ45.
• Future Registries-Pivot design patch plan.

Required hardening concerns

• Avoid overly broad definitions that flood the system with noise.
• Distinguish accountable owner from supporting roles/delegates/auditors/render owners.
• Separate birth-orphan from governance-orphan.
• Define governed exceptions such as Direct-PG API exception.
• Define anti-spam aggregation for system_issues/event_outbox.
• Avoid local governance schemas or per-table governance columns unless system-wide.
• Ensure no local governance island can pass readiness.
• Ensure future modules are automatically pulled into coverage.
• Ensure every clause has testable acceptance criteria.

Next action

Run a clause-hardening mission with Claude Code CLI. Output an evidence-backed critique, revised clause text proposals, open questions, and a go/no-go for moving to canonical design patching.