Law Merge Execution Report — Old Law Corpus vs F0→F5/FX New Model (2026-06-16)

Companions (this newlaws/ workspace only): law-merge-survey-packet.md (method) · law-merge-catalog-2026-06-16.md (the main table). Survey run 2026-06-17; cohort-dated 2026-06-16.

1. Status / boundary confirmation

STATUS: PASS (catalog complete enough for GPT/Codex/Owner review). READ-ONLY · NON-AUTHORIZING · CATALOG-ONLY.

This report classified the existing law corpus against the completed F0→F5/FX model. It produced no amendment, rewrite, compatibility note, technical design, implementation, Phase-1, live query, schema/registry change, or authority change, and it resolved no held blocker. Every reported-LIVE substrate is treated as DOCUMENTARY_ONLY; no live proof exists in this survey. Engineering/Codex/Council PASS ≠ Owner authorization.

2. Folder policy confirmation

Branch	Meaning	Touched?
`knowledge/dev/laws/`	old / enacted / draft law corpus	NO (read-only)
`knowledge/dev/laws-new/`	F0→F5/FX survey branch	read-only
`knowledge/dev/laws-new/newlaws/`	law-merge workspace	outputs only — exactly the 3 files

3. Sources discovered and read

New-model lens (read): F0/F1/F2/F3/F4/F5 owner-decision records; F4 + F5 execution reports; FX reuse-survey packet + FX execution report; F0→F5 Cross-F Evidence & Readiness Matrix; f5-…-reuse-survey-packet; technical-slice-framework.md (rev56); de-bai-cai-tien.md (rev33); cau-hoi-khi-tai-cau-truc.md (rev82).

Authority sources (read): constitution.md (rev44, v4.6.3); ssot/operating-rules.md (rev51, v7.58); enacted Điều 32/33/35/37/38/39; plus the foundation law-NN family, the terminology glossary, and Điều 43/44.

Old law corpus discovered. Two naming conventions exist side-by-side under knowledge/dev/laws/:

dieu*-…-law.md — Điều 20, 26, 28, 29, 30, 31, 32, 33, 34, 35 (+v5.0/v5.1), 36, 37, 38 (+appendix-01, +dieu38-trien-khai/LSL-01, /L4), 39, 41 (+5 drafts, +phụ-lục), 43 (System Context, +3 superseded), 44 (UOSL DRAFT); Constitution (+old amendment draft).
law-NN-*.md (the foundation family, initially mis-assumed missing) — Điều 0-H, 1, 2, 3 (full), 4, 5, 6, 7, 8, 9, 10–13, 14, 15–16, 17–18, 19, 22 (law-22-self-healing), 24 (label-law); plus terminology-glossary.md.
Implementation subtrees (dieu28/38/43/44-trien-khai/, dieu43-migrations/, dieu41-revision-rulings/) — DEFER buckets.

53 law-level records were produced. Implementation reports were not read individually except where they carry a law-level document (LSL-01, L4).

Read caveat / honest gap: the operative Điều 0-G "Luật Khai Sinh" is referenced from the Constitution index but has no standalone file (it is embedded in the Constitution; the procedural birth law is law-04-birth-process.md). Some 0-G operative-clause conclusions are therefore flagged UNKNOWN pending a later, separately-assigned read of the embedded text — see §7 Birth.

4. Owner 3-question answers

Question	Answer summary
Q1 — reusable as-is?	6 KEEP (fully compatible: Operating Rules v7.58, Điều 7 Assembly-First, Điều 20 Design-Before-Execution, Điều 30 Regression-Protection, Điều 6 Sync, Điều 15-16 State/Checkpoint) + the as-is core of 25 KEEP+NOTE. The reuse-first foundation is large and intact — the new model is built from these laws (NT8/NT9/NT11/NT14/NT15).
Q2 — need note / verify / amend first?	25 KEEP+NOTE (a compatibility note clarifying the new-model interpretation) + 5 AMEND (specific clauses to amend). The recurring note themes: birth = TEMP_ID (canonical at promote); scanner = list-only (no auto-fix); DOT = narrow; governance = info over existing ledgers; Owner-gate above Council; held CONS/CELL blockers.
Q3 — (re)write before technical design?	1 REWRITE (Điều 37 Governance Organization) + the High-priority AMEND set (Điều 33 PostgreSQL, Điều 36 Collection, Điều 38 v3.0, L4 Birth-Gate-Extension, Điều 22 Self-Healing). Nothing else is a true "write new"; the corpus is reusable foundation, restaged not replaced.

5. Method and internal gate result

Method: a documentary, reuse-first classification. The completed F0→F5/FX corpus was distilled into one invariants/boundaries lens; every law was then read in full and judged against that lens through the 11 per-law audit questions, with the more conservative label chosen on doubt. Discovery was run twice (the second pass after finding the law-NN foundation family the first discovery had missed), so the catalog covers the foundation laws rather than mislabeling them NOT_FOUND.

Gate	Result	Evidence
G1 F0→F5/FX readable	GREEN	all owner records + exec reports + matrix + framework read
G2 Constitution + OR readable	GREEN	constitution.md rev44, operating-rules.md rev51 read
G3 law corpus discoverable	GREEN	both `dieu*` and `law-NN` families + subtrees enumerated
G4 labels consistent	GREEN	one rubric applied across both passes
G5 no amend/rewrite/design/impl	GREEN	none produced
G6 no live DB/runtime/Phase-1	GREEN	KB-only; all substrate documentary
G7 Owner 3 questions preserved	GREEN	§4 + catalog
G8 special sections covered	GREEN	§7 (six sections)
G9 folder policy preserved	GREEN	`laws/` untouched; 3 outputs under `newlaws/`

All GREEN → survey ran to completion.

6. Catalog summary

Classification	Count	One-line meaning
KEEP	6	compatible as-is; keep reading from `laws/`
KEEP+NOTE	25	valid; add a laws-new compatibility note (no rewrite)
AMEND	5	valid goal; amend specific clauses before technical design
REWRITE	1	deep structural/authority conflict; rewrite later in `newlaws/`
DEFER	16	superseded / implementation-only / not-needed-before-technical-design
TOTAL	53

High-priority before technical design: Điều 37 (REWRITE); Điều 33, Điều 36, Điều 38 v3.0, L4, Điều 22 (AMEND); and the High-priority KEEP+NOTE notes whose interpretation gates design — Constitution, Điều 39, Điều 35, Điều 29, Điều 31, Điều 32, Điều 38 Appendix-01, Điều 0-H, Điều 1, Điều 4, Điều 19, Terminology Glossary.

7. Special sections

7.1 Constitution (`constitution.md` rev44, v4.6.3 BAN HÀNH) — KEEP+NOTE

Stay supreme? Yes, unambiguously. The Constitution self-declares "Văn bản tối cao." F0→F5/FX is an implementation/rollout method under it, never a competing authority; CONS-004 already fixes the precedence (HP supreme > enacted Điều 32/35/37/38/39 > laws-new KB drafts; VPS=SSOT; PG/Directus=truth; cross-class = Owner gate). It stays supreme; do not amend.
Compatibility note? Yes — short, forward-looking, written in laws-new (not in the Constitution), non-authorizing: (i) F0→F5/FX is a method under the Constitution; (ii) the principles it leans on; (iii) the clauses Owner may later adjudicate if Law Merge proceeds.
Principles that directly SUPPORT F0→F5/FX: NT8 Assembly-First (reuse-first / One-Roof-over-existing-ledgers), NT11 Khai-tối-thiểu (minimal birth / anti-bloat), NT14 Thực-thi-được-ngay (the honesty filter behind "documentary ≠ live"), NT15 Design-before-implementation (no schema/canonical write before Owner-gated design), NT9 Không-chắc-đúng=sai (checker fail-closed / uncertain→Mức 3), NT2/NT10 PG-as-truth. Điều 32/Mức 3 + Điều 20 are the heavy-governance gate the new model deliberately keeps for canonical/kernel/production.
Clauses that MAY need future amendment (flag only, do NOT amend): Điều 0-B (7 Lớp / 33 species) + Điều 29 (7 dimensions) → CONS-003 (6-vs-7 tầng), gating any cell_id; Điều 0-G + Điều 4 birth-timing → reconcile to canonical-at-promote; NT5 "tự sửa"/NT12 dual-trigger → read down to list-only observability; Điều 32 stamp-count → any new mandatory core stamp is a Mức-3 change.
Documentary note: the enacted text carries 15 principles (NT12–NT15 added post-v4.4), not 13 — a documentary correction, not a conflict.

7.2 Điều 37 — Governance Organization Law v3.3 (`dieu37-…`) — REWRITE (goals preserved)

Điều 37 is the one law whose entire subject is the governance bộ máy itself (Law→Agency→Entity, top-down) — exactly the FX D2 "Governance One Roof" domain. The reframing is structural and authority-level, so the disposition is REWRITE later (in newlaws/), not amend-in-place (Điều 37 is enacted/immutable). Three conflicts each pass the AMEND threshold:

Architecture: Điều 37 mandates a central governance_registry (+ 5 more owned tables). FX is explicit: "One Roof = a conceptual roof over EXISTING ledgers, NOT the central registry"; reuse universal_edges / governance_role / owner / governance_audit_log. Điều 37 is the central-registry model the new model rejects.
Authority model: Điều 37 enacts via Council 2-round vote and self-executes freeze→transfer→48h→DROP; the new model holds Owner is the only phase authority, Engineering/Council PASS ≠ Authority PASS, new mandatory governance obligations = Mức-3/Điều 32.
Mechanism: Điều 37 ships 6 auto-cron DOTs (incl. DOT-GOV-ONBOARD auto-inserting 5 default contracts) + 8 hard-REJECT triggers (Trigger #8 auto-inherits enforcement/jurisdiction). The new model says DOT = one narrow task, scanner = list-only (no auto-fix / no full-scan), no auto-mutation governance machine. This meets the carried RISK-BYPASS (the live fn_auto_approve_add 160-unvoted-applies bypass + "PRODUCTION READINESS FAIL").

Goals to preserve: the top-down↔bottom-up coverage mesh; gap/overlap/orphan/"luật tủ kính" detection (→ list-only scanner); jurisdiction/scope and enforcement-linkage as relationship facts; terminology SSOT + SSOT non-overlap discipline; OWNER_STAMP→governance_audit_log and GOV_STAMP→governance_role (the one literal One-Roof tie). Mechanisms to replace: the central registry; the 6 auto-cron DOTs; the auto-onboard/auto-inherit writers; the 8 hard-REJECT-trigger enforcement model; Council-vote/auto-DROP; the big-bang bootstrap seed.

A future rewrite MUST cover (do NOT write it now): Owner gate as sole phase authority; Codex/GPT/Claude as proposer/reviewer only (AI never self-enacts); Engineering ≠ Authority PASS; Mức 3; APR/Điều 32 as the escalation lane; the four primitives (DOT narrow / stamp marker / checker verdict / scanner list-only); governance as relationship/state/classification info over existing ledgers; no monster registry; no scanner auto-fix; no second birth system for agencies; carry the RISK-BYPASS caveat; re-anchor OWNER_STAMP/GOV_STAMP to the One Roof.

7.3 Điều 39 — Knowledge Graph Law v2.3 (`dieu39-…`) — KEEP+NOTE

Preserve goals? YES — every goal stays valid: the Data→DataGraph→KG→Priority→AI→human-oversight chain; the golden rule "AI ĐƯỢC ĐỀ XUẤT, KHÔNG ĐƯỢC TỰ BAN HÀNH TRI THỨC CHUẨN" (→ fail-closed); TBox=human / ABox=AI (→ Mức-3/Điều 32); trust_score + "không provenance = quarantine" (→ stamp/provenance + missing-stamp→quarantine); the narrow C5 output contract (→ "DOT = một việc hẹp"); ABox-only self-learning (never TBox/canonical).
Change rollout method? YES — the only real conflict is the rollout: 36 DOT-KG (18 pairs) + 14 kg_* tables + a 24/7 self-learning loop registered as one program. Restage one KG fact-type / one PG-only DOT at a time. Two postures need the list-only reframe: A6 self-healing (orphan→auto-link, contradiction→quarantine, stale→retire) and D4 auto-link / D3 auto-retire become list-only warning reports first, any fix Owner-gated. kg_auto_approve_rules is the surface implicated by the live fn_auto_approve_add bypass (RISK-BYPASS) — close it before trusting auto-approval.
Compatibility/reinterpretation note needed? YES — a future, separately-Owner-authorized "Điều 39 Compatibility/Reinterpretation Note" that preserves goals and stages rollout. Not a rewrite, not an amendment, not written here.
Registered/spec'd vs executed/live: load-bearing. Điều 39 is genuinely ENACTED, and §7B says "chưa đăng ký = chưa triển khai" — but per FX the runtime is EMPTY: even with 36/36 DOT-KG registered, last_executed is NULL, 0 runs / 0 KG events, KG owner unregistered, kg_* liveness unproven. Registered ≠ spec'd ≠ executed ≠ live ≠ production-ready. liveProof = No.
How it combines with F0→F5: as the cross-cutting FX (D2) layer over the F-stack — F1 supplies born entities (nodes); F3 supplies DOT substrate (reframed narrow); F4 supplies stamp/promote (TBox = Mức-3; HOLD-2 blocks KG canonical write at promote); F5 supplies observability (self-healing monitors → list-only). Reuse universal_edges/entity_relations, not a central registry.

7.4 Điều 38 — Text as Code family — AMEND (v3.0 DRAFT, L4 DRAFT) / KEEP+NOTE (Appendix-01 enacted, LSL-01)

The Điều 38 family is the closest old-law analogue to the new D4 Information Unit / Smart Brick and D5 Temp Store / Candidate.

Compatible (keep): atomization → brick = central subject; LSL-01 makes this explicit and correct ("chữ thật sống ở miếng"; document = lightweight publication = the store; vector chunk = projection, never SoT, never the "miếng"); canonical_address = identity-before-lifecycle; publication-snapshot/label/membership → candidate-packet-view vs canonical-at-promote; reuse-first ladder, paired writer/checker ("no checker no lane"), legal write-path, pilot-mock-first.
Needs AMENDMENT (before technical design): Điều 38 v3.0 (DRAFT) — "DOT tự động 100% sửa" + "văn bản đầu ra tự sinh" → scanner-list-only + checker-verdict + render-at-promote; B2.1 auto-retire via a bare PG trigger → route through the fail-closed checker + atomic-promote (HOLD-2 not lifted); keep A3 integrity guards as Mức-3 promote-boundary guards, not birth-P0. L4 Birth-Gate-Extension (DRAFT, the sharpest conflict) — it front-loads completeness + (for component) reuse-decision + human-approval AT INSERT, contradicting "birth P0 = minimal TEMP_ID only; governance + canonical birth at the promote boundary." Amend so birth issues only TEMP_ID and the completeness/reuse/approval checks relocate to the promote checker; reconcile with RISK-BYPASS (the Điều 0-G gate is warning-only and cannot be trusted to block). LSL-01 §10.4 keeps "L4 áp dụng nguyên," so LSL-01 and L4 must be reconciled to canonical-at-promote together.
Needs a NOTE (enacted, do not rewrite): Appendix-01 — MT0A/MT0B SSOT-Catalog + Component-Registry = reference-only Module-Contract-First for canonical/high-risk (the live contract between bricks is the thin 5-field IO Contract, CONS-002 open); MT5/MT6 "auto-fix or warn" = list-only; MT14 coverage/integrity dashboard ≈ the One-Roof/GCOS coverage-scanner which is DESIGN-ONLY / BUILD-NO-GO; Knowledge→truth promotion honors Owner/Mức-3 at promote. LSL-01 — §10.2 "Agent finalize low-risk" = Mức-1 workspace/delete-fast only (never canonical/promote write); §3 supremacy clause + NT15 carry KB practical-authority under CONS-004 but a formal constitution amendment still routes through Owner/Council/Điều 32.

7.5 Điều 35 — DOT Governance Law v5.2 (`dieu35-…`) — KEEP+NOTE

Alignment with DOT-as-narrow-info-completion: shared root intuition ("govern DOT itself: who's doing what, missing what, broken what" = the F5 list-only visibility concern; the A/B paired model + fn_dot_enforce_paired = the enacted ancestor of "no checker, no lane"). Where it must be narrowed (the note): its MT3 "tự vận hành khép kín / tự động 100%" + the 4 self-governing cron DOTs are the DOT-as-governance-engine framing the new model rejects — narrow DOT to one info-completion task; scanner stays list-only. (v5.1/v5.2 already self-corrected partway: H13 pulled back to "báo động only", §5.1 "INFER FAIL = CẤM POST partial" — both already aligned.)
Reusable old loop: §6.2 fix_repair_dot — the 6-step DETECT→PROPOSE→APPROVE→APPLY(backup+dry-run)→VERIFY(3-tier+rollback)→CLOSE loop is precisely the documentary pattern behind laws-new scanner(list-only)→checker(verdict)→atomic-promote(mutation) + FIX7-style rehearsal. §6.5 ADMIN-fallback (Chủ tịch-only, writes admin_fallback_log before patching + retroactive APR within 24h) is reusable as the Owner-gate/Mức-3-escalation-with-audit pattern. Reuse the pattern, not the running system.
Live caveats that must travel with any reuse: PRODUCTION READINESS FAIL (the live substrate audited not production-certified, checkpoint-codex-2026-06-05) — Council/Engineering PASS ≠ production-ready; confirmed authority bypass fn_auto_approve_add (160 unvoted applies) = RISK-BYPASS, must be closed + Phase-1-verified; fn_birth_gate warn-mode + birth_gate_mode kill-switch = cannot be trusted to block, and is metadata-scope for dot_tools only (§8.3) — must NOT be conflated with F4 canonical-birth-at-promote; runtime liveness unproven (no live query run).
Note vs amendment: a future compatibility/reinterpretation NOTE, not an amendment, not now — the goal is valid and the authority model (APR/Điều 32) is sound (no REWRITE), no obsolete goal (no DEFER); only the interpretation under the new rollout needs clarifying, which a note does without touching enacted text. The two non-final versions (v5.1 DRAFT, v5.0 BACKUP) are explicitly superseded → DEFER.

7.6 Birth / Điều 0-G (Constitution-embedded + `law-04-birth-process.md`) — KEEP+NOTE on Điều 4; 0-G operative text flagged

Important scope caveat: Điều 0-G "Luật Khai Sinh" is not a standalone file — it is embedded in the Constitution; the procedural birth law is law-04-birth-process.md (KEEP+NOTE). Conclusions about 0-G's operative clauses are partly UNKNOWN pending a later, separately-assigned read of the embedded text.
(a) Match minimal TEMP_ID / candidate identity? Điều 4 §2 grants, at birth: auto-ID + auto-register + minimal metadata + notify, and is silent on the TEMP_ID-vs-BIRTH_STAMP split. It does not name minimal TEMP_ID, but it also does not write a canonical birth at INSERT (no BIRTH_STAMP clause, no promote step, no canonical-field write). Closer to "candidate identity + minimal metadata at INSERT" → maps to TEMP_ID at birth (kho tạm, F1).
(b) Imply canonical birth too early? No clause forces canonical-at-INSERT, but the silence risks being read that way (a naive implementer could treat the INSERT-time registry row as canonical). The invariant: TEMP_ID_STAMP ≠ BIRTH_STAMP; canonical birth = output at promote (F4). Điều 4 doesn't contradict this — it predates it. Interpretive risk, not a hard conflict → KEEP+NOTE, not AMEND.
(c) Need amendment for BIRTH_STAMP at promote? A note, not an amendment. The goal (no entity born "bừa bãi"; process-first birth; auto-ID/register; minimal metadata; description guard) is fully preserved. The note supplies the missing lifecycle split: at birth grant TEMP_ID (the INSERT-time registry row is a candidate); BIRTH_STAMP + canonical birth = outputs at promote; the Description-Guard default WARN + auto-gen-only-on-NULL already match the soft/fail-closed completion-marker posture (keep verbatim). Held / not resolved: the co-residence of fn_birth_gate (Điều 35, warn + kill-switch = RISK-BYPASS) with the description guard; CONS-003 and CELL-003/004/007 (the birth CELL = layer×species×store×domain is the only canonical matrix; Điều 4 does not define it and must not be made to).
Scanner cross-note: Điều 19 Orphan Scanner is aligned with list-only (§5 Amidan: "không block tại gate … monitoring phát hiện"); only its "quét MỌI THỨ" wording needs the assemble-existing-signals note → KEEP+NOTE. Điều 22 Self-Healing is the one law with genuine auto-fix (detect_and_fix, HC-TRIGGER auto_attach, auto-close-as-mutation) → AMEND (re-scope auto-fix to Owner-gated narrow DOT or downgrade to proposals; keep the detect/list/expose half, which is exactly the One-Roof ledger).

8.–12. Classification lists (full corpus, per-law)

Each entry: goal-validity · key conflict · recommended action · per-row safety-lock. Live proof = No / Unknown / N-A for all (documentary survey). Ordered within each list as produced.

KEEP (6)

Dieu 20 - Design Before Execution Law (Thiet Ke Truoc Trien Khai) v1.2 — knowledge/dev/laws/dieu20-thiet-ke-truoc-trien-khai.md (rev 12; enacted(BAN HANH) v1.2 FINAL, in HP Dieu 1 NT15). Goal valid: Yes. Conflict: None. Action: Keep reading from laws/ unchanged. Cite Dieu 20 as the enacted process authority that the F0->F5/FX survey already operates under (design-before-execution, evidence-first, Owner-gated execution, double-evidence verify). Safety-lock: Must NOT be invoked to AUTHORIZE any F-phase execution/build by itself - Dieu 20 governs HOW to execute once Owner opens a phase; Engineering/process PASS under Dieu 20 is still not Authority PASS. N…
Dieu 30 - Regression Protection Law (Bao Ve Hoi Quy) v1.2 — knowledge/dev/laws/dieu30-regression-protection-law.md (rev 1; enacted(BAN HANH) v1.2 (S160, Council GPT+Gemini consensus,…). Goal valid: Yes. Conflict: None. Action: Keep reading from laws/ unchanged. Treat Dieu 30 as the enacted regression/evidence discipline the new model inherits (no blind PASS, evidence-or-FAIL, contract invariants, reproduce-before-fix). When an F-layer pilot/promote rehearsal is… Safety-lock: Must NOT be read as authorizing any test/pilot RUN in this survey phase; it governs how to prove non-regression once a change is Owner-authorized. No CI run, no Playwright run, no contract write in t…
Operating Rules (OR) v7.58 Concise — assembly-first operating/authority layer — knowledge/dev/ssot/operating-rules.md (rev 51; enacted operating/authority layer (concise SSOT; subordinat…). Goal valid: Yes. Conflict: None (operating-layer fully compatible; reinforces the new model). Action: KEEP and continue reading from ssot/operating-rules.md as the operating/authority layer; no amendment needed before technical design. Optionally (not required) the future laws-new compatibility note can cross-reference OR §0.3/§0.4 as the… Safety-lock: MUST NOT weaken OR's STOP/out-of-scope/read-only/AP-CLOSE guards when implementing the new model; MUST NOT let Matrix/Stamp 'open-goal' framing be used to skip OR §4 high-risk prompt gates (productio…
Dieu 15-16 - State Machine + Checkpoint Law — knowledge/dev/laws/law-15-16-state-checkpoint.md (rev 1; Enacted (constitution lists law-15 and law-16 separately; t…). Goal valid: Yes. Conflict: None material. Additive columns (step_type=state, workflow_mode, relation_type, current_s…. Action: Keep reading from laws/. No amendment needed before technical design. (Optional, non-blocking: when checkpoint/state schema is actually materialized, do it as additive columns under Owner-gated design and keep orphan-detection as list-only… Safety-lock: Must NOT treat the reported existing tables/record-counts as live-proven, must NOT materialize schema or run migrations this phase, must NOT query live DB/runtime, must NOT amend the law text this ph…
Dieu 6 — Luat Dong bo (Sync Law) — knowledge/dev/laws/law-06-sync.md (rev 1; Enacted, thin principle law (v4.0 extends to 5 layers, defe…). Goal valid: Yes. Conflict: No conflict. 'Phat hien TU DONG' = auto-detect/report, which is exactly scanner-list-only…. Action: Keep, read from laws/ as-is. No amendment needed before technical design. (Any DOT-orchestration / atomicity caveats attach to Dieu 0-H, not to this thin principle.) Optionally inherit the Dieu 0-H note by reference, but no standalone note… Safety-lock: MUST NOT run any sync/divergence check against live, MUST NOT auto-reconcile sources; survey only.
Dieu 7 - Assembly First Law (Luat Tan dung) — knowledge/dev/laws/law-07-assembly-first.md (rev 1; Enacted; foundational reuse-first priority order. This is t…). Goal valid: Yes. Conflict: None. Fully congruent with reuse-first / no-new-system / assemble-existing-signals. The '…. Action: Keep reading from laws/ unchanged. No note, no amendment needed before technical design. Use it as the governing reuse-first principle when scoping which existing substrate F0->F5/FX assembles. Safety-lock: MUST NOT propose any new system/table/registry where existing PG/Directus/Nuxt/open-source substrate can be assembled; MUST NOT do direct ALTER TABLE; MUST NOT execute any schema change this phase (r…

KEEP+NOTE (25)

Dieu 0-H — Luat Dong bo 5 Tang (5-Layer Sync Law) — knowledge/dev/laws/law-00h-5layer-sync.md (rev 1; Enacted (v1.0, S147). DOT-secret 2-cap + 2-dong-co mechanis…). Goal valid: Yes. Conflict: Rollout/mechanism framing: §2.2/§4.1 cast DOT Cap-B as a single button that writes schema…. Action: Keep reading from laws/. Add a short compatibility note: (a) re-map 'DOT Cap-B does all 5 layers' onto a SET of narrow DOT info-completion tasks orchestrated, not one monster engine; (b) secondary-engine §4.2 = scanner LIST-ONLY / assemble… Safety-lock: MUST NOT execute any DOT/Cap-B write, MUST NOT run scanner against live, MUST NOT alter any layer, MUST NOT design the 5-layer DOT orchestration; survey/catalog read-only only.
Dieu 1 — Nguyen tac Nen tang (v3.3, 15 principles incl NT11/NT14/NT15) — knowledge/dev/laws/law-01-foundation-principles.md (rev 12; Enacted, highest constitutional tier (Council PASS; NT11 Ge…). Goal valid: Yes. Conflict: No clause conflict. Only an interpretive gap: NT2 'Tu dong 100% / may lam' + NT3 'AI chi…. Action: Keep as legal foundation. Short note: NT2/NT3 '100% automation' is bounded by Owner-gate/Muc 3 — automation runs the mechanism, but canonical authorization/enactment stays Owner-only (Codex/Council/engineering-green PASS != Authority PASS)… Safety-lock: MUST NOT treat any engineering/Council PASS as authority to enact a phase; MUST NOT amend/rewrite a constitutional principle; survey only.
Dieu 29 - Collection Classification Law (Phan Loai Collection) v2.0 — knowledge/dev/laws/dieu29-classification-law.md (rev 1; enacted/simplified v2.0 (S160); v1.0 complex version explic…). Goal valid: Yes. Conflict: Mixed (Definitional birth-on-registration + Evidence-dependency; otherwise reuse-aligned). Action: Keep goals (governance_role taxonomy, species mapping, phantom detection are reused as-is); add a short compatibility note (do NOT rewrite): the 'birth trigger auto-INSERT birth_registry on every new record' clause must be reinterpreted un… Safety-lock: Must NOT let 'birth trigger auto-INSERT birth_registry on insert' be read as authorizing canonical birth at registration time; canonical birth stays an output at promote (HOLD-2). No birth_registry w…
Dieu 31 - System Integrity Verification Law (Toan Ven He Thong) v1.2 — knowledge/dev/laws/dieu31-system-integrity-law.md (rev 1; enacted(BAN HANH) v1.2 (S131/S131-R3, Council Gemini GOx2 +…). Goal valid: Yes. Conflict: Mixed (Architecture self-healing/auto-fix + Rollout-assumption big-bang scaling; otherwis…. Action: Keep goals and the contract-driven detect-then-expose core (it is reused directly); add a short compatibility note (do NOT rewrite): (a) under F0->F5/FX the scanner stays LIST-ONLY - the SS XII Self-Healing / auto-fix / auto-generated-cont… Safety-lock: Must NOT authorize any auto-fix / self-healing / auto-generated-contract / self-scaling scanner behavior in the new model; scanner stays list-only and no full-table-scan. No runner run, no contract w…
Dieu 32 - Approval Law (APR) v1.1 — knowledge/dev/laws/dieu32-approval-law.md (rev 2; enacted (BAN HANH v1.1, S178 Fix 15, 2026-04-18)). Goal valid: Yes. Conflict: Mixed (Authority-model compatible-and-relied-on; minor Architecture/Definitional friction…. Action: Add a short compatibility note: Dieu 32 = the heavy-governance Muc-3 / Canonical-lane approval gate that the new model PRESERVES for high-risk/canonical (checker ESCALATE_L3 -> Dieu 32; GOV/OWNER stamps; new-mandatory-stamp escalation). Cl… Safety-lock: Must NOT weaken or bypass Dieu 32 quorum/self-approve/reject-lock rules; must NOT use Matrix/Stamp light lanes to skip APR for high-risk/canonical/kernel changes; must NOT treat the reserved/unimplem…
Dieu 35 - DOT Governance Law v5.2 FINAL — knowledge/dev/laws/dieu35-dot-governance-law.md (rev 13; enacted (BAN HANH v5.2 FINAL, 2026-04-18 S178 Fix 15; live…). Goal valid: Partial. Conflict: Mixed. Action: Keep reading from laws/ as the enacted DOT law; attach a future compatibility/reinterpretation note (do NOT rewrite, do NOT amend the enacted text now) that: (1) reframes DOT under F0->F5 as a NARROW info-completion machine (one small task… Safety-lock: MUST NOT: call any fn_* (fn_birth_gate / fn_log_issue / fn_auto_approve_add) live; flip birth_gate_mode to 'block'; run BLOCK 4 / NOT NULL migration / dedupe; touch dot_tools or system_issues live; a…
Dieu 4 - Birth Process Law (Luat Sinh san) — knowledge/dev/laws/law-04-birth-process.md (rev 5; Enacted; description-guard operative; the standalone birth-…). Goal valid: Yes. Conflict: Rollout/sequencing assumption: §2 ('cap ID tu dong' + 'dang ky vao registry tu dong' at b…. Action: Add a short compatibility note: at birth this law grants TEMP_ID (kho tam / candidate identity F1), NOT BIRTH_STAMP; BIRTH_STAMP + canonical birth are OUTPUTS at PROMOTE (F4), never at INSERT. The Description Guard default WARN (not BLOCK)… Safety-lock: MUST NOT write canonical birth / BIRTH_STAMP at INSERT during this phase; MUST NOT alter the birth trigger functions or flip description_enforcement_mode warn->block; MUST NOT query/run birth substra…
Hiến pháp (Constitution) v4.6.3 BAN HÀNH — 15 NT + Điều 0/0-B/0-G/20/29/32/35/3… — knowledge/dev/laws/constitution.md (rev 44; enacted(BAN HANH) — supreme/văn bản tối cao). Goal valid: Yes. Conflict: Authority-model (supreme spine the new model must respect; the only 'conflict' is the sur…. Action: KEEP as supreme; do NOT amend now. Attach a forward compatibility NOTE (in laws-new, not in the constitution) recording: (i) CONS-004 working precedence (HP supreme > enacted Điều 32/35/37/38/39 > laws-new KB drafts; VPS=SSOT; PG/Directus=… Safety-lock: MUST NOT amend, rewrite, re-enact, or downgrade the constitution in this phase; MUST NOT resolve CONS-003 (6-vs-7 tầng) or alter Điều 0-G birth semantics; MUST NOT use Matrix/Stamp/DOT to bypass Mức-…
Terminology Glossary v2.1 (Giải thích Từ ngữ Hiến pháp Kiến trúc) — knowledge/dev/laws/terminology-glossary.md (rev v2.1 ENACTED…; ENACTED constitutional glossary (defines vocabulary for Hiế…). Goal valid: Yes. Conflict: Definitional tension (not error): (1) 'Lớp 7 cấp 0→6' + '33 species / Tab Pivot 7th row'…. Action: Keep as the shared vocabulary anchor. Add a compatibility note mapping F0→FX vocab onto it: (a) the only canonical matrix = birth CELL; 'Lớp 7'/'Tab Pivot 7th row' are reporting/pivot framings and remain subject to held CONS-003 + CELL-003… Safety-lock: MUST NOT resolve CONS-003 (6-vs-7 tầng) or CELL-003/004/007 here; MUST NOT redefine/rewrite any glossary term; MUST NOT assert the 7-level/Tab-Pivot framing as the canonical cell dimension model.
Điều 38 - Phụ lục 01: Text as Code Objectives (Đề bài — Component/BOM/SSOT Cata… — knowledge/dev/laws/dieu38-appendix-01-objectives.md (rev 5 (BAN HÀNH 2…; enacted (BAN HÀNH — Phụ lục 01 Điều 38, Mục tiêu)). Goal valid: Yes. Conflict: Architecture (Module-Contract-First / central-registry framing vs thin IO Contract + One-…. Action: Keep reading from laws/ unchanged (it is enacted; do NOT rewrite). Attach a short F0→F5/FX compatibility NOTE clarifying interpretation of four areas: (1) MT0A/MT0B SSOT-Catalog + Component-Registry = reference-only / Module-Contract-First… Safety-lock: Must NOT build the SSOT-Catalog/Component-Registry as a NEW central registry/store, nor the MT14 coverage/integrity dashboard as a live auto-fix scanner; no new mandatory stamp from MT-derived govern…
Dieu 10-13 - Operations Law (inject/idempotent/lifecycle/live-catalog) — knowledge/dev/laws/law-10-13-operations.md (rev 1; Enacted (constitution lists law-10/11/12/13 separately; thi…). Goal valid: Yes. Conflict: Rollout/mechanism partial-conflict (not goal conflict). Dieu 12 'Sua -> cap nhat TAT CA r…. Action: Keep reading from laws/. Add a short compatibility note (do NOT rewrite): (1) DOT stays the NARROW one-task info-completion machine; the '5-tang dong bo / DOT la cong duy nhat' wording is interpreted as goal not as a mandate to build a mul… Safety-lock: Must NOT build or authorize a multi-store auto-propagation / auto-sync engine, must NOT treat the '5-tang tu biet' / Model-B auto-sync as license for auto-fix or full-table reconciliation, must NOT q…
Dieu 14 - Anti-Duplicate Law (3 cap) — knowledge/dev/laws/law-14-no-duplicate.md (rev 1; Enacted but explicitly PENDING-ENFORCE: dot-duplicate-engin…). Goal valid: Yes. Conflict: Rollout/mechanism partial-conflict (not goal conflict). The prescribed single 'dot-duplic…. Action: Keep reading from laws/. Add a short compatibility note (do NOT rewrite): (1) keep the Cap1 cheap exact-block as a narrow pre-create check (DOT-narrow compatible); (2) realize Cap2/Cap3 NOT as one monster full-table-scan engine but as asse… Safety-lock: Must NOT build dot-duplicate-engine or any --scan --type=ALL full-table scanner, must NOT auto-delete/auto-merge suspected duplicates (warn-only), must NOT query live DB/runtime, must NOT amend the l…
Dieu 19 - Orphan Scanner Law (Side B) — knowledge/dev/laws/law-19-orphan-scanner.md (rev 1; Enacted; Side-B orphan/coverage scanner pairing the Side-A…). Goal valid: Yes. Conflict: Mechanism phrasing: §2 'quet MOI THU' + 'so TAT CA registries' reads as full-table-scan,…. Action: Add a compatibility note: under F0->F5 the orphan scanner is LIST-ONLY (chi liet ke), produces a report + orphan list and creates tasks (proposals) - it does NOT auto-fix and does NOT block at the gate (Amidan = exactly the new model). Cla… Safety-lock: MUST NOT run the scanner live, MUST NOT auto-fix or block-at-gate any orphan, MUST NOT trigger full-table scans, MUST NOT mutate registries this phase; report/list only.
Dieu 2 — Luat Registry (23 prefix) — knowledge/dev/laws/law-02-registry.md (rev 2; Enacted, declared 'most important foundation law' (violatio…). Goal valid: Yes. Conflict: No structural conflict. One interpretive boundary: 'ID khi cap = KHONG DOI' is the identi…. Action: Keep. Note: the auto-issued unchanging ID = the identity-root / TEMP_ID class at birth (F1); it is NOT the BIRTH_STAMP nor canonical birth, which are F4 outputs at promote ('canonical = output at promote'). The registries here = per-class… Safety-lock: MUST NOT create/alter any registry, MUST NOT issue/mutate IDs, MUST NOT materialize cell_id/dot_role columns, MUST NOT promote anything to canonical; read-only catalog.
Dieu 26 - Pivot Law (formerly Registries & Counting) v4.0 — knowledge/dev/laws/dieu26-pivot-law.md (rev 1; enacted/council-approved (v3.4 L1 + v3.5 L2 thong qua; v4.0…). Goal valid: Partial. Conflict: Mixed (Architecture + Definitional + Rollout-assumption). Action: Keep goals; add a short compatibility note (do NOT rewrite): (a) DOT = narrow info-completion machine, not a scale/governance engine; (b) the only canonical matrix is the 4-axis cell, while Tab-Pivot/Layer-5 matrices are display/reporting… Safety-lock: Must NOT treat Tab-Pivot/Layer-5 matrices as the canonical birth/cell dimension model, and must NOT let 'scale by DOT' authorize a DOT-governance/scale engine. No materialization of matrix dimensions…
Dieu 3 — Luat Metadata (machine-checkable description governance) — knowledge/dev/laws/law-03-metadata.md (rev 6; Enacted (S178 Fix 23 + Fix 28, Council 2-round APPROVE FINA…). Goal valid: Yes. Conflict: No deep conflict. §2.1 C1-C3 are enforced by a PG trigger at INSERT/UPDATE (Dieu 4 §2.1 B…. Action: Keep. Note: the §2.1 PG-trigger description guard = a fail-closed completion guard/stamp at TEMP/birth level (validate-or-block), NOT auto-fix and NOT canonical BIRTH_STAMP; H11/H11b scans = list-only assemble-existing (Dieu 43), report no… Safety-lock: MUST NOT run any description guard/trigger or H11 scan against live, MUST NOT write/backfill descriptions, MUST NOT change dot_config, MUST NOT promote PROV-AI to PROV-HUMAN; catalog only.
Dieu 39 - Knowledge Graph Law v2.3 (Knowledge Graph Governance Law) — knowledge/dev/laws/dieu39-knowledge-graph-law.md (rev 15; enacted (BAN HANH v2.3, S159 2026-04-03, Council 3 rounds G…). Goal valid: Yes. Conflict: Mixed (Rollout-assumption + Evidence-dependency; goals/discipline COMPATIBLE). Action: Keep reading from laws/ as the enacted FX compatibility source. Do NOT rewrite, do NOT amend the law text. Later (separately Owner-authorized) draft a future 'Dieu 39 Compatibility/Reinterpretation Note' that PRESERVES all goals/discipline… Safety-lock: MUST NOT rewrite/amend/re-enact Dieu 39 (it is enacted; only a future compatibility/reinterpretation note is allowed). MUST NOT treat its 36 DOT-KG / 14 kg_* tables / 24-7 self-learning as live or pr…
Dieu 41 - VPS Code Operation Law v1.1 — knowledge/dev/laws/dieu41-luat-van-hanh-ma-vps-v1.1.md (rev 36; enacted (BAN HANH v1.1, 2026-04-18; amended in-place 2026-0…). Goal valid: Yes. Conflict: None / Mixed (mostly compatible; minor vocabulary-overlap and rollout-assumption notes). Action: Keep enacted and keep reading from laws/. Add a short compatibility NOTE (do NOT rewrite) clarifying: (a) Dieu 41's 'patch = miếng thông tin mã' / agent-sandbox / promotion-gate / MERGE!=DONE are the CODE-deploy analog of the new model's b… Safety-lock: Must NOT amend or rewrite Dieu 41 in this phase; must NOT treat its 'promote to trusted source' as canonical-birth or its DOT deploy-guards as the new-model checker/scanner; must NOT use the new Lego…
Dieu 5 — Kien truc 5 Tang (Five Tiers Architecture) — knowledge/dev/laws/law-05-five-tiers.md (rev 1; Enacted architectural law. Body mixes a stable layer model…). Goal valid: Yes. Conflict: Goal = no conflict. §3 'Hien trang (2026-03)' makes reported-LIVE claims (Tang2 'HOAN THA…. Action: Keep the architectural goal. Note: (a) §3 status snapshot is a dated DOCUMENTARY_ONLY claim — must NOT be cited as live evidence (all reported-live substrate downgraded; nothing Phase-1-proven); (b) Tier-5 'auto-fix' is to be interpreted u… Safety-lock: MUST NOT treat §3 status as proven-live, MUST NOT run verify_counts/pivot/scanner, MUST NOT build any tier, MUST NOT design tier remediation; survey only.
Dieu 9 - Schema Governance Law (SCR pending-enforce) — knowledge/dev/laws/law-09-schema-governance.md (rev 1; Enacted but PENDING-ENFORCE: the law has effect, but its SC…). Goal valid: Yes. Conflict: Authority-precedence clarification + substrate-liveness. §2 chain ends at 'Council review…. Action: Add a short compatibility note: the Owner gate sits ABOVE Council 'Approve' for any schema change (Council PASS authorizes nothing; Owner authorizes), and the SCR enforcement substrate is PENDING-ENFORCE / documentary (not live) - so this… Safety-lock: MUST NOT perform or design any schema change this phase; MUST NOT treat Council/engineering approval as Owner authorization; MUST NOT direct-ALTER-TABLE; survey/classify only.
LSL-01 - Luật sửa luật: Miếng thông tin (Information Unit) first v0.3 — knowledge/dev/laws/dieu38-trien-khai/LSL-01-information-unit-first.md (rev 1 (doc v0.3 B…; enacted (amendment-law, Council PASS, uploaded KB; adds NT1…). Goal valid: Yes. Conflict: Authority-model (scoped supremacy + NT15 constitution-add + Agent-finalize tiers vs CONS-…. Action: Keep as the doctrinal anchor for D4/D5 (it is the best-aligned old law to the new model). Attach a NOTE clarifying: (1) under CONS-004, LSL-01/NT15 carry KB practical-authority for laws-new design but a formal constitution amendment (NT15)… Safety-lock: Must NOT let Agent 'finalize' (low-risk tier) become a path to write canonical birth_registry or bypass the promote checker; must NOT treat NT15/supremacy clause as an enacted constitution amendment…
Điều 24 — Label Law v1.3 (Luật Nhãn) — knowledge/dev/laws/label-law.md (rev v1.3 ENACTED/…; ENACTED (frozen/ĐÓNG BĂNG). Constitutional supplement (Hiến…). Goal valid: Yes. Conflict: Soft/clause-level: fn_auto_label_assignment is an AFTER INSERT/UPDATE auto-write trigger…. Action: Keep reading from laws/. Add a short compatibility note: F0→FX treats Đ24 labels as a classification/pivot facet (governance-info), NOT as the birth CELL dimension; auto-label assignment is auto-mutation of DERIVED metadata only (bounded b… Safety-lock: MUST NOT run/alter the auto-label triggers or label_rules; MUST NOT query/touch live taxonomy/entity_labels; MUST NOT redefine labels as the canonical cell_id; MUST NOT rewrite the frozen law.
Điều 43 — System Context Law v1.2 FINAL (Luật Bản đồ Hệ thống) — knowledge/dev/laws/dieu43-system-context-law.md (rev v1.2 FINAL BA…; ENACTED (BAN HÀNH v1.2 FINAL). Council R1+R2 done + Desktop…). Goal valid: Yes. Conflict: Clause-level only: (a) §9.2.4 backfill = AI writes descriptions in batches + auto-assigns…. Action: Keep reading from laws/. Add a clarifying note: F0→FX treats Đ43's H11/context-pack scanning as ASSEMBLE-over-existing-signals (system_issues + fn_log_issue), consistent with scanner-list-only — the auto-build/publish is a documentary cont… Safety-lock: MUST NOT run the context-pack build/verify DOTs, cron, or H11 scan; MUST NOT execute the backfill pipeline or write descriptions/PROV labels; MUST NOT flip context_pack_mode to block; MUST NOT amend/…
Dieu 17-18 - Multi-domain + i18n + Change Law — knowledge/dev/laws/law-17-18-domain-change.md (rev 1; Enacted (law-17 + law-18). Most concrete workflows are mark…). Goal valid: Yes. Conflict: Mostly out-of-scope/implementation-deep rather than conflicting. Mild tension: dot-domain…. Action: Keep reading from laws/. Add a short compatibility note (do NOT rewrite): (1) the dot-domain-create / dot-*-create change workflows are INFRA orchestration outside the narrow knowledge-DOT / birth-cell core, so DOT=narrow is judged against… Safety-lock: Must NOT build/provision any domain/nginx/SSL/connector workflow or treat TD-marked workflows as existing, must NOT let 'update registries' become auto-fix, must NOT query live DB/runtime or touch pr…
Dieu 8 — Luat Phu thuoc (Dependency Law) — knowledge/dev/laws/law-08-dependency.md (rev 1; Enacted, thin law. Reports 'DA CO: entity_dependencies 90+…). Goal valid: Yes. Conflict: No conflict. The dependency graph is precisely the 'map of relations + states' the new mo…. Action: Keep. Note: entity_dependencies = relationship-info reused under the FX One-Roof (conceptual roof over the existing edge ledger, e.g. universal_edges), NOT a new central governance registry and NOT a second birth system; dot-dependency-sca… Safety-lock: MUST NOT run dot-dependency-scan against live, MUST NOT write/modify dependency edges, MUST NOT deprecate/retire anything; catalog only.

AMEND (5)

Dieu 22 - Self-Healing + Self-Improvement Law v1.2 — knowledge/dev/laws/law-22-self-healing.md (rev 22; Enacted (BAN HANH v1.2, S178 Fix 24 + Fix 29). Owns the sys…). Goal valid: Yes. Conflict: Auto-fix vs scanner-list-only. Specific conflicting clauses: §4.3 check_kind='detect_and_…. Action: Before technical design, amend the rollout assumptions (not the goal): split the law's outputs into (a) detect+list signals that feed the One-Roof list-only (KEEP) vs (b) auto-fix actions (detect_and_fix, auto_attach_trigger, auto-close-as… Safety-lock: MUST NOT enable or run any auto-fix this phase (keep hc_trigger_autofix_enabled='false', no auto_attach, no auto-close mutation, no detect_and_fix execution); MUST NOT treat engineering-green health…
Dieu 33 - PostgreSQL Law v2.1 — knowledge/dev/laws/dieu33-postgresql-law.md (rev 5; enacted (BAN HANH v2.1, base v2.0/S176 + S178 Fix 15, 2026-…). Goal valid: Partial. Conflict: Mixed (Architecture+Obsolete-substrate KEEP; specific Auto-fix/schema-change clauses conf…. Action: Keep the foundation (PG-single-enforcement, 4-DB/3-layer architecture s0, naming/canonical-field intent s2/s11.2, exceptions E1-E5 s13, 1-GSM-password s14, CI/deploy-hook legalization s15). AMEND the specific clauses that license auto-fix/… Safety-lock: Must NOT run any DOT Loai-2 auto-fix / ALTER TABLE ADD COLUMN / ALTER COLUMN TYPE / canonical_fields DDL; must NOT add dot_role/cell_id columns to dot_tools; must NOT do any schema change outside an…
Dieu 36 - Collection Protocol Law v5.0 — knowledge/dev/laws/dieu36-collection-protocol-law.md (rev 4; DRAFT 30% (v5.0 S170; Part 1 7-MT approved by NĐ-36-01, Par…). Goal valid: Partial. Conflict: Mixed (Architecture + Definitional + Evidence-dependency): goals valid but rollout assume…. Action: Keep the 7 goals (they are foundational and valid), but AMEND the rollout/mechanism clauses before technical design: (a) reconcile MT1/MT6 reverse-traceability + 'đúng chuồng'/Species-Matrix with the held CONS-003 (6-vs-7 tầng) and CELL-00… Safety-lock: Must NOT enact/finish this draft, materialize cell_id/'đúng chuồng' placement, build cascade auto-propagation, or stand up a new central classification/relationship registry while CONS-003 + CELL-003…
L4 - Birth Gate Extension (Mở rộng Điều 0-G cho Text Unit + Component) — knowledge/dev/laws/dieu38-trien-khai/L4-birth-gate-extension.md (rev 1 (DỰ THẢO —…; draft (DỰ THẢO — extension of Đ0-G Birth Registry Law v1.0)). Goal valid: Partial. Conflict: Architecture (governance-at-birth vs minimal-birth/canonical-at-promote) + Evidence-depen…. Action: Keep the goal (govern text_unit + component birth, reuse Đ0-G principle not copy — §9 pt 8). Before technical design, amend the birth-vs-promote split: (a) at birth P0 issue only TEMP_ID/minimal identity (what/species/store/owner/draft) —… Safety-lock: Must NOT enact a birth gate that writes/certifies canonical text_unit/component at INSERT or front-loads reuse-approval/governance into birth P0; must NOT call fn_birth_register/fn_birth_gate live or…
Điều 38 - Luật SQL Hoá Văn Bản v3.0 (Normative Document / Document Digitization… — knowledge/dev/laws/dieu38-normative-document-law.md (rev 2 (doc v3.0,…; draft (DRAFT — chờ Huyên duyệt; MT đã duyệt cơ bản, GP đang…). Goal valid: Yes. Conflict: Mixed (Rollout-assumption + Architecture + Evidence-dependency). Action: Keep the 3 MT goals and Semantic-Annotation product as-is. Before technical design, amend the rollout/automation clauses: (a) MT1 'DOT tự động 100%' and MT3 'Agent sửa hoặc cảnh báo → văn bản đầu ra tự sinh' must be constrained to scanner… Safety-lock: Must NOT implement 'DOT tự động 100% sửa', auto-output-regeneration, or the B2.1 auto-retire trigger as live auto-fix/auto-mutation in this phase; any retire/promote mutation stays behind a fail-clos…

REWRITE (1)

Dieu 37 - Governance Organization Law v3.3 (Luat To chuc Bo may Quan tri) — knowledge/dev/laws/dieu37-governance-organization-law.md (rev 5; enacted (BAN HANH) v3.3 — Council 2-round THONG QUA (Gemini…). Goal valid: Yes. Conflict: Architecture + Authority-model + Mixed (also Evidence-dependency). Action: Preserve goals; later REWRITE in laws-new/newlaws (do NOT amend in place — Đ37 is enacted/immutable, NT7 §4.7) to express the same top-down governance coverage as a conceptual One-Roof OVER existing ledgers (universal_edges + governance_ro… Safety-lock: MUST NOT amend/rewrite/re-enact Đ37 in this phase; MUST NOT call/seed any of the 6 DOTs (BOOTSTRAP/VERIFY/ONBOARD/DISCOVERY/LAW-HEALTH/CONFLICT), MUST NOT fire any of the 8 PG triggers, MUST NOT touc…

DEFER (16)

Constitution v4.2.0 Amendment Draft — +NT10 (Quản lý bằng PG) + Điều 28 v2.0 — knowledge/dev/laws/constitution-v4.2.0-amendment-draft.md (rev 3; superseded (old draft; both changes already absorbed into e…). Goal valid: Yes. Conflict: Obsolete (superseded by the enacted v4.6.3; not a live authority). Action: DEFER: classify as a superseded historical draft. No action needed before technical design. Do NOT read from it as authority (read enacted v4.6.3 instead); keep only for provenance/trace of how NT10 + Điều 28 entered the constitution. If t… Safety-lock: MUST NOT cite this draft as current/standalone authority (use enacted v4.6.3); MUST NOT amend/rewrite it; MUST NOT treat NT numbering here (10 principles) as current (the enacted text now has 15 NT).
D28 Implementation Bucket (Display Technology) - knowledge/dev/laws/dieu28-trie… — knowledge/dev/laws/dieu28-trien-khai/ (rev (bucket); implementation). Goal valid: Partial. Conflict: Obsolete. Action: Defer as a single bucket; no per-file law classification. Retain for D28 implementation history; not a merge subject. Safety-lock: Do not treat any file here as a standalone law or as authority; do not re-run deploy/smoke prompts; read-only.
D38 Text-as-Code Implementation Bucket - knowledge/dev/laws/dieu38-trien-khai/ — knowledge/dev/laws/dieu38-trien-khai/ (rev (bucket); implementation). Goal valid: Partial. Conflict: Mixed. Action: Defer as one bucket. EXCLUDE LSL-01 (knowledge/dev/laws/dieu38-trien-khai/LSL-01-information-unit-first.md) and L4 (knowledge/dev/laws/dieu38-trien-khai/L4-birth-gate-extension.md) - classified elsewhere. Safety-lock: Do not enact L1/L2/L3/L5 appendix drafts as law; do not re-run G6/Gate-A production DDL or migration prompts; read-only. LSL-01 and L4 are NOT part of this bucket.
D41 Revision Rulings Bucket - knowledge/dev/laws/dieu41-revision-rulings/ — knowledge/dev/laws/dieu41-revision-rulings/ (rev (bucket); process). Goal valid: Partial. Conflict: None. Action: Defer as one bucket; Codex revision reports are review process records, not law text. Safety-lock: Do not treat revision reports as authority/law; read-only. The enacted D41 law is dieu41-luat-van-hanh-ma-vps-v1.1.md, not these reports.
D43 Migrations Bucket (System Context) - knowledge/dev/laws/dieu43-migrations/ — knowledge/dev/laws/dieu43-migrations/ (rev (bucket); implementation). Goal valid: Partial. Conflict: Obsolete. Action: Defer as one bucket. Note the actual D43 standalone law is dieu43-system-context-law.md (enacted v1.2 FINAL); this folder is implementation SQL + apply logs only. Safety-lock: Do not re-execute migration SQL (00-08) against any DB; read-only. These .sql files are applied-history artifacts, not re-runnable scripts in this pass.
D44 UOSL Implementation Bucket - knowledge/dev/laws/dieu44-trien-khai/ — knowledge/dev/laws/dieu44-trien-khai/ (rev (bucket); implementation). Goal valid: Partial. Conflict: Mixed. Action: Defer as one bucket. EXCLUDE README (knowledge/dev/laws/dieu44-trien-khai/README.md) - classified elsewhere. The standalone D44 law text (dieu44-universal-object-schema-law.md) and D45 enacted law live outside this folder. Safety-lock: Do not execute any compile-only/DDL/SQL artifacts or execution prompts; do not enact D45 draft from here; read-only. README is NOT part of this bucket.
DEFER BUCKET — Superseded Đ43 drafts/backup + Đ44 UOSL GPT review (process/hist… — knowledge/dev/laws/dieu43-system-context-law-draft.md + dieu43-system… (rev D43-draft rev…; NON-AUTHORITATIVE: 3 explicitly SUPERSEDED/BACKUP Đ43 histo…). Goal valid: No. Conflict: None (non-normative history). Reading them as law would itself violate their own banners.. Action: DEFER as history/audit-only. List-confirmed present (not read in full). No action before technical design. Keep for audit trail; do not classify clause-by-clause or carry into the new model. Safety-lock: MUST NOT cite these as current law (their own banners forbid it); MUST NOT amend/restore them; MUST NOT treat the GPT review as authorization (review ≠ Authority).
Dieu 28 - Display Technology Law (Ky Thuat Hien Thi) v2.0 — knowledge/dev/laws/dieu28-display-technology-law.md (rev 1; enacted(BAN HANH) v2.0 (Council GPT 8.4 + Gemini 9.5, 2 rou…). Goal valid: Yes. Conflict: None (orthogonal; minor parallel patterns). Action: Defer for this phase: it is display-layer and implementation-specific (concrete design_templates schema, PG triggers, template_statuses ref table, DOT pairs). Not needed before technical design of the F0->F5/FX backend. Revisit only if/whe… Safety-lock: Must NOT be pulled into F0->F5 birth/stamp/promote design as if it governed the data layer; must NOT treat its coverage scanner as the One-Roof/F5 scanner. No template schema change, no DOT registrat…
Dieu 3 - Appendix: Description Templates (Phu Luc Description Templates) — knowledge/dev/laws/dieu3-phu-luc-description-templates.md (rev 3; appendix / documentation-mirror (NOT enacted law text); run…). Goal valid: Yes. Conflict: None. Action: Defer: this is an appendix / documentation-mirror whose runtime SSOT is dot_config; it is implementation-specific description formatting and is not needed before the F0->F5/FX technical design. Leave as-is; revisit only when description me… Safety-lock: Must NOT be treated as a runtime source of truth (its own header says runtime SSOT = dot_config; update dot_config FIRST). No dot_config write, no description regeneration, no template change in this…
Dieu 34 - Workflow Law v1.0 — knowledge/dev/laws/dieu34-workflow-law.md (rev 1; draft (v1.0, S145, 'Cho hoi dong AI review' - NOT enacted)). Goal valid: Partial. Conflict: Mixed (Obsolete/draft + Rollout-assumption big-bang + Architecture birth-on-create; goal-…. Action: DEFER: it is an unenacted DRAFT awaiting AI-council review, deeply implementation-specific (named DOT tools, node-type catalog, block_library, BPMN regeneration, 4-phase rollout), and NOT a foundation law the Matrix/Stamp refactor must rec… Safety-lock: Must NOT treat this draft as enacted authority; must NOT build/run the named workflow DOT tools or write WF/node birth rows; must NOT create workflow_node_types/block_library tables or any schema; mu…
Dieu 35 - DOT Governance Law v5.0 FINAL (BACKUP) — knowledge/dev/laws/dieu35-dot-governance-law-v5-0-backup.md (rev 1; backup / superseded (explicit banner 'SUPERSEDED by v5.1 FI…). Goal valid: Partial. Conflict: Obsolete. Action: Defer: backup/superseded stub. Do not classify, amend, or build compatibility notes here. Retain for v5.0<->v5.1 audit only. The enacted lens is v5.2 FINAL. Safety-lock: MUST NOT: treat as current/authoritative; MUST NOT reference in code/law/prompt; MUST NOT run anything from it; no amend/rewrite (frozen backup under AP-21).
Dieu 35 - DOT Governance Law v5.1 DRAFT — knowledge/dev/laws/dieu35-dot-governance-law-v5-1-draft.md (rev 11; draft / superseded (carries explicit top banner: 'FILE NAY…). Goal valid: Partial. Conflict: Obsolete. Action: Defer: do not classify or amend separately. It is explicitly superseded by the enacted file and retained only for audit. Any compatibility note belongs on v5.2 FINAL, not here. Leave in place; do not reference in code/law/prompt (per its o… Safety-lock: MUST NOT: treat this draft as authoritative or current; MUST NOT cite it in new code/law/prompt; MUST NOT run any SQL/migration/function it contains; no amend/rewrite (it is a frozen audit artifact u…
Dieu 41 - Appendix: Deployment Plan (Living Doc) — knowledge/dev/laws/dieu41-phu-luc-ke-hoach-trien-khai.md (rev 32; implementation / living-doc appendix (non-enacted, continuo…). Goal valid: Yes. Conflict: Evidence-dependency / Obsolete (status snapshots) / Implementation. Action: Defer for this merge phase: it is a living implementation/forensic tracker, not a law to keep/amend/rewrite. Leave it in laws/ as a Dieu 41 sub-artifact. Its DURABLE findings (fn_birth_gate warning-only = RISK-BYPASS confirmation; dot-dot-… Safety-lock: Must NOT treat this living-doc's time-stamped runtime claims (row counts, '5 tables missing', 'KB protection LIVE', 'DONE' checkpoints) as current live proof; must NOT execute any of its 14 TODO / CL…
Dieu 44 - UOSL implementation README (standalone law not found) — knowledge/dev/laws/dieu44-trien-khai/README.md (rev 1; implementation/process support folder README (P44-0). Dieu…). Goal valid: Yes. Conflict: None (process/implementation scaffolding; not a normative law). Action: Defer: this is an implementation/process README for a not-yet-enacted law (Đ44 v0.1.2 controlled DRAFT) and the standalone Đ44 law text is absent from this corpus, so there is no enacted/normative target to KEEP/AMEND/REWRITE here. Leave t… Safety-lock: Must NOT treat this README as enacted law or as authorization to build Family Registry/SCMR/Profile Registry/new schema stores; must NOT start UOSL implementation, DDL, or migration (the README itsel…
Superseded D41 Drafts + Council Review Requests Bucket — knowledge/dev/laws/dieu41-luat-van-hanh-ma-vps-draft-v0.{2,3,4,5,5.1}… (rev (bucket); superseded). Goal valid: No. Conflict: Obsolete. Action: Defer as one superseded bucket; the enacted text is knowledge/dev/laws/dieu41-luat-van-hanh-ma-vps-v1.1.md (BAN HANH). Do not merge drafts. Safety-lock: Do not cite/enact any v0.x draft as current law; superseded by v1.1. Read-only.
Điều 44 — Universal Object Schema Law (UOSL) v0.1.2 — knowledge/dev/laws/dieu44-universal-object-schema-law.md (rev v0.1.2 contro…; NOT ENACTED — explicitly 'controlled DRAFT, CHƯA CÓ HIỆU LỰ…). Goal valid: Partial. Conflict: Structural + clause + authority: (1) DRAFT not enacted (Eng≠Authority). (2) §9.1 Correctn…. Action: DEFER: it is a controlled DRAFT (not enacted, do NOT apply as law) AND its structural/authority reconciliation with F0→FX is deep AND it is not needed before technical design of the new Lego/DOT/stamp/checker model. Park alongside the FX c… Safety-lock: MUST NOT apply Đ44 as enacted law (it is controlled DRAFT); MUST NOT build Family Registry/SCMR/birth-gate or any §9.1 auto-fix DOT; MUST NOT resolve CONS-002/003 or the Đ44-vs-One-Roof overlap here;…

13. Missing / not-found list

Every law number the macro enumerated is accounted for. The only items with no standalone file are the Constitution-embedded articles; an initial discovery pass wrongly assumed several law-NN foundation files were missing — those were located and classified in a second pass (corrections below).

Item	Result
Điều 0 (root entity)	No standalone file — embedded in Constitution (`constitution.md`). Not NOT_FOUND content; covered by Constitution record.
Điều 0-B (composition, "7 Lớp / 33 species")	Embedded in Constitution. Origin of CONS-003 (6-vs-7 tầng).
Điều 0-G (Khai Sinh / Birth Gate)	Embedded in Constitution (no standalone `law-00g`); operative birth procedure is `law-04-birth-process.md`. See §7.6.
Điều 0-S / 0-M / 0-L	Embedded in Constitution (no standalone files; appear in `knowledge/dev/architecture/constitution-amendment-measurement.md`, not a `laws/` doc).
Điều 0-H	FOUND standalone — `law-00h-5layer-sync.md` (classified KEEP+NOTE).
Điều 1–19	ALL FOUND standalone (`law-01-…` … `law-19-…`, some combined: 10-13, 15-16, 17-18). (Correction: not missing.)
Điều 20	FOUND — `dieu20-thiet-ke-truoc-trien-khai.md` (KEEP).
Điều 22	FOUND — `law-22-self-healing.md` (AMEND). (Correction.)
Điều 24	FOUND — `label-law.md` (KEEP+NOTE). (Correction.)
Điều 43 (standalone law text)	FOUND — `dieu43-system-context-law.md` v1.2 FINAL rev51 (KEEP+NOTE); the `dieu43-migrations/` folder is implementation SQL (DEFER bucket). (Correction.)
Điều 44 (standalone law text)	FOUND — `dieu44-universal-object-schema-law.md` UOSL v0.1.2 controlled DRAFT (DEFER); `dieu44-trien-khai/` is implementation (DEFER bucket). (Correction.)
Terminology / glossary	FOUND — `terminology-glossary.md` v2.1 (KEEP+NOTE). (Correction.)

No law was invented. Where an operative clause lives in an unread embedded file (Điều 0-G), the gap is flagged rather than guessed (§7.6).

14. Conflict / HOLD log (carried, not resolved)

These are surfaced by the corpus↔new-model comparison and are explicitly not resolved in this survey (Owner-gated):

CONS-002 — which source wins the IO Contract fields (thin 5-field vs DOT/evidence/owner); blocks IO_STAMP / concrete IO contracts. Surfaced by Điều 38 Appendix-01 (Module-Contract-First lean).
CONS-003 — 6-vs-7 tầng ambiguity (Constitution Điều 0-B / Điều 29 "7 dimensions" vs drafts' 6-tầng); blocks any cell_id / CELL_STAMP. Surfaced by Constitution, Điều 29, Điều 26, Điều 36, Terminology.
CONS-004 / CONS-005 — authority order + freeze baseline decided at F0 as working precedence / KB-only; cross-class stays Owner-gated; not re-opened here.
CELL-003 / 004 / 007 — cell_id collection/species/tầng dimensions unmaterialized; block cell placement. Surfaced by Điều 36, Điều 29, Điều 2.
HOLD-1 — iu_staging_* pre-promote staging liveness unproven, Phase-1-gated. (Điều 38 family, F2.)
HOLD-2 — atomic promote has no real transaction; blocks any canonical/BIRTH_STAMP write at promote. (Điều 4, Điều 38 v3.0 B2.1, Điều 39, L4.)
RISK-BYPASS — fn_birth_gate mode=warn + app.bypass_birth_gate kill-switch and the confirmed live fn_auto_approve_add authority bypass (160 unvoted applies); the gate cannot be trusted to block until Phase-1-verified + closed. (Điều 35, Điều 37, Điều 39, Điều 4, L4, Điều 41 appendix forensic evidence.)
PRODUCTION READINESS FAIL — the live Điều 35 governance substrate audited not production-certified; Council/Engineering PASS ≠ production-ready.
Điều 39 runtime EMPTY — enacted but ~unimplemented (registered ≠ executed).
RISK-GC / RISK-CAP / RISK-IDX (no full-table-scan) / RISK-AP/STL/RUN/CRASH/TIME, STG-012 / STG-015 / STG-REUSE-001/003, DOT-CAP-001/004/006/010, GOV-016/017 (no risk/blast-radius calculator; no fail-closed-on-uncomputable-risk code), GOV-REUSE-001 (unproven whether universal_edges/governance_role/owner can hold the minimal governance graph) — all open survey/design gates.

15. Recommendation for next macros

GPT review of this catalog (scope-control + classification sanity).
Codex review of this catalog (control verdict; PASS ≠ Owner authorization).
Owner decides batches — suggested sequencing, each Owner-gated and separately authorized:
- Batch A (note): the High-priority KEEP+NOTE compatibility notes that gate technical design — Constitution, Điều 39, Điều 35, Điều 29, Điều 31, Điều 32, Điều 38 Appendix-01, Điều 0-H, Điều 1, Điều 4, Điều 19, Terminology. (Written later in newlaws/, never inside laws/.)
- Batch B (amend): Điều 33, Điều 36, Điều 38 v3.0, L4, Điều 22 — amend the auto-fix / schema-auto-change / birth-at-INSERT clauses to fit list-only / canonical-at-promote.
- Batch C (rewrite): Điều 37 — the goals-preserving One-Roof rewrite (per the §7.2 checklist).
- Batch D (verify): a scoped, read-only Phase-1 to verify the live substrate the held blockers depend on (RISK-BYPASS close, HOLD-1 iu_staging_* liveness, Điều 35 production-readiness, Điều 39 runtime) — before trusting any birth/promote/governance lane.
- Then, and only after Owner accepts the Law Merge Catalog and authorizes the required note/amend/rewrite batches, proceed to technical-design preparation. FX is already completed and accepted as the precondition for this Law Merge Survey; it is not rerun here.
Read the embedded Điều 0-G text (constitution.md birth section + Điều 0 / Điều 0-B) in a later assigned pass to firm up the Birth special-section conclusions.

Default disposition until Owner acts: HOLD.

16. Non-authorization confirmation

no law amendment: confirmed — none produced.
no rewrite: confirmed.
no technical design: confirmed.
no Phase-1: confirmed.
no DB/runtime query: confirmed — KB-only; all substrate documentary.
no implementation: confirmed.
no authority change: confirmed — CONS-004 used as-decided, not altered.
no edit/move/delete under knowledge/dev/laws/: confirmed — read-only.
no rename of laws/ or laws-new/: confirmed.
held blockers (CONS/CELL/HOLD/RISK/GOV/STG/DOT-CAP): carried, none resolved.

PASS means only: the Law Merge Catalog is complete enough for GPT/Codex/Owner review. It authorizes nothing.