Law Revision — Workstream D0: Consolidation Planning Packet

Status: Planning & decision-support only. READ-ONLY · NON-ENACTING · NON-AUTHORIZING. Created: 2026-06-17 · Law Revision Workstream D0 · rev1. What this is: A plan for how the completed Law-Revision drafting work (Workstreams A / B0 / B1 / B2 / C) could later be consolidated into a single "current working understanding" — and the Owner decision required before any consolidation happens. It does not consolidate anything, does not create a current corpus, and does not change any law. Basis (all under knowledge/dev/laws-new/newlaws/, all read first-hand for this packet): law-merge-catalog-2026-06-16.md (rev1, 53 records) · law-merge-execution-report-2026-06-16.md (rev2) · LAW_READING_INDEX.md (rev1, Workstream A) · reports/law-revision-workstream-a-execution-report-2026-06-17.md (PARTIAL) · reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md (COMPLETE-as-navigation) · reports/law-revision-workstream-b0-b1-execution-report-2026-06-17.md (rev8, PASS) · reports/law-revision-workstream-b2-execution-report-2026-06-17.md (rev10, PASS) · reports/law-revision-workstream-c-dieu37-rewrite-execution-report-2026-06-17.md (PARTIAL) · the 5 AMEND drafts under amendments/ · the 1 REWRITE draft under rewrites/ · the 8 compatibility notes under notes/. Control status of the basis: the Law-Merge survey bundle PASSED Codex review; Workstreams A / B0+B1 / B2 / C are each "Ready for Codex review" and (per the auto-memory) carried through the GPT → Codex chain as drafts. Codex / Council / GPT PASS ≠ Owner authorization. Engineering PASS ≠ Authority PASS. This D0 packet has not yet been Codex-reviewed; it is itself a draft for the GPT → Codex → Owner chain. Companion: consolidation/owner-decision-matrix-law-revision-2026-06-17.md (D0.2) presents the four clean Owner decision options. reports/law-revision-workstream-d0-consolidation-planning-execution-report-2026-06-17.md (D0.3) is the execution report.

1. Scope and non-authorization

1.1 What D0 is

D0 is the consolidation-planning gate. Workstreams A → B0 → B1 → B2 → C produced the materials for a future consolidated reading of the law corpus (a reading index, 8 compatibility notes, 5 amendment drafts, 1 rewrite draft, and a source-recovery map). D0 lays out how those materials would be assembled into a single current working understanding and asks the Owner to choose whether, and how, to proceed — without assembling anything yet.

1.2 What D0 is NOT (hard non-authorization)

This packet, by itself, authorizes nothing. Specifically it does not:

create a current corpus (newlaws/current/, laws-current/, current/, etc.) — none is created;
copy, move, rename, or edit any file under knowledge/dev/laws/ (the old laws stay exactly where and as they are);
copy law files into newlaws/ or into any "current" location;
enact, adopt, or put into force any note, amendment, or rewrite;
declare any current law changed;
write technical design, run Phase-1, run any live DB/runtime query, or implement schema/table/registry/index;
resolve any blocker (§10), change the authority order, change the v0.1 baseline, or promote v0.2-hardening (§ "Tool-Kiem-Thu lock").

D0 produces exactly three documents (this packet, the Owner decision matrix, the execution report), all under newlaws/consolidation/ and newlaws/reports/. Nothing else is created, moved, or changed.

1.3 The standing discipline (carried verbatim from every prior workstream)

Codex/GPT/Council PASS ≠ Owner authorization. Engineering PASS / scanner PASS / health PASS / test PASS / registration PASS ≠ authority PASS. Default disposition: HOLD.

"Accepted by Codex" means usable for Owner/User decision — it does not mean enacted, consolidated, current, technical-design-authorized, Phase-1-authorized, or implementation-authorized.

2. Summary of the completed workstreams (A / B0 / B1 / B2 / C)

All five are read-only, KB-only, non-enacting. Together they processed the entire 53-record Law-Merge catalog into a reuse-first reading layer. Nothing was enacted; knowledge/dev/laws/ was never touched.

WS	Output (under `newlaws/`)	Status	What it produced	Control
Catalog (pre-A basis)	`law-merge-catalog-2026-06-16.md` (rev1) + `law-merge-execution-report-2026-06-16.md` (rev2)	PASS (catalog)	53-record reuse-first classification of the old corpus vs F0→F5/FX: KEEP 6 · KEEP+NOTE 25 · AMEND 5 · REWRITE 1 · DEFER 16. Corpus = "restaged, not replaced."	Survey bundle PASSED Codex (folder-policy HOLD raised then cleared).
A	`LAW_READING_INDEX.md` + 8 compatibility notes (`notes/`) + birth-embedded check (`reports/…`) + WS-A report	PARTIAL (honest, non-blocking)	Mapped all 53 records to 5 reading categories; wrote the 8 highest-priority KEEP+NOTE notes (the technical-design-gating ones); recorded the safety lock. PARTIAL because Đ0/0-B/0-G are not embedded in the Constitution — they live in `architecture/`.	"Ready for Codex review: YES."
B0	`reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md`	COMPLETE (as a navigation/provenance report)	Located the operative Đ0/0-B/0-G texts in `architecture/`; confirmed the Constitution's `law-00.md` references are broken* (absent from `laws/`); surfaced 5 Owner-gated open items (§9). Moved/renamed/patched nothing.	Engineering COMPLETE; Codex PASS ≠ Owner auth.
B1	`amendments/dieu22-self-healing-amendment-draft.md` + `amendments/dieu33-postgresql-law-amendment-draft.md` + report (rev8)	PASS (review-ready, not adoption-ready)	DRAFT amendments for Điều 22 (auto-fix → proposal-only) and Điều 33 (block auto-DDL / schema-auto-change before design). Goals preserved; only unsafe rollout reframed.	"Ready for Codex review: YES."
B2	`amendments/dieu36-…` + `amendments/l4-birth-gate-extension-…` + `amendments/dieu38-normative-document-law-v3-…` + report (rev10)	PASS (draft-amendment package, review-ready)	The remaining 3 AMEND drafts — Điều 36 (block cell_id/Species-Matrix materialization + scanner auto-reclassify while CONS-003+CELL open), L4 (relocate completeness/reuse/approval from INSERT to promote checker; TEMP at INSERT, canonical at promote/F4), Điều 38 v3.0 (constrain "DOT 100%"/auto-output-regen to scanner+checker+render-at-promote). Includes a first-hand source re-verification pass (all CONFIRM; Đ39 = PARTIAL).	"Ready for Codex review: yes."
C	`rewrites/dieu37-governance-organization-law-rewrite-draft.md` (rev1) + report	PARTIAL (honest, non-blocking)	The lone REWRITE: Điều 37 — preserve 10 governance goals (G1–G10), retire 7 mechanisms (R1–R7: central `governance_registry`, 6 auto-cron DOTs, auto-onboard/inherit, 8-trigger enforcement machine, Council-vote/auto-DROP, big-bang seed, in-law schema), replace with One-Roof-over-existing-ledgers + 4 primitives + Owner/Đ32 gate. PARTIAL because several load-bearing facts (RISK-BYPASS / Đ35 prod-readiness / Đ39 runtime) are runtime/Phase-1 observations carried as claims, not KB-verifiable proofs.	"Ready for Codex review: YES."

Net result of A→C: every one of the 5 AMEND records and the 1 REWRITE record now has a non-enacting DRAFT in newlaws/; 8 of the 25 KEEP+NOTE records have a written compatibility note; the 6 KEEP records and 17 of the 25 KEEP+NOTE records have no new artifact (and need none / not-yet, respectively). No blocker was resolved in any workstream.

3. Full 53-record consolidation matrix

Records are in catalog order (action-first: REWRITE → AMEND → KEEP+NOTE → KEEP → DEFER). Disposition is exact from the catalog. Reading rule (D0) is the recommended current reading rule (§4). Consolidation artifact is the newlaws/ draft/note that exists for that record, if any (✗ = none exists / none needed).

#	Old-law identity (`laws/…` unless noted)	Short title	Disposition	Reading rule (D0)	Consolidation artifact
1	`dieu37-governance-organization-law.md`	Governance Organization Law v3.3	REWRITE	READ_REWRITE_DRAFT_PENDING_OWNER	`rewrites/dieu37-governance-organization-law-rewrite-draft.md`
2	`law-22-self-healing.md`	Self-Healing + Self-Improvement v1.2	AMEND	READ_AMENDMENT_DRAFT_PENDING_OWNER	`amendments/dieu22-self-healing-amendment-draft.md`
3	`dieu33-postgresql-law.md`	PostgreSQL Law v2.1	AMEND	READ_AMENDMENT_DRAFT_PENDING_OWNER	`amendments/dieu33-postgresql-law-amendment-draft.md`
4	`dieu36-collection-protocol-law.md`	Collection Protocol v5.0 (DRAFT 30%)	AMEND	READ_AMENDMENT_DRAFT_PENDING_OWNER	`amendments/dieu36-collection-protocol-amendment-draft.md`
5	`dieu38-trien-khai/L4-birth-gate-extension.md`	L4 Birth Gate Extension (mở rộng Đ0-G)	AMEND	READ_AMENDMENT_DRAFT_PENDING_OWNER	`amendments/l4-birth-gate-extension-amendment-draft.md`
6	`dieu38-normative-document-law.md`	SQL Hoá Văn Bản v3.0 (DRAFT)	AMEND	READ_AMENDMENT_DRAFT_PENDING_OWNER	`amendments/dieu38-normative-document-law-v3-amendment-draft.md`
7	`law-00h-5layer-sync.md`	Điều 0-H — Đồng bộ 5 Tầng	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
8	`law-01-foundation-principles.md`	Điều 1 — Foundation Principles (15 NT)	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu1-foundation-principles-compatibility-note.md`
9	`dieu29-classification-law.md`	Điều 29 — Collection Classification v2.0	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
10	`dieu31-system-integrity-law.md`	Điều 31 — System Integrity v1.2	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
11	`dieu32-approval-law.md`	Điều 32 — Approval (APR) v1.1	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu32-approval-owner-gate-compatibility-note.md`
12	`dieu35-dot-governance-law.md`	Điều 35 — DOT Governance v5.2 FINAL	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu35-dot-governance-compatibility-note.md`
13	`law-04-birth-process.md`	Điều 4 — Birth Process (Luật Sinh sản)	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu4-birth-process-compatibility-note.md`
14	`constitution.md`	Constitution v4.6.3 (SUPREME)	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/constitution-compatibility-note.md`
15	`terminology-glossary.md`	Terminology Glossary v2.1	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/terminology-compatibility-note.md`
16	`dieu38-appendix-01-objectives.md`	Điều 38 Phụ lục 01 — Text-as-Code Objectives	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu38-text-as-code-appendix01-compatibility-note.md`
17	`law-10-13-operations.md`	Điều 10-13 — Operations	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
18	`law-14-no-duplicate.md`	Điều 14 — Anti-Duplicate (3 cấp)	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
19	`law-19-orphan-scanner.md`	Điều 19 — Orphan Scanner (Side B)	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
20	`law-02-registry.md`	Điều 2 — Registry (23 prefix)	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
21	`dieu26-pivot-law.md`	Điều 26 — Pivot v4.0	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
22	`law-03-metadata.md`	Điều 3 — Metadata	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
23	`dieu39-knowledge-graph-law.md`	Điều 39 — Knowledge Graph v2.3	KEEP+NOTE	READ_OLD_WITH_NOTE (note exists)	`notes/dieu39-knowledge-graph-compatibility-note.md`
24	`dieu41-luat-van-hanh-ma-vps-v1.1.md`	Điều 41 — VPS Code Operation v1.1	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
25	`law-05-five-tiers.md`	Điều 5 — Kiến trúc 5 Tầng	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
26	`law-09-schema-governance.md`	Điều 9 — Schema Governance (SCR)	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
27	`dieu38-trien-khai/LSL-01-information-unit-first.md`	LSL-01 — Information Unit First v0.3	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
28	`label-law.md`	Điều 24 — Label Law v1.3 (frozen)	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
29	`dieu43-system-context-law.md`	Điều 43 — System Context v1.2 FINAL	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
30	`law-17-18-domain-change.md`	Điều 17-18 — Multi-domain + i18n + Change	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
31	`law-08-dependency.md`	Điều 8 — Dependency Law	KEEP+NOTE	READ_OLD_WITH_NOTE (note not yet written)	✗ (future Batch-A note)
32	`dieu20-thiet-ke-truoc-trien-khai.md`	Điều 20 — Design Before Execution v1.2	KEEP	READ_OLD_AS_IS	✗ (none needed)
33	`dieu30-regression-protection-law.md`	Điều 30 — Regression Protection v1.2	KEEP	READ_OLD_AS_IS	✗ (none needed)
34	`ssot/operating-rules.md`	Operating Rules v7.58 (Concise)	KEEP	READ_OLD_AS_IS	✗ (none needed)
35	`law-15-16-state-checkpoint.md`	Điều 15-16 — State Machine + Checkpoint	KEEP	READ_OLD_AS_IS	✗ (none needed)
36	`law-06-sync.md`	Điều 6 — Sync Law	KEEP	READ_OLD_AS_IS	✗ (none needed)
37	`law-07-assembly-first.md`	Điều 7 — Assembly First (Luật Tận dụng)	KEEP	READ_OLD_AS_IS	✗ (none needed)
38	`constitution-v4.2.0-amendment-draft.md`	Constitution v4.2.0 Amendment Draft	DEFER	DEFER_DO_NOT_USE	✗ (superseded by enacted v4.6.3)
39	`dieu28-trien-khai/` (bucket, ~27 files)	D28 Display Tech implementation bucket	DEFER	DEFER_DO_NOT_USE	✗
40	`dieu38-trien-khai/` (bucket, ~150 files)	D38 Text-as-Code implementation bucket	DEFER	DEFER_DO_NOT_USE	✗ (excl. #5 L4, #27 LSL-01)
41	`dieu41-revision-rulings/` (bucket, 2 files)	D41 Revision Rulings bucket	DEFER	DEFER_DO_NOT_USE	✗
42	`dieu43-migrations/` (bucket, 23 files)	D43 Migrations bucket	DEFER	DEFER_DO_NOT_USE	✗
43	`dieu44-trien-khai/` (bucket, ~350+ files)	D44 UOSL implementation bucket	DEFER	DEFER_DO_NOT_USE	✗ (excl. #51 README)
44	`dieu43-system-context-law-draft.md` + others	Superseded Đ43 drafts/backup + Đ44 UOSL GPT-review	DEFER	DEFER_DO_NOT_USE	✗
45	`dieu28-display-technology-law.md`	Điều 28 — Display Technology Law v2.0	DEFER	DEFER_DO_NOT_USE	✗
46	`dieu3-phu-luc-description-templates.md`	Điều 3 Phụ lục — Description Templates	DEFER	DEFER_DO_NOT_USE	✗
47	`dieu34-workflow-law.md`	Điều 34 — Workflow Law v1.0 (unenacted draft)	DEFER	DEFER_DO_NOT_USE	✗
48	`dieu35-dot-governance-law-v5-0-backup.md`	Điều 35 v5.0 FINAL (BACKUP)	DEFER	DEFER_DO_NOT_USE	✗ (superseded by v5.2)
49	`dieu35-dot-governance-law-v5-1-draft.md`	Điều 35 v5.1 DRAFT	DEFER	DEFER_DO_NOT_USE	✗ (superseded by v5.2)
50	`dieu41-phu-luc-ke-hoach-trien-khai.md`	Điều 41 Phụ lục — Deployment Plan (living doc)	DEFER	DEFER_DO_NOT_USE	✗
51	`dieu44-trien-khai/README.md`	Điều 44 — UOSL implementation README	DEFER	DEFER_DO_NOT_USE	✗
52	`dieu41-luat-van-hanh-ma-vps-draft-v0.{2..5.1}` (bucket, 7 files)	Superseded D41 drafts + Council Review Requests	DEFER	DEFER_DO_NOT_USE	✗ (superseded by v1.1)
53	`dieu44-universal-object-schema-law.md`	Điều 44 — UOSL v0.1.2 (controlled DRAFT)	DEFER	DEFER_DO_NOT_USE	✗ (not enacted)

Class totals (verified, sum = 53): KEEP 6 (records 32–37) · KEEP+NOTE 25 (records 7–31) · AMEND 5 (records 2–6) · REWRITE 1 (record 1) · DEFER 16 (records 38–53). 6 + 25 + 5 + 1 + 16 = 53.

4. Recommended reading rule for each record (the 5 categories)

Each of the 53 records gets exactly one reading rule. The five rules and their mapping from catalog disposition:

Reading rule	Means	Maps from disposition	Count
READ_OLD_AS_IS	Read the old law in `laws/` (or `ssot/`) as-is — it is compatible with F0→F5/FX.	KEEP	6
READ_OLD_WITH_NOTE	Read the old law together with its compatibility note under `newlaws/notes/`. The old law is not rewritten. (If the note is not yet written — 17 of 25 — read the old law as-is and apply the global bad-reading rejections in §13 until the note exists.)	KEEP+NOTE	25
READ_AMENDMENT_DRAFT_PENDING_OWNER	A DRAFT amendment now exists under `newlaws/amendments/`. Read it as a proposal pending Owner, alongside the old law. The amendment is not enacted; the conflicting clauses of the old law are not yet final for new design.	AMEND	5
READ_REWRITE_DRAFT_PENDING_OWNER	A DRAFT rewrite now exists under `newlaws/rewrites/`. Read it as a proposal pending Owner, for the preserved goals + proposed new structure. The rewrite is not in force; the old law's structure/authority model is not the basis for new design.	REWRITE	1
DEFER_DO_NOT_USE	Superseded, implementation-specific, obsolete, or too deep for this phase. Audit/history only — not a source for new design now.	DEFER	16

4.1 Important: the reading rule has advanced since the Workstream-A index — but the index is unchanged

LAW_READING_INDEX.md is rev1, authored in Workstream A, before any amendment/rewrite text existed. It therefore routes the 6 AMEND/REWRITE records to READ_NEW_AMENDED_VERSION_PENDING / READ_NEW_REWRITE_VERSION_PENDING with the explicit caveat "no amendment/rewrite exists yet — read the old law as background only." That was correct then.

After Workstreams B1 / B2 / C, the 5 AMEND drafts and the 1 REWRITE draft now exist. So the current reading rule for those 6 records advances to READ_AMENDMENT_DRAFT_PENDING_OWNER / READ_REWRITE_DRAFT_PENDING_OWNER (read the draft as a pending proposal). D0 records this advanced reading rule here; it does NOT edit LAW_READING_INDEX.md. Re-pointing the index at the new drafts is an Owner-gated change reserved for a future consolidation step (see §11). Until then, the index file is partially stale for exactly these 6 records, and this packet is the authoritative pointer.

5. The 5 AMEND drafts mapped to their old-law records

All five are rev1, DRAFT · NON-ENACTING · READ-ONLY · NON-AUTHORIZING. Each preserves the old law's goals and reframes only the unsafe automation/rollout. None is an enacted amendment. The recurring discipline across all five: scanner detects/lists/proposes; any mutation requires design (NT15/Đ20) → checker (F4) → Owner/Mức 3/Đ32 → regression (Đ30).

#	AMEND draft (`newlaws/amendments/…`)	Old-law record mapped (`laws/…`)	PRESERVE (goals kept)	REFRAME / BLOCK (unsafe rollout re-scoped)	Blockers carried
2	`dieu22-self-healing-amendment-draft.md`	Điều 22 Self-Healing v1.2 BAN HÀNH (`law-22-self-healing.md`)	detect→list→propose→learn loop; double-entry; expose-all; silent-fail ban; two-engine ("DOT = nhiệt kế")	genuine auto-fix → proposal-only (steps ③, issue auto-close/reopen, `detect_and_fix`/`auto_fix_action`, HC-TRIGGER auto-attach, regex auto-rewrite carve-out removed); canonical safe path = Đ35 §6.2 `fix_repair_dot`	RISK-BYPASS, HOLD-2, CONS-003, CELL
3	`dieu33-postgresql-law-amendment-draft.md`	Điều 33 PostgreSQL v2.1 BAN HÀNH (`dieu33-postgresql-law.md`)	PG = sole enforcement/truth; 4-DB; 3-layer Não/Kho/Cổng; naming; canonical-field discipline; migration discipline; E1–E5	"schema detected & proposed, never mutated, automatically" — auto-`ALTER`→propose; DDL never Loại-2; `canonical_fields`/`dot_role`/`cell_id` materialization deferred while CONS-003+CELL open	CONS-003, CELL-003/004/007, HOLD-2, RISK-BYPASS/GC/CAP, CONS-002
4	`dieu36-collection-protocol-amendment-draft.md`	Điều 36 Collection Protocol v5.0 DRAFT (`dieu36-collection-protocol-law.md`; v4.0 was ENACTED)	the 7 goals MT1–MT7 (reverse-trace, propagation, grouping via `governance_role`, lifecycle, đúng chuồng)	Species Matrix + cell placement NOT auto-generated/materialized while CONS-003+CELL open; bi-directional auto-propagation, DOT-ORPHAN auto-apply, auto-reclassify, HC-SCHEMA→auto-DDL → detect+propose; reverse-trace = listed observation, not canonical proof	CONS-003, CELL-003/004/007, HOLD-2, RISK-BYPASS/GC/CAP, CONS-002, source-location
5	`l4-birth-gate-extension-amendment-draft.md`	L4 Birth Gate Extension DỰ THẢO (`dieu38-trien-khai/L4-birth-gate-extension.md`)	"no text-unit/component born bad"; birth-gate checks completeness not correctness; reuse-decision requirement; human-approval-not-self-grant; reuse Đ0-G principle not schema	INSERT = identity-root + TEMP/uncertified (`certified=false`); completeness-final + reuse-adjudication + approval + BIRTH_STAMP/PROMOTE_STAMP relocate to promote checker (F4); no auto-certify at INSERT; canonical never at INSERT	HOLD-2 (primary), RISK-BYPASS, CONS-003, CELL, source-location
6	`dieu38-normative-document-law-v3-amendment-draft.md`	Điều 38 SQL Hoá Văn Bản v3.0 DRAFT (`dieu38-normative-document-law.md`)	3 MT goals (data-ize / auto-generate output / lifecycle); Text→Code→Workflow→Knowledge; Semantic Annotation (list-only); IU/Smart-Brick (`unit_version`=SSOT, file/vector=projection); LSL-01; integrity REJECT guards	"DOT 100%" = 100%-automatable detection, not auto-application; no auto-fix / no auto-output-regen / no auto-rewrite of enacted text / no auto-schema; output = render-at-promote; MT0A/MT0B = reference-only (live = thin 5-field, CONS-002 open)	CONS-002 (primary), CONS-003, CELL, Đ39 runtime-EMPTY, HOLD-1, RISK-BYPASS, coverage-scanner BUILD-NO-GO

6. The Đ37 rewrite mapped to old Đ37

REWRITE draft (`newlaws/rewrites/…`)	Old-law record mapped	Why REWRITE (not AMEND)	PRESERVE	RETIRE / REPLACE	Blockers carried
`dieu37-governance-organization-law-rewrite-draft.md` (rev1)	Record #1 — Điều 37 Governance Organization Law v3.3 BAN HÀNH (`laws/dieu37-governance-organization-law.md`, enacted/immutable per NT7)	The conflict is structural/authority-level, not a clause fix: central `governance_registry` + Council auto-DROP vote + auto-cron DOTs vs FX One-Roof-over-existing-ledgers + Owner-gate. Enacted v3.3 stays immutable; the rewrite is a future law, drafted now as a proposal.	G1–G10: top-down↔bottom-up coverage mesh; 11-question observability; gap/overlap/orphan/"luật tủ kính" detection (→ list-only); jurisdiction+enforcement as relationship facts; terminology SSOT; no-governance-orphan; owner/approval lanes; KG-aware (Đ39); the OWNER_STAMP→`governance_audit_log` + GOV_STAMP→`governance_role` tie; future-laws-declare-coverage (§0-GOV hook)	R1–R7 retire: central `governance_registry`; 6 auto-cron DOTs; auto-onboard/auto-inherit; 8 hard-REJECT trigger machine; Council-vote + auto-DROP; big-bang seed; in-law schema/DOT/trigger sections. REPLACE: One-Roof = conceptual roof OVER existing ledgers (NOT central registry, NOT 2nd birth system) + 4 primitives (DOT-narrow / stamp-marker / checker-fail-closed / scanner-list-only) + mutation lane design→checker→Owner/Đ32→Đ30. "Retire" = the future law no longer mandates the mechanism; no live table/DOT/trigger/row is dropped, disabled, or altered.	RISK-BYPASS, HOLD-1, HOLD-2, CONS-002, CONS-003, CELL-003/004/007, GOV-016/017, GOV-REUSE-001, Đ39 runtime-EMPTY, Đ35 production-readiness FAIL

7. The 8 compatibility notes mapped to their old-law records

All eight are rev1, READ-ONLY · NON-AUTHORIZING · NOT enacted law, written in newlaws/notes/ and never inside laws/. Each annotates a KEEP+NOTE record — the old law stays AS-IS; only a note is added. A note does not amend its law. These 8 are the highest-priority KEEP+NOTE notes (the ones that gate technical-design reasoning).

Note (`newlaws/notes/…`)	Old-law record mapped	What it preserves / clarifies (old law unchanged)
`constitution-compatibility-note.md`	#14 Constitution v4.6.3 (`constitution.md`, SUPREME)	Constitution stays supreme; F0→FX is a method under it. NT2/NT3 "100% automation" bounded by Owner-gate/Mức 3; NT5/NT12 self-healing = scanner list-only. Documentary fix: enacted text = 15 NT, not 13.
`terminology-compatibility-note.md`	#15 Terminology Glossary v2.1 (`terminology-glossary.md`)	Glossary stays the vocab anchor; new terms (TEMP_ID/BIRTH_STAMP, brick vs candidate, scanner vs checker, `cell_id`, One-Roof) are mapped onto it as candidate vocabulary for a future Owner-gated glossary addition — not added now.
`dieu1-foundation-principles-compatibility-note.md`	#8 Điều 1 Foundation Principles 15 NT (`law-01-foundation-principles.md`)	The 15 NT stay supreme; new model is built to satisfy them. NT2/NT3 bounded by Owner-gate + NT9 fail-closed; genuine auto-fix is Đ22's subject (→ Đ22 = AMEND, not Đ1).
`dieu32-approval-owner-gate-compatibility-note.md`	#11 Điều 32 Approval v1.1 (`dieu32-approval-law.md`)	Đ32 IS the Owner-gate/Mức-3 approval authority — not weakened; the new model routes to it. Carries "KHÔNG dùng Matrix/Stamp để né production/kernel gate."
`dieu35-dot-governance-compatibility-note.md`	#12 Điều 35 DOT Governance v5.2 FINAL (`dieu35-dot-governance-law.md`)	Đ35 stays enacted; the new model reuses the `fix_repair_dot` pattern (DETECT→PROPOSE→APPROVE→APPLY→VERIFY→CLOSE) but rejects DOT-as-engine and reads the secondary engine as scanner-list-only. "Reuse pattern, carry caveats — do not import the running system turnkey."
`dieu39-knowledge-graph-compatibility-note.md`	#23 Điều 39 Knowledge Graph v2.3 (`dieu39-knowledge-graph-law.md`)	Đ39 is the mandatory FX compatibility source; goals preserved; golden rule "AI đề xuất, không tự ban hành" = fail-closed/Mức 3. Recommends a future "Đ39 Compatibility/Reinterpretation Note" — preserve goals, deliver incrementally; do NOT authorize the one-block KG rollout.
`dieu4-birth-process-compatibility-note.md`	#13 Điều 4 Birth Process (`law-04-birth-process.md`)	Birth grants identity-root, not canonical status: `certified=false` ⇒ TEMP_ID/F1; `{certified=true}+stamps` ⇒ canonical = output at promote/F4. Why KEEP+NOTE not AMEND: Đ4/Đ0-G don't force canonical-at-INSERT; AMEND pressure lives in L4 (#5) + Đ38 v3.0 (#6).
`dieu38-text-as-code-appendix01-compatibility-note.md`	#16 Điều 38 Phụ lục 01 Objectives (`dieu38-appendix-01-objectives.md`, BAN HÀNH)	Closest enacted analogue to D4 (Information Unit/Smart Brick) + D5 (Temp Store). MT0A/MT0B read as reference-only Module-Contract-First; live IO contract is the thin 5-field one — which wins = CONS-002 open. Distinct from Đ38 v3.0 DRAFT (#6) and L4 (#5).

8. The remaining 17 KEEP+NOTE notes — identified, NOT yet written (future Batch-A work)

These 17 KEEP+NOTE records are READ_OLD_WITH_NOTE, but their compatibility note has not been written. Until each note exists, the interim reading rule is: read the old law as-is AND apply the global bad-reading rejections (§13). Writing these 17 notes is future, Owner-gated Batch-A work — D0 does not write them and does not authorize writing them.

#	Old-law record	Note status
7	Điều 0-H — Đồng bộ 5 Tầng	not yet written
9	Điều 29 — Collection Classification v2.0	not yet written
10	Điều 31 — System Integrity v1.2	not yet written
17	Điều 10-13 — Operations	not yet written
18	Điều 14 — Anti-Duplicate (3 cấp)	not yet written
19	Điều 19 — Orphan Scanner (Side B)	not yet written
20	Điều 2 — Registry (23 prefix)	not yet written
21	Điều 26 — Pivot v4.0	not yet written
22	Điều 3 — Metadata	not yet written
24	Điều 41 — VPS Code Operation v1.1	not yet written
25	Điều 5 — Kiến trúc 5 Tầng	not yet written
26	Điều 9 — Schema Governance (SCR)	not yet written
27	LSL-01 — Information Unit First v0.3	not yet written
28	Điều 24 — Label Law v1.3 (frozen)	not yet written
29	Điều 43 — System Context v1.2 FINAL	not yet written
30	Điều 17-18 — Multi-domain + i18n + Change	not yet written
31	Điều 8 — Dependency Law	not yet written

8 written + 17 not-yet-written = 25 KEEP+NOTE. Consistent.

9. Source-recovery caveats for Đ0 / 0-B / 0-G (must travel with any consolidation)

From reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md (Workstream B0). These caveats are unresolved Owner-gated items and must be attached to any future consolidation that touches birth/foundation reasoning:

The operative texts live in architecture/, not laws/: Đ0 = architecture/information-atom-law.md (v2.0, rev18); Đ0-B = architecture/composition-level-law.md (file-title v3.0 / body-header v3.1, rev22); Đ0-G = architecture/birth-registry-law.md (v1.0, rev2).
The Constitution's file pointers are broken: the Constitution MỤC LỤC references law-00-entity.md / law-00b-composition.md / law-00g-birth.md (and law-00sml-amendments.md) — all absent from laws/ (a list_documents on laws/law-00 returns only law-00h-5layer-sync.md).
architecture/ is working-source, NOT supreme: existing-law-references.md states "Constitution v4.0 (laws/) là tài liệu CHÍNH. File architecture/ = tham khảo chi tiết." The Constitution self-declares "Văn bản tối cao." ⇒ architecture/ is the temporary/detailed working source for the text of Đ0/0-B/0-G but is not supreme and not the enacting authority by itself. Where they disagree = an Owner-gated reconciliation item, not an architecture/ win.
The 5 Owner-gated open items (unresolved): (1) broken Constitution law-00*.md references; (2) Đ0-B version drift v3.0 (file title) vs v3.1 (body) vs v3.0 (existing-law-references.md); (3) CONS-003 — 6 vs 7: composition_level enum = 6 Lớp (atom/molecule/compound/material/product/building) vs Constitution index "7 Lớp" / Đ29 "7 dimensions" / schema "6+1…meta" — root of CONS-003, gating any cell_id/canonical matrix; (4) the "authoritative-current" question (are the architecture/ versions the authoritative current texts, or documentary ancestors the Constitution meant to supersede via the missing law-00*.md); (5) law-00sml-amendments.md absent (the present file appears to be architecture/constitution-amendment-measurement.md v3.8 — flagged, not confirmed).
Discipline: the Constitution has NOT been patched, and must not be in this workstream. Until an Owner-gated source-recovery pass reconciles these, read Đ0/0-B/0-G from the three architecture/ files as temporary working source and do not build birth-related technical design on them.

10. Blockers that must stay open

D0 resolves none of these. They are carried, unresolved, and must remain open through any consolidation step. (Consolidation as a non-enacting reading/provenance layer does not require resolving them; technical design, Phase-1, and implementation do.)

Blocker	What it is	Why it must stay open
RISK-BYPASS	live `fn_auto_approve_add` (160 unvoted applies) + `fn_birth_gate` warn-mode + `app.bypass_birth_gate` kill-switch	An authority bypass exists in the live substrate; the gate cannot be trusted to block until Phase-1-verified and closed.
HOLD-1	`iu_staging_*` pre-promote staging liveness unproven	Documentary only; Phase-1-gated.
HOLD-2	atomic promote has no real transaction	Blocks the canonical / BIRTH_STAMP / PROMOTE_STAMP write at promote (F4).
CONS-002	IO Contract field-set: thin 5-field vs Module-Contract-First (MT0A/MT0B)	Blocks IO_STAMP; unresolved which source wins.
CONS-003	6-Lớp (`composition_level`) vs 7-dimension (Constitution/Đ29)	Blocks any `cell_id` and the canonical matrix.
CELL-003/004/007	`cell_id` dimensions (collection/species/tầng/store/domain) unmaterialized	The birth CELL is the only canonical matrix; it cannot be materialized while CONS-003 open.
GOV-016/017	no risk/blast-radius calculator; no fail-closed-on-uncomputable-risk code	Governance risk cannot be computed/enforced fail-closed yet.
GOV-REUSE-001	unproven whether `universal_edges`/`governance_role`/owner can hold the minimal governance graph	The One-Roof "facts over existing ledgers" model is not yet proven feasible on the live substrate.
Đ39 runtime-EMPTY	enacted but ~unimplemented (registered ≠ executed: 0 DOT exec / 0 KG events; owner unregistered; registry IUs `lifecycle_status=draft`)	The KG law is not live; rollout is not authorized.
Đ35 production-readiness FAIL	audit checkpoint-codex-2026-06-05: "CORE AUDIT PASS / PRODUCTION READINESS FAIL"; 14/14 health checks not LIVE	The live Đ35 governance substrate is not production-certified.
source-recovery Đ0/0-B/0-G	broken Constitution refs + `architecture/`-as-working-source + Đ0-B version drift + CONS-003 root + `law-00sml` absent (§9)	Foundation-text provenance is unreconciled; birth technical design is gated on it.
Carried context	STG-012/015, STG-REUSE-001/003, DOT-CAP-001/004/006/010, RISK-GC/CAP/IDX/AP/STL/RUN/CRASH/TIME	Open survey/operational-risk gates from earlier F-passes; none in scope for D0.

Recorded as DECIDED (not blockers): CONS-004 (authority order) and CONS-005 (freeze-candidate baseline) were decided at F0; they are not re-opened by D0.

11. What is allowed AFTER the Owner accepts planning

Owner acceptance of this planning packet (Option A in D0.2) authorizes only the following, and only after the GPT → Codex chain on D0 itself:

Treating this packet + the Owner decision matrix as the agreed map for a future consolidation — i.e., the agreed reading-rule for each of the 53 records.
Optionally, as a separate Owner decision (Option B in D0.2): authorizing a future, non-enacting "current-corpus drafting" workstream that would assemble a single consolidated reading/provenance layer (a pointer document, not copied law text) in newlaws/ — still DRAFT, still non-enacting, still Owner-gated, and still leaving laws/ untouched. D0 does not perform this; it only scopes it.
Optionally, as a separate Owner decision (Option D in D0.2): opening a scoped, read-only Phase-1 (Batch D) to verify the runtime blockers (RISK-BYPASS close / HOLD-1 / HOLD-2 / Đ39 runtime / Đ35 production-readiness) — an independent track that does not require consolidation.
Writing the 17 remaining KEEP+NOTE notes (future Batch-A), if the Owner directs it — read-only, non-enacting, like the existing 8.
Re-pointing LAW_READING_INDEX.md at the new AMEND/REWRITE drafts (a later Owner-gated index revision; §4.1).

None of the above is performed by D0. Each is a separate, later, Owner-gated step.

12. What remains forbidden (even after planning is accepted)

Accepting the planning packet does not unlock any of these. They remain forbidden until their own explicit Owner authorization:

Creating a current corpus by copying or moving old-law files into a "current" location (a consolidated reading layer is pointers + notes, never copied law text that could drift from laws/).
Editing, moving, or renaming anything under knowledge/dev/laws/; patching the Constitution.
Adopting / enacting any amendment, the Đ37 rewrite, or any note; declaring any current law changed; putting the Đ37 rewrite in force.
Writing technical design; running Phase-1 as if it were authorized by this packet; running any live DB/runtime query; implementing schema/table/registry/index.
Creating governance_registry; materializing the KG, cell_id/dot_role/canonical_fields, the Species Matrix, or BIRTH_STAMP/PROMOTE_STAMP.
Resolving any blocker (§10); changing the authority order (CONS-004); changing the v0.1 baseline; promoting v0.2-hardening (next section).

13. Bad readings this packet explicitly REJECTS

"Codex PASS means adoption." — FALSE. Codex PASS = usable for Owner/User decision. Adoption/enactment is an Owner act not yet taken.
"Drafts can now replace laws/." — FALSE. The drafts are non-enacting; laws/ is untouched and remains the source/provenance.
"A current corpus can be created automatically." — FALSE. No current corpus exists or is created; assembling one is a separate Owner-gated, non-enacting drafting step.
"Consolidation planning authorizes technical design." — FALSE. D0 authorizes no technical design, Phase-1, or implementation.
"Runtime blockers are resolved." — FALSE. RISK-BYPASS, HOLD-1/2, CONS-002/003, CELL, GOV-016/017, GOV-REUSE-001, Đ39 runtime-EMPTY, Đ35 prod-FAIL all remain open (§10).
"Source-recovery Đ0/0-B/0-G is resolved." — FALSE. The 5 Owner-gated source-recovery items remain open (§9); the Constitution is unpatched.
"v0.2-hardening replaces v0.1." — FALSE. v0.1-stable / FIX7 V3 remains the locked baseline (next section).
"Đ37 rewrite is now in force." — FALSE. It is a non-enacting DRAFT; enacted Đ37 v3.3 stays immutable.
"AMEND drafts are enacted amendments." — FALSE. They are DRAFT proposals pending Owner.
"KEEP+NOTE notes amend old laws." — FALSE. A note never amends its law; the old text stays AS-IS, a note is added under newlaws/.

14. Tool-Kiem-Thu safety lock (carried)

v0.1-stable / FIX7 V3 baseline remains LOCKED. It is the authority baseline; D0 does not touch it.
v0.2-hardening is a separate dev track. It is not authority.
v0.2 becomes authority only after regression + Owner/User promotion — neither performed nor authorized by D0.

This lock is independent of the consolidation question and is carried unchanged.

15. Folder policy (this packet)

Allowed output paths (used): knowledge/dev/laws-new/newlaws/consolidation/ (D0.1, D0.2) and knowledge/dev/laws-new/newlaws/reports/ (D0.3).
Forbidden output paths (not used, verified): knowledge/dev/laws/, knowledge/dev/laws-new/laws/, knowledge/dev/laws/newlaws/, newlaws/current/, laws-new/current/, laws-current/, current/, and laws-new/newlaws/ root.
laws/ untouched: no read-for-edit, no move, no copy. Old laws referenced by path only.

16. Readiness for Codex review

This packet is read-only, non-authorizing, and creates no current corpus. It maps all 53 records, all 5 AMEND drafts, the 1 REWRITE, the 8 written notes, the 17 not-yet-written notes, the source-recovery caveats, and the blockers that must stay open — and defers every build/adopt/resolve action to a later, explicit Owner decision (D0.2).

Ready for Codex review: YES. Recommended chain: GPT reviews D0 → Codex reviews D0 → Owner chooses one option in D0.2. Codex PASS ≠ Owner authorization.