Điều 32 — Approval / Owner-Gate (v1.1) — Compatibility Note

Reading category: READ_OLD_WITH_COMPATIBILITY_NOTE (catalog record #11, KEEP+NOTE). Status of this note: READ-ONLY · NON-AUTHORIZING · NOT enacted law. 2026-06-17, rev1.

1. Old source

• Path: knowledge/dev/laws/dieu32-approval-law.md — "LUẬT PHÊ DUYỆT v1.1 BAN HÀNH" (amended by S178 Fix 15).
• Status: ENACTED. This is the system's approval/Owner-gate authority. Preserved as the heavy-governance Mức-3 gate; do not weaken it.

2. Preserved goal

Every system-impacting change goes through a standardized, PG-native approval mechanism (collections + trigger + explicit states) — "không phải chat, không phải email, không phải 'anh OK rồi đó'." Quorum scales with risk. Preserved in full.

3. How F0→F5/FX interprets it

• Điều 32 is the Owner-gate / Mức-3 / canonical approval lane the new model routes to. Quorum (high = ≥1 president + ≥2 ai_council + 0 reject; medium = ≥1 president; low = ≥1 approve or a valid auto-approve rule) is preserved.
• The new model's checker is fail-closed and verdict-only; on kernel/canonical it returns ESCALATE_L3 → lane Canonical / Đ32. "AI đề xuất, không tự ban hành" (Đ39 golden rule) is the same fail-closed discipline.
• Hard rule carried in: "KHÔNG dùng Matrix/Stamp để né production / kernel gate." Matrix/Stamp is a workspace mechanism, not a way around Đ32.
• Đ32's own anti-bypass guards are reused as design constraints: no self-approve for high-risk by the creator (§4.3); reserved amend_law (high, RESERVED); handler_ref='unimplemented' blocked at DB gate + runtime, "không chỉ text policy."

4. What is NOT authorized

• No weakening of quorum; no Owner self-downgrade of a high/highest risk ("Owner không tự hạ risk … phải qua authority hợp pháp").
• No bypass of Đ32 via Matrix/Stamp for production/kernel/enacted-law changes.
• No amendment to Đ32 (KEEP+NOTE). No technical design, Phase-1, live query, schema change, or authority-order change.

5. Remaining blockers / caveats

• RISK-BYPASS (BLOCKER) — a live bypass of the approval path exists (fn_auto_approve_add, 160 unvoted applies; see the Đ35 note). This is a real violation of the Đ32 discipline to be closed in Phase-1, not a feature to imitate.
• Reserved amend_law flow is not yet implemented and must stay blocked until built.
• Metric to keep at zero: "APR historical còn missing mapping = 0."

6. Where this fits in the index

LAW_READING_INDEX.md §3.2, record #11, category READ_OLD_WITH_COMPATIBILITY_NOTE.

7. Bad readings this note rejects

• "Matrix/Stamp lets us skip Điều 32 for production/kernel changes" → FALSE; explicitly forbidden.
• "Auto-approve rules can apply without quorum / vote" → FALSE; the live fn_auto_approve_add unvoted applies are RISK-BYPASS, a violation to close.
• "The Owner can lower a high-risk item to low to ease approval" → FALSE; no self-downgrade.
• "This note amends Điều 32" → FALSE.

Điều 32 compatibility note rev1 | 2026-06-17 | read-only · non-authorizing | Owner-gate preserved · no Stamp-bypass