Điều 1 — Foundation Principles (15 Nguyên tắc) — Compatibility Note

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

1. Old source

• Path: knowledge/dev/laws/law-01-foundation-principles.md — "ĐIỀU 1: NGUYÊN TẮC NỀN TẢNG" (body header v3.3, 2026-05-04, +NT15).
• Status: ENACTED foundational law (the detailed expansion of the Constitution's 15 NT). Legal bedrock.
• Version discrepancy to flag (note only): body title = v3.3, metadata/MỤC LỤC title still says v3.0 — a stale label, not a content change; recommend reconciling in a source-recovery pass.

2. Preserved goal

The 15 supreme principles that every decision must satisfy simultaneously ("Vi phạm 1 = vi phạm Hiến pháp"). Preserved in full. The new model is built to satisfy them, not to relax them.

3. How F0→F5/FX interprets it

• NT2 "Tự động 100%" + NT3 "DOT 100%" → read as bounded by the Owner gate / Mức 3: the machine executes, but NT2's own rule keeps humans on the Yes/No decision ("con người chỉ ra quyết định Yes/No"), reinforced by NT9 fail-closed. Automation is not self-enactment; canonical/kernel/enacted changes still need Đ32 / Owner.
• NT5 "Tự phát hiện, tự sửa" + NT12 "DOT theo cặp" (secondary detect/report engine) → read as the scanner = list-only posture: auto-detect + warn + create a fix task, not auto-fix of canonical state. (Genuine auto-fix is Điều 22's subject, which is why Đ22 is AMEND, not Đ1.)
• NT10 / NT11 / NT13 (PG-as-truth, declare-minimum, PG First·Native·Driven) → directly preserved; they are the new model's reuse-first + minimal-birth + PG-source-of-truth discipline.
• NT14 "THỰC THI ĐƯỢC NGAY" → the binding 6-question acceptance test for any future note/amendment/rewrite produced by this workstream.
• NT15 "Thiết kế trước triển khai" (Điều 20) → the process spine: reviewed design = SSOT before code/DDL/runtime.

4. What is NOT authorized

• No amendment to Điều 1. This note clarifies bounds of interpretation, it does not change any NT.
• No re-scoping of NT5/NT12 into "scanner may auto-fix" — that is a forbidden bad reading.
• No technical design, Phase-1, live query, schema change, or authority-order change.

5. Remaining blockers / caveats

• Version discrepancy v3.3 (body) vs v3.0 (metadata) → source-recovery.
• The NT2/NT3 "100% automation" vs Owner-gate boundary is an interpretation, not a clause edit; it must be confirmed by the Owner if it is ever to bind.
• RISK-BYPASS at the system level shows why "100% automation" must not be read as "auto-approve" (see the Đ35 note).

6. Where this fits in the index

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

7. Bad readings this note rejects

• "NT2/NT3 (100% automation) authorize AI to self-approve or self-enact" → FALSE; bounded by NT2 human Yes/No + Mức 3 / Đ32.
• "NT5 self-healing authorizes the scanner to auto-fix canonical state" → FALSE; scanner is list-only; auto-fix is Đ22 (AMEND).
• "This note amends Điều 1" → FALSE.

Điều 1 compatibility note rev1 | 2026-06-17 | read-only · non-authorizing | automation bounded by Owner-gate