KB-185E

Current-Understanding Pointer Layer — Law Revision Workstream D1 (2026-06-17, non-enacting, pointer-only, NOT a current corpus, read-only, non-authorizing)

35 min read Revision 1
laws-newnewlawslaw-revisionworkstream-d1pointer-layercurrent-understandingnavigationprovenance53-record-matrixkeep-amend-rewrite-deferamend-enactedrevise-draft-directionnon-enactingno-current-corpusread-onlynon-authorizingowner-gatedtool-kiem-thu-lock2026-06-17

Current-Understanding Pointer Layer — Law Revision Workstream D1

THIS IS NOT A CURRENT CORPUS.

Status: Reader-facing navigation / pointer / provenance layer. NON-ENACTING · POINTER-ONLY · READ-ONLY · NON-AUTHORIZING. Created: 2026-06-17 · Law Revision Workstream D1 · rev1. Companion: the re-pointed knowledge/dev/laws-new/newlaws/LAW_READING_INDEX.md (rev2, D1). This document is the more-detailed pointer table behind that index. Basis (all under knowledge/dev/laws-new/newlaws/, read first-hand for this layer): consolidation/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/law-revision-workstream-d0-consolidation-planning-execution-report-2026-06-17.md (D0.3, rev1) · reports/workstream-e0-new-law-consistency-conflict-audit-2026-06-17.md (E0, rev1, PASS_WITH_MEDIUM_FINDINGS) · law-merge-catalog-2026-06-16.md (rev1, 53 records) · the 5 AMEND drafts under amendments/ · the 1 REWRITE draft under rewrites/ · the 8 compatibility notes under notes/ · reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md (B0). Standing rule: Codex/GPT/Council PASS ≠ Owner authorization. Engineering PASS ≠ Authority PASS. Default disposition: HOLD.


0. Non-enacting / pointer-only banner

  • This document does not copy law text. Every cell below is a pointer (a path + a reading rule + a status), never the body of a law.
  • This document does not replace laws/. knowledge/dev/laws/ (and ssot/, architecture/) stay the source / provenance corpus, untouched.
  • This document does not enact drafts. The 5 AMEND drafts and the 1 REWRITE draft it points to are DRAFT / NON-ENACTING / PENDING_OWNER.
  • This document does not create current law. No law is changed, adopted, consolidated, or put into force.
  • This document is only a navigation / pointer layer. It tells a reader which source to read for each of the 53 Law-Merge records — nothing more.
  • THIS IS NOT A CURRENT CORPUS. A current corpus would copy or move law files into a "current" location; this layer does neither. It is pointers + notes, never copied law text that could drift from laws/.

D1 = the documentary track of D0 Option B, executed non-enactingly. It re-points the reading map at the now-existing drafts and assembles this single reader-facing pointer table. It changes no law, builds no current corpus, resolves no blocker.


1. Purpose

After Workstreams A → B0 → B1 → B2 → C produced the law-revision materials (a reading index, 8 compatibility notes, 5 amendment drafts, 1 rewrite draft, a source-recovery map), D0 planned how they could be consolidated and asked the Owner to choose (Options A/B/C/D), and E0 audited the whole new-law corpus for consistency (PASS_WITH_MEDIUM_FINDINGS).

This pointer layer is the single reader-facing answer to "which law source do I read right now, for each law, and what is its status?" — assembled from the D0 53-record matrix and re-pointed at the drafts that now exist. It exists so a reader does not have to reconstruct the map from eight separate artifacts, and so the named entry point (LAW_READING_INDEX.md) is no longer stale for the 6 AMEND/REWRITE records (E0-M1).

It is deliberately pointers, not law text (E0-I1): it keeps "canonical birth = output at promote (F4)" distinct from "the current reading" (this non-enacting pointer layer). Reading this layer tells you where to look; it never tells you a draft is in force.

E0 findings this layer (with the index re-point) addresses: 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), E0-L3 (AMEND used for non-enacted draft targets). E0-L4 (glossary/stamp/gate terminology) is carried as future work (§12), not done here.


2. The 53-record pointer table

Records are in catalog order (action-first: REWRITE → AMEND → KEEP+NOTE → KEEP → DEFER). Disposition is exact from the Law-Merge catalog. D1 reading rule uses the D0 labels (now primary). Pointer target is the newlaws/ artifact to read alongside the old law, if any. Status records whether that artifact is a draft pending Owner, a written note, a future note, or none. laws/… paths are provenance only — untouched, never copied here.

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

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

Disposition Count D1 reading rule
KEEP 6 READ_OLD_AS_IS
KEEP+NOTE 25 READ_OLD_WITH_NOTE (8 notes written, 17 future)
AMEND 5 READ_AMENDMENT_DRAFT_PENDING_OWNER
REWRITE 1 READ_REWRITE_DRAFT_PENDING_OWNER
DEFER 16 DEFER_DO_NOT_USE
TOTAL 53

3. Six draft pointers (the 5 AMEND + 1 REWRITE — DRAFT / PENDING_OWNER)

Each of the 6 conflict records now has a non-enacting DRAFT in newlaws/. Read the old law (provenance) together with its draft, as DRAFT / PENDING_OWNER. None is enacted. laws/… is untouched.

3.1 The Đ37 rewrite (1)

Record Old law (provenance, immutable) Rewrite draft (pointer, DRAFT/PENDING_OWNER) One-line
#1 Đ37 laws/dieu37-governance-organization-law.mdv3.3 BAN HÀNH (enacted/immutable per NT7) rewrites/dieu37-governance-organization-law-rewrite-draft.md Preserve G1–G10 governance goals; retire 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. "Retire" = the future law stops mandating the mechanism; no live table/DOT/trigger/row is dropped, disabled, or altered.

3.2 The 5 amendment drafts (records 2–6)

Record Old law (provenance) Amendment draft (pointer, DRAFT/PENDING_OWNER) PRESERVE / REFRAME (one-line)
#2 Đ22 laws/law-22-self-healing.md amendments/dieu22-self-healing-amendment-draft.md Preserve detect→list→propose→learn; reframe genuine auto-fix → proposal-only (canonical safe path = Đ35 §6.2 fix_repair_dot).
#3 Đ33 laws/dieu33-postgresql-law.md amendments/dieu33-postgresql-law-amendment-draft.md Preserve PG-foundation / 4-DB / 3-layer / canonical-field discipline; block auto-ALTER/schema-auto-change → design chain; defer canonical_fields/dot_role/cell_id materialization while CONS-003 + CELL open.
#4 Đ36 laws/dieu36-collection-protocol-law.md amendments/dieu36-collection-protocol-amendment-draft.md Preserve the 7 goals (MT1–MT7); block Species-Matrix + cell-placement materialization + scanner auto-reclassify while CONS-003 + CELL open; reverse-trace = listed observation, not canonical proof.
#5 L4 laws/dieu38-trien-khai/L4-birth-gate-extension.md amendments/l4-birth-gate-extension-amendment-draft.md Preserve birth-gate goal (completeness not correctness); INSERT = identity-root + TEMP/uncertified; relocate completeness-final + reuse + approval + BIRTH_STAMP/PROMOTE_STAMP to the promote checker (canonical at promote / F4, never at INSERT).
#6 Đ38 v3.0 laws/dieu38-normative-document-law.md amendments/dieu38-normative-document-law-v3-amendment-draft.md Preserve the 3 MT goals / Text-as-Code / IU-Smart-Brick / LSL-01; constrain "DOT 100%" to 100%-automatable detection; no auto-fix / no auto-output-regen / no auto-rewrite of enacted text / no auto-schema; output = render-at-promote.

3.3 AMEND_ENACTED vs REVISE_DRAFT_DIRECTION (addresses E0-L3)

The 5 AMEND records are not all the same kind of "amendment":

  • AMEND_ENACTED (2 records): Đ22 (#2), Đ33 (#3). 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.
  • REVISE_DRAFT_DIRECTION (3 records): Đ36 (#4), L4 (#5), Đ38 v3.0 (#6). Their old target texts are themselves draft / non-enacted (Đ36 v5.0 DRAFT — v4.0 was the last enacted; L4 DỰ THẢO; Đ38 v3.0 DRAFT). "Amending" these is really revising a draft's direction, not amending enacted law. Each draft discloses its target's draft-status and states it "does not enact or adopt."

All five remain DRAFT / PENDING_OWNER; none is enacted. The distinction is descriptive — it changes neither the reading rule (READ_AMENDMENT_DRAFT_PENDING_OWNER) nor the non-enacting status; it just tells a reader whether the thing being revised is enacted law or a prior draft.


4. Eight note pointers (written KEEP+NOTE notes)

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

Record Old law (provenance) Note pointer (newlaws/notes/…) What it clarifies (old law unchanged)
#14 laws/constitution.md (SUPREME) constitution-compatibility-note.md 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 = 15 NT, not 13.
#15 laws/terminology-glossary.md terminology-compatibility-note.md Glossary stays the vocab anchor; new terms (TEMP_ID/BIRTH_STAMP, brick vs candidate, scanner vs checker, cell_id, One-Roof) are candidate vocabulary for a future Owner-gated glossary addition — not added now.
#8 laws/law-01-foundation-principles.md dieu1-foundation-principles-compatibility-note.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.
#11 laws/dieu32-approval-law.md dieu32-approval-owner-gate-compatibility-note.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."
#12 laws/dieu35-dot-governance-law.md dieu35-dot-governance-compatibility-note.md Đ35 stays enacted; new model reuses the fix_repair_dot pattern but rejects DOT-as-engine and reads the secondary engine as scanner-list-only. Carries Đ35 production-readiness FAIL + RISK-BYPASS.
#23 laws/dieu39-knowledge-graph-law.md dieu39-knowledge-graph-compatibility-note.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 Note"; does NOT authorize the one-block KG rollout (runtime-EMPTY).
#13 laws/law-04-birth-process.md dieu4-birth-process-compatibility-note.md Birth grants identity-root, not canonical status: certified=false ⇒ TEMP_ID/F1; canonical = output at promote/F4. Why KEEP+NOTE not AMEND: Đ4/Đ0-G don't force canonical-at-INSERT; the AMEND pressure lives in L4 (#5) + Đ38 v3.0 (#6).
#16 laws/dieu38-appendix-01-objectives.md dieu38-text-as-code-appendix01-compatibility-note.md Closest enacted analogue to D4 (IU/Smart Brick) + D5 (Temp Store). MT0A/MT0B read as reference-only Module-Contract-First; live IO contract is the thin 5-field — which wins = CONS-002 open. Distinct from Đ38 v3.0 DRAFT (#6) and L4 (#5).

5. Seventeen future-note records (KEEP+NOTE, note NOT yet written)

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 (§11). Writing these 17 notes is future, Owner-gated Batch-A workD1 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 (§4) + 17 not-yet-written (§5) = 25 KEEP+NOTE. Consistent.


6. Six KEEP records (READ_OLD_AS_IS — no artifact, none needed)

These 6 are compatible with the F0→F5/FX model as-is. Read the old law in laws/ (or ssot/) directly. No note, amendment, or rewrite exists or is needed.

# Old law (provenance) Short title D1 reading rule
32 laws/dieu20-thiet-ke-truoc-trien-khai.md Điều 20 — Design Before Execution v1.2 READ_OLD_AS_IS
33 laws/dieu30-regression-protection-law.md Điều 30 — Regression Protection v1.2 READ_OLD_AS_IS
34 ssot/operating-rules.md Operating Rules v7.58 (Concise) READ_OLD_AS_IS
35 laws/law-15-16-state-checkpoint.md Điều 15-16 — State Machine + Checkpoint READ_OLD_AS_IS
36 laws/law-06-sync.md Điều 6 — Sync Law READ_OLD_AS_IS
37 laws/law-07-assembly-first.md Điều 7 — Assembly First (Luật Tận dụng) READ_OLD_AS_IS

7. Sixteen DEFER records (DEFER_DO_NOT_USE — audit/history only)

These 16 are superseded, implementation-specific, obsolete, or too deep for this phase. Do not use any of them as a source for new design now. Audit/history only. D1 does not make any DEFER record an active source.

# Old source (provenance) Short title Why DEFER
38 laws/constitution-v4.2.0-amendment-draft.md Constitution v4.2.0 Amendment Draft superseded by enacted v4.6.3
39 laws/dieu28-trien-khai/ (~27 files) D28 Display Tech implementation bucket implementation-specific
40 laws/dieu38-trien-khai/ (~150 files) D38 Text-as-Code implementation bucket implementation-specific (excl. #5 L4, #27 LSL-01)
41 laws/dieu41-revision-rulings/ (2 files) D41 Revision Rulings bucket implementation-specific
42 laws/dieu43-migrations/ (23 files) D43 Migrations bucket implementation-specific
43 laws/dieu44-trien-khai/ (~350+ files) D44 UOSL implementation bucket implementation-specific (excl. #51 README)
44 laws/dieu43-system-context-law-draft.md + others Superseded Đ43 drafts/backup + Đ44 UOSL GPT-review superseded
45 laws/dieu28-display-technology-law.md Điều 28 — Display Technology v2.0 deep / out-of-phase
46 laws/dieu3-phu-luc-description-templates.md Điều 3 Phụ lục — Description Templates deep / out-of-phase
47 laws/dieu34-workflow-law.md Điều 34 — Workflow v1.0 unenacted draft
48 laws/dieu35-dot-governance-law-v5-0-backup.md Điều 35 v5.0 FINAL (BACKUP) superseded by v5.2
49 laws/dieu35-dot-governance-law-v5-1-draft.md Điều 35 v5.1 DRAFT superseded by v5.2
50 laws/dieu41-phu-luc-ke-hoach-trien-khai.md Điều 41 Phụ lục — Deployment Plan living doc / out-of-phase
51 laws/dieu44-trien-khai/README.md Điều 44 — UOSL implementation README implementation-specific
52 laws/dieu41-luat-van-hanh-ma-vps-draft-v0.{2..5.1} (7 files) Superseded D41 drafts + Council Review Requests superseded by v1.1
53 laws/dieu44-universal-object-schema-law.md Điều 44 — UOSL v0.1.2 (controlled DRAFT) not enacted

8. Source-recovery caveats (must travel with this layer)

From reports/source-recovery-dieu0-dieu0b-dieu0g-2026-06-17.md (B0). These are unresolved Owner-gated items and must be attached to any reading that touches birth/foundation reasoning. D1 resolves none of them.

  • Operative texts live in architecture/, not laws/: Đ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).
  • The Constitution's file pointers are broken: its 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/ (only law-00h-5layer-sync.md exists).
  • architecture/ is working-source, NOT supreme: existing-law-references.md states 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/v3.1; (3) CONS-003 — 6 vs 7: composition_level enum = 6 Lớp vs Constitution/Đ29 "7"; root of CONS-003, gating any cell_id/canonical matrix; (4) the "authoritative-current" question for the architecture/ versions; (5) law-00sml-amendments.md absent.
  • 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.

9. Blockers carried (none resolved by D1)

D1 resolves none of these. They are carried, unresolved, and must remain open. (A non-enacting reading/provenance layer does not require resolving them; technical design, Phase-1, and implementation do.)

Blocker What it is State
RISK-BYPASS live fn_auto_approve_add (160 unvoted applies) + fn_birth_gate warn-mode + app.bypass_birth_gate kill-switch open
HOLD-1 iu_staging_* pre-promote staging liveness unproven open
HOLD-2 atomic promote has no real transaction (blocks canonical / BIRTH_STAMP / PROMOTE_STAMP at F4) open
CONS-002 IO Contract field-set: thin 5-field vs Module-Contract-First (MT0A/MT0B) open
CONS-003 6-Lớp (composition_level) vs 7-dimension (Constitution/Đ29) open
CELL-003/004/007 cell_id dimensions unmaterialized; the birth CELL is the only canonical matrix open
GOV-016/017 no risk/blast-radius calculator; no fail-closed-on-uncomputable-risk code open
GOV-REUSE-001 unproven whether universal_edges/governance_role/owner can hold the minimal governance graph open
Đ39 runtime-EMPTY enacted but ~unimplemented (registered ≠ executed; 0 DOT exec / 0 KG events; owner unregistered) open
Đ35 production-readiness FAIL audit checkpoint-codex-2026-06-05: "CORE AUDIT PASS / PRODUCTION READINESS FAIL"; 14/14 health checks not LIVE open
source-recovery Đ0/0-B/0-G 5 Owner-gated items (§8) open
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 (out of D1 scope)

Decided at F0 (NOT blockers, NOT reopened, NOT changed by D1 — addresses E0-L1): CONS-004 (authority order) and CONS-005 (freeze-candidate baseline) were decided at F0. The authority order is unchanged.


10. Tool-Kiem-Thu safety lock (carried, not executed)

  • v0.1-stable / FIX7 V3 baseline remains LOCKED. It is the authority baseline; D1 does not touch it.
  • It remains usable for FIX7 Recheck / current Codex packet verification, and is the regression/comparison fixture. It must not be overwritten.
  • v0.2-hardening is a separate dev track living on a separate dev surface; it inherits the V3 lessons (black-box oracle, fail-open regression, manifest-laundering prevention, adversarial invalid-input testing).
  • v0.2 becomes authority only after regression + Owner/User promotion — neither performed nor authorized by D1.

Do not build v0.2-hardening. Do not modify the v0.1 baseline. This layer only records the lock.


11. Bad readings this pointer layer explicitly REJECTS

A pointer is not a license. All of the following are FALSE.

Carried from the reading index / D0 (all FALSE):

  1. "Codex/GPT/Council PASS authorizes adoption or technical design." — PASS = review-complete; only the Owner enacts/opens a phase.
  2. "A pointer to a draft means the draft is enacted." — every draft here is DRAFT / PENDING_OWNER.
  3. "KEEP+NOTE notes amend the old law." — a note never amends its law; the old text stays AS-IS.
  4. "Đ39/Đ35 are live/production-ready because enacted." — Đ39 runtime-EMPTY; Đ35 production-readiness FAIL + RISK-BYPASS.
  5. "Birth INSERT = canonical now." — INSERT = uncertified TEMP; canonical = output at promote (F4).
  6. "governance_registry should be reused directly." — it conflicts with FX One-Roof; that is why Đ37 is REWRITE.
  7. "newlaws/ replaces laws/ automatically." — laws/ stays the source corpus.

D1-specific (all FALSE): 8. D1 creates a current corpus. — No. D1 is a pointer/navigation layer; no current corpus, no current/ folder, no copied law text. 9. The D1 pointer layer is current law. — No. It is a non-enacting reading map; laws/ remains the source of truth. 10. D1 adopts the AMEND drafts. — No. It points to them as DRAFT / PENDING_OWNER; it adopts/enacts nothing. 11. D1 adopts the Đ37 rewrite. — No. The rewrite stays a non-enacting DRAFT; enacted v3.3 is immutable. 12. D1 replaces laws/. — No. laws/, ssot/, architecture/ are untouched. 13. D1 authorizes technical design. — No. 14. D1 authorizes Phase-1. — No live DB/runtime query is authorized. 15. D1 resolves runtime blockers. — No; all blockers in §9 stay open. 16. D1 fixes the source-recovery Đ0/0-B/0-G items. — No; the 5 Owner-gated items stay open; the Constitution is unpatched. 17. D1 makes a DEFER doc an active design source. — No; DEFER records stay DEFER_DO_NOT_USE. 18. D1 changes the authority order. — No; CONS-004 is unchanged. 19. D1 promotes v0.2-hardening. — No; v0.1-stable / FIX7 V3 stays the locked baseline.


12. What this pointer layer does NOT authorize

Assembling this pointer layer authorizes nothing. It does not:

  • create a current corpus by copying or moving old-law files into a "current" location (this layer is pointers + notes, never copied law text that could drift from laws/); no current/ folder of any name is created;
  • edit, move, or rename anything under knowledge/dev/laws/; patch the Constitution;
  • adopt / enact any amendment, the Đ37 rewrite, or any note; declare any current law changed; put the Đ37 rewrite in force;
  • write technical design; run Phase-1; run any live DB/runtime query; implement schema/table/registry/index;
  • create governance_registry; materialize the KG, cell_id/dot_role/canonical_fields, the Species Matrix, or BIRTH_STAMP/PROMOTE_STAMP;
  • resolve any blocker (§9); change the authority order (CONS-004); change the v0.1 baseline; promote v0.2-hardening.

Future glossary work (carried, NOT done here — E0-L4): the Owner / Mức 3 / Điều 32 relationship (an authority / a risk level / an approval law — three distinct things) and the stamp family (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). Not part of D1.


13. Next decision options

This layer is the documentary output of D0 Option B. After GPT → Codex review of D1, the Owner may:

  1. Use this pointer layer as the working navigation map (alongside the re-pointed LAW_READING_INDEX.md rev2) — non-enacting; laws/ stays the source of truth; nothing is adopted.
  2. Open the glossary work (E0-L4) — a future Owner-gated, non-enacting glossary addition normalizing the Owner/Mức 3/Đ32 relationship and the stamp family.
  3. Open a separate read-only Phase-1 (D0 Option D) — scoped, read-only verification of the runtime blockers (RISK-BYPASS / HOLD-1 / HOLD-2 / Đ39 runtime / Đ35 production-readiness). This is the real gate to any future technical design and is independent of the documentary track.
  4. Request a fix to a named artifact (D0 Option C) — only if review surfaces a concrete defect.

None of these is performed by D1. Each is a separate, later, Owner-gated step. Default disposition: HOLD. Codex/Council/GPT PASS ≠ Owner authorization.


Current-Understanding Pointer Layer | Law Revision Workstream D1 rev1 | 2026-06-17 | 53/53 records pointed · 6 drafts (5 AMEND + 1 REWRITE) · 8 notes · 17 future notes · 6 KEEP · 16 DEFER | NON-ENACTING · POINTER-ONLY · NOT a current corpus · read-only · non-authorizing | Codex PASS ≠ Owner authorization

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/current-understanding-pointer-layer-2026-06-17.md