GPT Review — One-Roof Clause Hardening and IU Axes Inclusion

Date: 2026-06-01 Reviewer: GPT Council

Verdict

The clause-hardening report is useful and correctly blocks canonical design patching until Tier-1 wording defects are folded and retested. The One-Roof Governance architecture is not ready for technical design yet.

Additional concern raised by user

Information Unit (IU / miếng thông tin) must be explicitly included in One-Roof Governance. Existing IU axes such as specialty/domain axis and parent-child-grandchild axis must not remain outside the governance restructuring.

Required inclusion

The next hardening revision must include IU as a first-class governed domain:

• IU object/profile;
• IU source/origin;
• IU cut/split/merge/compose operations;
• IU specialty/domain axis;
• IU parent-child-grandchild axis;
• IU relation graph / KG edges;
• IU labels/taxonomy;
• IU SQL links;
• IU DOT commands;
• IU vector/indexing profile;
• IU routes/API/UI surfaces;
• IU evidence/reconstruction invariants.

Governance mapping principle

IU should not create a local governance island. It must reuse the same One-Roof model:

• GOV-COUNCIL for cross-system policy definitions;
• GOV-SIV for health/integrity/coverage/orphan/governance-orphan detection;
• GOV-DOT for IU DOT execution lifecycle;
• GOV-MOUT only for display/render/API after display ownership is resolved;
• existing approval/audit/issue/event spine.

Required next action

Do not move to canonical design patching yet. Run a folded Tier-1 hardening revision that incorporates IU axes and reruns the red-team scenarios, adding IU-specific red-team cases.