LAW READING INDEX — Which Law Source to Read After Law Merge (2026-06-17, rev2 D1 pointer re-point, read-only, non-authorizing)
LAW READING INDEX — Which Law Source to Read After Law Merge
Status: Working navigation index. READ-ONLY · NON-AUTHORIZING. Created: 2026-06-17 · Law Revision Workstream A · rev1. Re-pointed: 2026-06-17 · Law Revision Workstream D1 · rev2 (pointer/navigation update only — see the D1 banner below). Basis:
law-merge-survey-packet.md(rev1) +law-merge-catalog-2026-06-16.md(rev1, 53 records) +law-merge-execution-report-2026-06-16.md(rev2) +law-merge-administrative-phase-gate-2026-06-17.md(rev1); re-pointed againstconsolidation/law-revision-consolidation-planning-packet-2026-06-17.md(D0, rev1) +consolidation/owner-decision-matrix-law-revision-2026-06-17.md(D0.2, rev1) +reports/workstream-e0-new-law-consistency-conflict-audit-2026-06-17.md(E0, rev1, PASS_WITH_MEDIUM_FINDINGS); all underknowledge/dev/laws-new/newlaws/. Codex status of the basis: Law Merge Survey bundle PASSED Codex review (a folder-policy HOLD was raised, then cleared by removing an out-of-workspace fileknowledge/dev/laws-new/laws/README.md; recheck = PASS). Codex/Council PASS ≠ Owner authorization for technical design.
⚑ D1 UPDATE — NON-ENACTING POINTER UPDATE
This index has been re-pointed after B1 / B2 / C / D0 / E0. 5 AMEND drafts and 1 REWRITE draft now exist. They are DRAFT / NON-ENACTING / PENDING_OWNER. This index still does not enact, consolidate, or create a current corpus.
What D1 changed in this file (pointer/navigation only):
- Re-pointed the 6 AMEND/REWRITE records at the now-existing draft files (
newlaws/amendments/,newlaws/rewrites/).- Replaced the stale "no amendment/rewrite exists yet — read old as background only" wording with "draft exists — read old + draft as DRAFT / PENDING_OWNER (not enacted)."
- Made the D0 reading-rule labels primary (
READ_OLD_AS_IS/READ_OLD_WITH_NOTE/READ_AMENDMENT_DRAFT_PENDING_OWNER/READ_REWRITE_DRAFT_PENDING_OWNER/DEFER_DO_NOT_USE); the older Workstream-A labels are retained only as historical aliases.- Distinguished AMEND_ENACTED (Đ22, Đ33) from REVISE_DRAFT_DIRECTION (Đ36, L4, Đ38 v3.0).
- Separated CONS-004 / CONS-005 (decided at F0) from the open-blocker list.
- Added a forward note for future glossary work (E0-L4).
This addresses E0 findings E0-M1 (index stale for the 6 AMEND/REWRITE records), E0-L1 (CONS-004/005 lumped with open blockers), E0-L2 (reading-rule label divergence) and E0-L3 (AMEND used for non-enacted draft targets). E0-L4 (glossary/stamp/gate terminology) is carried as future work, not done here.
D1 is the documentary track of D0 Option B. It is non-enacting. A companion, more detailed pointer/provenance layer lives at
consolidation/current-understanding-pointer-layer-2026-06-17.md. Default disposition until the Owner acts: HOLD.
0. What this index is for
This file tells a human or an agent which law source to read when they need the current working understanding of a law after the Law Merge survey. It does not change any law. It is a map, not a decree.
It classifies every one of the 53 Law Merge catalog records into exactly one of five reading rules. The labels below are the D0 reading-rule labels (made primary by D1); the right-most column records the older Workstream-A label as a historical alias only.
| Reading rule (D0 — primary) | Means | Maps from catalog disposition | Historical WS-A alias |
|---|---|---|---|
| READ_OLD_AS_IS | Read the old law in knowledge/dev/laws/ (or ssot/) as-is; it is compatible with the F0→F5/FX model. |
KEEP | (unchanged) |
| READ_OLD_WITH_NOTE | Read the old law together with the compatibility note (under newlaws/notes/, Owner-gated; 8 written, 17 future). 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 §4 until the note exists.) |
KEEP+NOTE | READ_OLD_WITH_COMPATIBILITY_NOTE |
| READ_AMENDMENT_DRAFT_PENDING_OWNER | An AMEND draft now exists under newlaws/amendments/. Read the old law + the amendment draft as DRAFT / PENDING_OWNER. The draft is not enacted; the conflicting clauses of the old law are not yet final for new design. |
AMEND | READ_NEW_AMENDED_VERSION_PENDING |
| READ_REWRITE_DRAFT_PENDING_OWNER | A REWRITE draft now exists under newlaws/rewrites/. Read the old law as source/provenance + the rewrite draft as DRAFT / PENDING_OWNER (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 | READ_NEW_REWRITE_VERSION_PENDING |
| DEFER_DO_NOT_USE | Superseded, implementation-specific, obsolete, or too deep for this phase. Do not use as a source for new design now. Audit/history only. | DEFER | DEFER_DO_NOT_USE_FOR_NEW_DESIGN |
Catalog totals (verified, sum = 53): KEEP 6 · KEEP+NOTE 25 · AMEND 5 · REWRITE 1 · DEFER 16.
| Reading rule (D0) | Count |
|---|---|
| READ_OLD_AS_IS | 6 |
| READ_OLD_WITH_NOTE | 25 |
| READ_AMENDMENT_DRAFT_PENDING_OWNER | 5 |
| READ_REWRITE_DRAFT_PENDING_OWNER | 1 |
| DEFER_DO_NOT_USE | 16 |
| TOTAL | 53 |
1. Two-corpus rule (read this before anything else)
knowledge/dev/laws/(andknowledge/dev/ssot/,knowledge/dev/architecture/) = SOURCE / PROVENANCE corpus. Mostly read-only. These hold the enacted/old law text. Workstreams A / B0 / B1 / B2 / C / D0 / D1 did not edit, move, rename, or delete anything here.knowledge/dev/laws-new/newlaws/= NOTES / AMENDMENTS / REWRITES / current working-law WORKSPACE. All reading-index entries, compatibility notes, amendment drafts, rewrite drafts, and the D0/D1 pointer/consolidation materials live here.- No old law is replaced unless this index explicitly says so after review.
newlaws/does not automatically replacelaws/. A KEEP+NOTE note does not supersede the old law; an AMEND/REWRITE draft is a pending, non-enacting proposal, not an enacted change. The presence of a draft (re-pointed by D1) does not make it law. - Supremacy unchanged: the Constitution (
laws/constitution.mdv4.6.3) remains the supreme text ("Văn bản tối cao"). F0→F5/FX is a method under it, not a competing authority. Authority order is unchanged by D1. It was recorded/decided at F0 (CONS-004, working precedence, not enacted): supreme Constitution > enacted laws (Đ32/Đ35/Đ37/Đ38/Đ39…) > laws-new KB drafts (practical authority for laws-new docs only); VPS = SSOT code/runtime; PG/Directus = truth; cross-class = Owner gate. CONS-004 is a decided item, not an open blocker (see §7).
2. Navigation caveat — foundation laws Đ0 / 0-B / 0-G are NOT in laws/
This is a real source-location hazard discovered during Workstream A and confirmed by the B0 source-recovery report. D1 does not fix it (that is an Owner-gated source-recovery pass); it only carries it forward.
- The Constitution's MỤC LỤC lists
law-00-entity.md(Đ0),law-00b-composition.md(Đ0-B),law-00g-birth.md(Đ0-G). These files do NOT exist inknowledge/dev/laws/(onlylaw-00h-5layer-sync.mdexists there). - The operative texts live in
knowledge/dev/architecture/: Đ0 =architecture/information-atom-law.md(v2.0); Đ0-B =architecture/composition-level-law.md(file-title v3.0 / body-header v3.1 — a tracked drift); Đ0-G =architecture/birth-registry-law.md(v1.0).knowledge/dev/laws/existing-law-references.mddesignatesarchitecture/as the "tham khảo chi tiết" (detailed reference) home of foundational laws — working source under the Constitution, NOT supreme. - The Constitution itself does not embed the full Đ0/0-B/0-G article text — it only references them.
- Consequence: when an index entry below points to Đ0 / 0-B / 0-G or "the embedded birth law," read the
architecture/file, not a non-existentlaws/law-00*.md. A future Owner-gated source-recovery pass should reconcile the Constitution's broken file references and confirm whether thearchitecture/versions are the authoritative current texts. Seereports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.mdandreports/birth-embedded-dieu0-dieu0b-dieu0g-check-2026-06-17.md. D1 does not resolve any of the 5 Owner-gated source-recovery items.
3. The 53-record reading map
Disposition labels and record order are taken verbatim from law-merge-catalog-2026-06-16.md. The "Note (this batch)" column points to the compatibility notes created in Workstream A (8 of the 25 KEEP+NOTE records). The remaining KEEP+NOTE notes are future Batch-A work. The AMEND/REWRITE records (§3.3, §3.4) were re-pointed by D1 at the now-existing draft files.
3.1 READ_OLD_AS_IS — KEEP (6)
| # | Target law | Old source path | Reading rule (D0) |
|---|---|---|---|
| 32 | Điều 20 — Design Before Execution v1.2 | laws/dieu20-thiet-ke-truoc-trien-khai.md |
READ_OLD_AS_IS |
| 33 | Điều 30 — Regression Protection v1.2 | laws/dieu30-regression-protection-law.md |
READ_OLD_AS_IS |
| 34 | Operating Rules v7.58 (Concise) | ssot/operating-rules.md |
READ_OLD_AS_IS |
| 35 | Điều 15-16 — State Machine + Checkpoint | laws/law-15-16-state-checkpoint.md |
READ_OLD_AS_IS |
| 36 | Điều 6 — Sync Law | laws/law-06-sync.md |
READ_OLD_AS_IS |
| 37 | Điều 7 — Assembly First (Luật Tận dụng) | laws/law-07-assembly-first.md |
READ_OLD_AS_IS |
3.2 READ_OLD_WITH_NOTE — KEEP+NOTE (25)
| # | Target law | Old source path | Reading rule (D0) | Note (this batch) |
|---|---|---|---|---|
| 7 | Điều 0-H — Đồng bộ 5 Tầng | laws/law-00h-5layer-sync.md |
READ_OLD_WITH_NOTE | future |
| 8 | Điều 1 — Foundation Principles (15 NT) | laws/law-01-foundation-principles.md |
READ_OLD_WITH_NOTE | notes/dieu1-foundation-principles-compatibility-note.md |
| 9 | Điều 29 — Collection Classification v2.0 | laws/dieu29-classification-law.md |
READ_OLD_WITH_NOTE | future |
| 10 | Điều 31 — System Integrity v1.2 | laws/dieu31-system-integrity-law.md |
READ_OLD_WITH_NOTE | future |
| 11 | Điều 32 — Approval (APR) v1.1 | laws/dieu32-approval-law.md |
READ_OLD_WITH_NOTE | notes/dieu32-approval-owner-gate-compatibility-note.md |
| 12 | Điều 35 — DOT Governance v5.2 FINAL | laws/dieu35-dot-governance-law.md |
READ_OLD_WITH_NOTE | notes/dieu35-dot-governance-compatibility-note.md |
| 13 | Điều 4 — Birth Process (Luật Sinh sản) | laws/law-04-birth-process.md |
READ_OLD_WITH_NOTE | notes/dieu4-birth-process-compatibility-note.md |
| 14 | Hiến pháp (Constitution) v4.6.3 | laws/constitution.md |
READ_OLD_WITH_NOTE | notes/constitution-compatibility-note.md |
| 15 | Terminology Glossary v2.1 | laws/terminology-glossary.md |
READ_OLD_WITH_NOTE | notes/terminology-compatibility-note.md |
| 16 | Điều 38 — Phụ lục 01: Text as Code Objectives | laws/dieu38-appendix-01-objectives.md |
READ_OLD_WITH_NOTE | notes/dieu38-text-as-code-appendix01-compatibility-note.md |
| 17 | Điều 10-13 — Operations | laws/law-10-13-operations.md |
READ_OLD_WITH_NOTE | future |
| 18 | Điều 14 — Anti-Duplicate (3 cấp) | laws/law-14-no-duplicate.md |
READ_OLD_WITH_NOTE | future |
| 19 | Điều 19 — Orphan Scanner (Side B) | laws/law-19-orphan-scanner.md |
READ_OLD_WITH_NOTE | future |
| 20 | Điều 2 — Registry (23 prefix) | laws/law-02-registry.md |
READ_OLD_WITH_NOTE | future |
| 21 | Điều 26 — Pivot v4.0 | laws/dieu26-pivot-law.md |
READ_OLD_WITH_NOTE | future |
| 22 | Điều 3 — Metadata | laws/law-03-metadata.md |
READ_OLD_WITH_NOTE | future |
| 23 | Điều 39 — Knowledge Graph v2.3 | laws/dieu39-knowledge-graph-law.md |
READ_OLD_WITH_NOTE | notes/dieu39-knowledge-graph-compatibility-note.md |
| 24 | Điều 41 — VPS Code Operation v1.1 | laws/dieu41-luat-van-hanh-ma-vps-v1.1.md |
READ_OLD_WITH_NOTE | future |
| 25 | Điều 5 — Kiến trúc 5 Tầng | laws/law-05-five-tiers.md |
READ_OLD_WITH_NOTE | future |
| 26 | Điều 9 — Schema Governance (SCR) | laws/law-09-schema-governance.md |
READ_OLD_WITH_NOTE | future |
| 27 | LSL-01 — Information Unit First v0.3 | laws/dieu38-trien-khai/LSL-01-information-unit-first.md |
READ_OLD_WITH_NOTE | future |
| 28 | Điều 24 — Label Law v1.3 (frozen) | laws/label-law.md |
READ_OLD_WITH_NOTE | future |
| 29 | Điều 43 — System Context v1.2 FINAL | laws/dieu43-system-context-law.md |
READ_OLD_WITH_NOTE | future |
| 30 | Điều 17-18 — Multi-domain + i18n + Change | laws/law-17-18-domain-change.md |
READ_OLD_WITH_NOTE | future |
| 31 | Điều 8 — Dependency Law | laws/law-08-dependency.md |
READ_OLD_WITH_NOTE | future |
Note on the 8 vs 25: Workstream A wrote the 8 highest-priority KEEP+NOTE notes (the ones that gate technical-design reasoning: Constitution, Đ39, Đ35, Đ32, Đ4, Đ1, Terminology, Đ38 Appendix-01). The other 17 KEEP+NOTE notes are future Batch-A work and are listed "future" above. "future" means the note has not been written yet; until it is, read the old law as-is and apply the global bad-reading rejections in §4. D1 did not write any of the 17 future notes.
3.3 READ_AMENDMENT_DRAFT_PENDING_OWNER — AMEND (5)
Re-pointed by D1. A DRAFT amendment now exists under newlaws/amendments/ for each of these 5 records. Read the old law (provenance) together with its amendment draft, as DRAFT / PENDING_OWNER. The draft is not enacted; laws/… is untouched.
| # | Target law | Old source path (provenance, untouched) | Reading rule (D0) | Amendment draft — DRAFT / PENDING_OWNER (newlaws/amendments/…) |
Amend type |
|---|---|---|---|---|---|
| 2 | Điều 22 — Self-Healing + Self-Improvement v1.2 | laws/law-22-self-healing.md |
READ_AMENDMENT_DRAFT_PENDING_OWNER | dieu22-self-healing-amendment-draft.md |
AMEND_ENACTED |
| 3 | Điều 33 — PostgreSQL v2.1 | laws/dieu33-postgresql-law.md |
READ_AMENDMENT_DRAFT_PENDING_OWNER | dieu33-postgresql-law-amendment-draft.md |
AMEND_ENACTED |
| 4 | Điều 36 — Collection Protocol v5.0 (DRAFT) | laws/dieu36-collection-protocol-law.md |
READ_AMENDMENT_DRAFT_PENDING_OWNER | dieu36-collection-protocol-amendment-draft.md |
REVISE_DRAFT_DIRECTION |
| 5 | L4 — Birth Gate Extension (mở rộng Điều 0-G) | laws/dieu38-trien-khai/L4-birth-gate-extension.md |
READ_AMENDMENT_DRAFT_PENDING_OWNER | l4-birth-gate-extension-amendment-draft.md |
REVISE_DRAFT_DIRECTION |
| 6 | Điều 38 — SQL Hoá Văn Bản v3.0 (DRAFT) | laws/dieu38-normative-document-law.md |
READ_AMENDMENT_DRAFT_PENDING_OWNER | dieu38-normative-document-law-v3-amendment-draft.md |
REVISE_DRAFT_DIRECTION |
Amend type — precision note (D1, addresses E0-L3):
- Đ22 and Đ33 are AMEND_ENACTED targets — their old target texts are enacted laws (Đ22 v1.2 BAN HÀNH; Đ33 v2.1 BAN HÀNH). The draft proposes a future amendment to enacted law.
- Đ36, L4, and Đ38 v3.0 are REVISE_DRAFT_DIRECTION targets — their old target texts are themselves draft / non-enacted (Đ36 v5.0 DRAFT, with v4.0 the last enacted; L4 DỰ THẢO; Đ38 v3.0 DRAFT). "Amending" these is really revising a draft's direction, not amending enacted law.
- All five remain DRAFT / PENDING_OWNER and none is enacted. The distinction is descriptive; it changes neither the reading rule nor the non-enacting status.
Why each is AMEND (one line, carried from the catalog):
- #2 Đ22 — only law with genuine auto-fix; split detect/list (keep) from auto-fix (re-scope to Owner-gated proposal-only).
- #3 Đ33 — keep PG-foundation / 4-DB-3-layer / canonical-field discipline; amend auto-fix + schema-auto-change clauses (auto-
ALTER→ propose).- #4 Đ36 — keep the 7 goals; block cell_id / Species-Matrix / cell-placement materialization + scanner auto-reclassify while CONS-003 + CELL open.
- #5 L4 — birth issues TEMP_ID only at INSERT; relocate completeness / reuse / approval from INSERT to the promote checker (canonical at promote / F4).
- #6 Đ38 v3.0 — keep the 3 MT goals; constrain "DOT 100%" / auto-output-regen to scanner + checker + render-at-promote.
3.4 READ_REWRITE_DRAFT_PENDING_OWNER — REWRITE (1)
Re-pointed by D1. A DRAFT rewrite now exists under newlaws/rewrites/. Read old Đ37 as source/provenance + the rewrite draft as DRAFT / PENDING_OWNER. The rewrite is not enacted; enacted Đ37 v3.3 stays immutable (NT7).
| # | Target law | Old source path (provenance, untouched — immutable v3.3) | Reading rule (D0) | Rewrite draft — DRAFT / PENDING_OWNER (newlaws/rewrites/…) |
|---|---|---|---|---|
| 1 | Điều 37 — Governance Organization v3.3 | laws/dieu37-governance-organization-law.md |
READ_REWRITE_DRAFT_PENDING_OWNER | dieu37-governance-organization-law-rewrite-draft.md |
Why rewrite (not amend): the conflict is structural / authority-level, not a clause fix — central
governance_registry+ Council auto-DROP vote + auto-cron DOTs conflict with FX One-Roof-over-existing-ledgers + Owner-gate. Goals (G1–G10) preserved; 7 mechanisms (R1–R7) retired; replaced with One-Roof + 4 primitives + Owner/Đ32 gate. "Retire" = the future law no longer mandates the mechanism; no live table/DOT/trigger/row is dropped, disabled, or altered. The enacted v3.3 stays immutable; the rewrite is a future law, drafted now as a non-enacting proposal.
3.5 DEFER_DO_NOT_USE — DEFER (16)
| # | Target / bucket | Old source path | Reading rule (D0) |
|---|---|---|---|
| 38 | Constitution v4.2.0 Amendment Draft (+NT10 +Đ28 v2.0) | laws/constitution-v4.2.0-amendment-draft.md |
DEFER_DO_NOT_USE |
| 39 | D28 Display Technology implementation bucket (~27 files) | laws/dieu28-trien-khai/ |
DEFER_DO_NOT_USE |
| 40 | D38 Text-as-Code implementation bucket (~150 files; excl. LSL-01, L4) | laws/dieu38-trien-khai/ |
DEFER_DO_NOT_USE |
| 41 | D41 Revision Rulings bucket (2 files) | laws/dieu41-revision-rulings/ |
DEFER_DO_NOT_USE |
| 42 | D43 Migrations bucket (23 files) | laws/dieu43-migrations/ |
DEFER_DO_NOT_USE |
| 43 | D44 UOSL implementation bucket (~350+ files; excl. README) | laws/dieu44-trien-khai/ |
DEFER_DO_NOT_USE |
| 44 | DEFER bucket — superseded Đ43 drafts/backup + Đ44 UOSL GPT review | laws/dieu43-system-context-law-draft.md + others |
DEFER_DO_NOT_USE |
| 45 | Điều 28 — Display Technology v2.0 | laws/dieu28-display-technology-law.md |
DEFER_DO_NOT_USE |
| 46 | Điều 3 — Appendix: Description Templates | laws/dieu3-phu-luc-description-templates.md |
DEFER_DO_NOT_USE |
| 47 | Điều 34 — Workflow v1.0 (unenacted draft) | laws/dieu34-workflow-law.md |
DEFER_DO_NOT_USE |
| 48 | Điều 35 — DOT Governance v5.0 FINAL (BACKUP) | laws/dieu35-dot-governance-law-v5-0-backup.md |
DEFER_DO_NOT_USE |
| 49 | Điều 35 — DOT Governance v5.1 DRAFT | laws/dieu35-dot-governance-law-v5-1-draft.md |
DEFER_DO_NOT_USE |
| 50 | Điều 41 — Appendix: Deployment Plan (living doc) | laws/dieu41-phu-luc-ke-hoach-trien-khai.md |
DEFER_DO_NOT_USE |
| 51 | Điều 44 — UOSL implementation README | laws/dieu44-trien-khai/README.md |
DEFER_DO_NOT_USE |
| 52 | Superseded D41 drafts + Council Review Requests bucket (7 files) | laws/dieu41-luat-van-hanh-ma-vps-draft-v0.{2..5.1} |
DEFER_DO_NOT_USE |
| 53 | Điều 44 — Universal Object Schema Law (UOSL) v0.1.2 (controlled DRAFT) | laws/dieu44-universal-object-schema-law.md |
DEFER_DO_NOT_USE |
Path note: several old source paths above are as the catalog records them; a few exact filenames (e.g. the consolidated
law-NN-*.mdfoundation family) should be confirmed bylist_documentsbefore citation in a future technical-design pass. Where a path differs from disk, the disk path wins; this is a navigation aid, not a source of truth. D1 does not make any DEFER record an active source for new design.
4. Bad readings this index explicitly REJECTS
A category label is not a license. The following readings are wrong and must not be acted on.
4.1 Standing bad readings (carried; updated for the now-existing drafts)
- "Codex/GPT/Council PASS authorizes technical design." FALSE. PASS = the artifact is review-complete. Only the Owner opens a phase. Engineering PASS ≠ Authority PASS.
- "KEEP+NOTE means the note is enacted law." FALSE. A compatibility note is interpretation guidance written in
newlaws/; it does not enact, amend, or supersede the old law. - "AMEND means amend the law now." FALSE. A DRAFT amendment now exists under
newlaws/amendments/(written in Workstreams B1/B2; re-pointed by D1), but it is non-enacting / PENDING_OWNER. Reading the draft as a pending proposal is required; treating it as an enacted amendment is not. No law is amended until a separate, explicit Owner enactment decision. - "REWRITE means rewrite the law now." FALSE. A DRAFT rewrite now exists under
newlaws/rewrites/(Điều 37, Workstream C; re-pointed by D1), but it is non-enacting / PENDING_OWNER. Enacted Điều 37 v3.3 stays immutable; the rewrite is not in force. - "Điều 39 is live because it is enacted (BAN HÀNH)." FALSE. Đ39 is enacted but runtime-EMPTY (0 DOT executions, 0 KG events; owner unregistered). Enacted ≠ implemented ≠ live.
- "36 DOT-KG registered means executed / live / production-ready." FALSE. 36/36 registered (18/18 pairs, 0 NULL) but
last_executedNULL, 0 runs. Registered ≠ executed ≠ live ≠ production-ready. - "Scanner can auto-fix because Điều 22 says self-healing." FALSE. In the new model the scanner is list-only (no auto-fix, no gate-block). Điều 22's genuine auto-fix is exactly why Đ22 is AMEND.
- "Birth registry INSERT means canonical birth now." FALSE. Đ0-G inserts an uncertified birth record at INSERT (
certified=false); certification/canonical status is a later, separately-gated event. Canonical birth = output at promote (F4). - "Điều 37
governance_registryshould be reused directly." FALSE. Đ37's central registry conflicts with FX One-Roof (a conceptual roof over existing ledgers, not a central system). That conflict is why Đ37 is REWRITE. - "Điều 35 is production-ready because it is enacted v5.2." FALSE. Live Đ35 substrate reads "PRODUCTION READINESS FAIL" with a confirmed authority bypass (
fn_auto_approve_add, 160 unvoted applies = RISK-BYPASS). Enacted ≠ production-certified. - "
newlaws/replaceslaws/automatically." FALSE.laws/stays the source corpus; replacement happens only when this index explicitly says so after review. - "v0.2-hardening replaces the v0.1 baseline automatically." FALSE. See the Safety Lock in §5.
4.2 D1-specific bad readings (added by the D1 re-point — all FALSE)
- "D1 creates a current corpus." FALSE. D1 creates a pointer/navigation layer only; no current corpus, no
current/folder, no copied law text. - "The D1 pointer layer / re-pointed index is current law." FALSE. It is a non-enacting reading map;
laws/remains the source of truth. - "D1 adopts the AMEND drafts." FALSE. D1 points to them as DRAFT / PENDING_OWNER; it adopts/enacts nothing.
- "D1 adopts the Đ37 rewrite." FALSE. Same — the rewrite stays a non-enacting DRAFT; enacted v3.3 is immutable.
- "D1 replaces
laws/." FALSE.laws/,ssot/,architecture/are untouched. - "D1 authorizes technical design." FALSE. No technical design is authorized by D1.
- "D1 authorizes Phase-1." FALSE. No Phase-1 / no live DB/runtime query is authorized by D1.
- "D1 resolves runtime blockers." FALSE. RISK-BYPASS, HOLD-1/2, CONS-002/003, CELL, GOV-016/017, GOV-REUSE-001, Đ39 runtime-EMPTY, Đ35 prod-FAIL all stay open.
- "D1 fixes the source-recovery Đ0/0-B/0-G items." FALSE. The 5 Owner-gated source-recovery items remain open; the Constitution is unpatched.
- "D1 makes a DEFER doc an active design source." FALSE. DEFER records stay
DEFER_DO_NOT_USE. - "D1 changes the authority order." FALSE. CONS-004 authority order is unchanged.
- "D1 promotes v0.2-hardening." FALSE. v0.1-stable / FIX7 V3 stays the locked baseline (§5).
5. Registries-Pivot / Tool-Kiem-Thu Safety Lock
This lock travels with this index and the Workstream A / D0 / D1 materials. It is recorded, not executed. D1 does not touch it.
- The current tool/packet built by T1 = v0.1-stable / FIX7 V3 baseline.
- It remains usable for FIX7 Recheck-9 / current Codex packet verification.
- It must not be overwritten.
- It is the regression baseline / comparison fixture.
- Tool-Kiem-Thu v0.2-hardening is a separate development track.
- v0.2-hardening must live on a separate dev surface.
- v0.2-hardening inherits the lessons from V3: black-box oracle; fail-open regression; manifest-laundering prevention; adversarial invalid-input testing.
- v0.2-hardening is not authority for FIX7 until it passes regression and is promoted by Owner/User.
Do not build v0.2-hardening. Do not modify the v0.1 baseline. This workstream only records the safety lock.
6. Where the working-law materials live
- Reading index:
knowledge/dev/laws-new/newlaws/LAW_READING_INDEX.md(this file; rev2 D1 re-point). - D1 pointer/provenance layer:
knowledge/dev/laws-new/newlaws/consolidation/current-understanding-pointer-layer-2026-06-17.md(the companion navigation layer; pointers, not copied law text). - Compatibility notes:
knowledge/dev/laws-new/newlaws/notes/(8 created in Workstream A; 17 more in future Batch A). - Amendment drafts (5, DRAFT/PENDING_OWNER):
knowledge/dev/laws-new/newlaws/amendments/. - Rewrite draft (1, DRAFT/PENDING_OWNER):
knowledge/dev/laws-new/newlaws/rewrites/. - Consolidation planning (D0):
knowledge/dev/laws-new/newlaws/consolidation/law-revision-consolidation-planning-packet-2026-06-17.md+…/owner-decision-matrix-law-revision-2026-06-17.md. - Source-recovery:
knowledge/dev/laws-new/newlaws/reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md. - Consistency/conflict audit (E0):
knowledge/dev/laws-new/newlaws/reports/workstream-e0-new-law-consistency-conflict-audit-2026-06-17.md. - Execution reports:
knowledge/dev/laws-new/newlaws/reports/(Workstream A / B0+B1 / B2 / C / D0 / D1).
7. Non-authorization (binding on every reader of this index)
This index does NOT: enact, amend, rewrite, re-enact, supersede, move, rename, or delete any law; authorize technical design; authorize Phase-1 or any live DB/runtime query; authorize implementation / schema / table / registry / index creation; resolve any held blocker; change the authority order; or change the v0.1-stable / FIX7 V3 baseline.
Open blockers (NOT resolved by this index or by D1): CONS-002, CONS-003, CELL-003/004/007, HOLD-1, HOLD-2, RISK-BYPASS, RISK-GC/CAP, STG-, DOT-CAP-, GOV-016/017, GOV-REUSE-001, Đ39 runtime-EMPTY, Đ35 production-readiness FAIL, and the 5 Owner-gated source-recovery items (Đ0/0-B/0-G). All remain open.
Decided at F0 (NOT open blockers, NOT reopened, NOT changed by D1): CONS-004 (authority order) and CONS-005 (freeze-candidate baseline) were decided at F0. They are recorded here as decided for clarity (addresses E0-L1); the authority order is unchanged.
Future glossary work (carried, NOT done by D1 — E0-L4): the Owner / Mức 3 / Điều 32 relationship (an authority / a risk level / an approval law — three distinct things, currently used interchangeably) and the stamp family vocabulary (BIRTH_STAMP, PROMOTE_STAMP, OWNER_STAMP, GOV_STAMP, completeness/TEMP stamp, CELL_STAMP/IO_STAMP) should be normalized in a future Owner-gated glossary addition (already scoped by the terminology compatibility note). This is not part of D1.
Default disposition until the Owner acts: HOLD. Next: GPT review → Codex review → Owner decides among D0 Options A (accept the map) / B (this non-enacting pointer layer — the D1 track) / C (fix a named artifact) / D (scoped read-only Phase-1 blocker verification). Codex/Council/GPT PASS ≠ Owner authorization.
LAW READING INDEX rev2 | 2026-06-17 | 53/53 records mapped · 6 AMEND/REWRITE records re-pointed at drafts (D1) | read-only · non-authorizing · non-enacting | Codex PASS ≠ Owner authorization