Incomex AI Portal
KB-6A99

Source Recovery — Điều 0 / 0-B / 0-G (where to read the foundation laws after Workstream A) — 2026-06-17 (read-only, non-authorizing)

14 min read Revision 1
laws-newnewlawsreportsource-recoverydieu0dieu0bdieu0garchitecturebroken-referencescons-003read-onlynon-authorizing2026-06-17workstream-b0

Source Recovery — Điều 0 / 0-B / 0-G

Law Revision Workstream B0. READ-ONLY · NON-AUTHORIZING. 2026-06-17, rev1. STATUS: COMPLETE as a source-recovery navigation report (all sources read first-hand; no source-access failure). It confirms where Điều 0 / 0-B / 0-G should be read from as a temporary working source, and it surfaces the formal reconciliation items that remain Owner-gated. It does not move/copy/rename any file, does not patch the Constitution, and does not create a canonical/current corpus. Basis: Constitution laws/constitution.md v4.6.3 (rev44), laws/existing-law-references.md (rev1), architecture/information-atom-law.md (Đ0), architecture/composition-level-law.md (Đ0-B), architecture/birth-registry-law.md (Đ0-G), Workstream A LAW_READING_INDEX.md §2 + reports/birth-embedded-dieu0-dieu0b-dieu0g-check-2026-06-17.md, and the law-merge-administrative-phase-gate-2026-06-17.md.

0. Why this report exists

Workstream A discovered, while answering the Birth questions (Goal C), that the Constitution references law-00*.md files for Điều 0 / 0-B / 0-G that do not exist in knowledge/dev/laws/. Workstream A located the operative texts in knowledge/dev/architecture/ and answered the birth questions from there, marking that goal PARTIAL on the source-location finding and recommending an Owner-gated source-recovery pass.

B0 is that recovery pass at the navigation / provenance level only. It answers: which source should a human or agent read for Điều 0 / 0-B / 0-G until the Constitution's broken references are formally reconciled? It is not authority to rewrite the Constitution, promote architecture/ to supreme, or build a canonical current corpus.

1. The nine questions (direct answers)

Q1. What does the Constitution reference for Đ0 / 0-B / 0-G?

The Constitution's MỤC LỤC LUẬT → Nền tảng table (laws/constitution.md v4.6.3, rev44) lists, verbatim:

Điều Tên File (as written in the Constitution)
0 Luật Thực thể + Bảo toàn law-00-entity.md
0-B 7 Lớp Cấu tạo (33 species) law-00b-composition.md
0-G Luật Khai Sinh law-00g-birth.md
0-H Đồng bộ 5 Tầng + DOT 2 cấp law-00h-5layer-sync.md
0-S/M/L Single Provider, Đo lường, Dùng lại law-00sml-amendments.md
1 13 Nguyên tắc Nền tảng law-01-foundation-principles.md

So the Constitution points Đ0 → law-00-entity.md, Đ0-B → law-00b-composition.md, Đ0-G → law-00g-birth.md. The Constitution does not embed the full article text of Đ0 / 0-B / 0-G — it only references these files. (It does embed the 15 Nguyên tắc, the 4-DB/3-layer architecture, and the MỤC LỤC, but not the Đ0/0-B/0-G bodies.)

Q2. Are those referenced files present under knowledge/dev/laws/?

No. A list_documents on prefix knowledge/dev/laws/law-00 returns exactly one document: law-00h-5layer-sync.md (Điều 0-H). The three files the Constitution names for Đ0 / 0-B / 0-G — law-00-entity.md, law-00b-composition.md, law-00g-birth.md — are absent from laws/. (law-00sml-amendments.md, referenced for Đ0-S/M/L, is also absent.) The Constitution's references for the deepest foundation laws are therefore broken file pointers with respect to the laws/ corpus.

Q3. What source files were actually found under knowledge/dev/architecture/?

The operative texts were located in architecture/ and read in full in this workstream:

Law architecture/ file Title (verbatim) Version rev content_length
Đ0 architecture/information-atom-law.md "Luật Thực thể Được Quản trị — Nền tảng Cơ bản Nhất (Điều 0)" v2.0 (S111) 18 17,712
Đ0-B architecture/composition-level-law.md "Điều 0-B: Luật Phân tầng Cấu tạo Vật chất Thông tin" file title v3.0 / body header v3.1 (S111) 22 12,146
Đ0-G architecture/birth-registry-law.md "Điều 0-G: Luật Khai Sinh — Birth Registry Law" v1.0 (S157) 2 11,681

Content confirmed first-hand:

  • Đ0 defines a managed entity by 5 conditions (unique PREFIX-NNN ID that is never reused, registered in a queryable registry, full metadata, 8 relation rules, a "Lớp 3" page) and the conservation principles (ID never reused, relations don't self-destruct, metadata only grows, registry never shrinks). It uses no TEMP_ID / BIRTH_STAMP / canonical-birth vocabulary.
  • Đ0-B defines the composition axis. Its composition_level enum is exactly 6 Lớp: atom, molecule, compound, material, product, building (plus a sub-atomic "Lớp 0 / Quark" that is not a managed entity). "CHỈ NÂNG, KHÔNG HẠ" (upgrade-only).
  • Đ0-G defines the Birth Registry. fn_birth_registry_auto fires on INSERT into a governed collection and writes a birth_registry row with born_at=now(), certified=false (DEFAULT), ON CONFLICT (entity_code) DO NOTHING. Certification (certified=true) is a separate, later event via the PEN → STAMP → GATE inspector pipeline + an AFTER-UPDATE auto-certify.

Q4. Does existing-law-references.md support architecture/ as the detailed reference?

Yes — explicitly, and with an explicit subordination. laws/existing-law-references.md (rev1) opens:

"Các Điều dưới đây có file chi tiết trong knowledge/dev/architecture/. Constitution v4.0 (laws/) là tài liệu CHÍNH. File architecture/ = tham khảo chi tiết."

and maps, verbatim:

"### Điều 0: Luật Thực thể → architecture/information-atom-law.md (v2.0)" "### Điều 0-B: 7 Lớp Cấu tạo → architecture/composition-level-law.md (v3.0) — 7 lớp. 33 species." "### Điều 0-G: Luật Khai Sinh → architecture/birth-registry-law.md (v1.0)"

So existing-law-references.md designates architecture/ as the "tham khảo chi tiết" (detailed reference) home of the foundation laws, explicitly subordinate to the Constitution as "tài liệu CHÍNH" (the main/authoritative document).

Q5. Can architecture/ be treated as a temporary working source?

Yes. Confirmed on two independent grounds: (a) existing-law-references.md designates architecture/ as the detailed-reference home of Đ0 / 0-B / 0-G, and (b) the files are present and self-consistent (read in full this workstream). Therefore an agent or human who needs the current working understanding of Đ0 / 0-B / 0-G should read the architecture/ file, not a non-existent laws/law-00*.md. This matches LAW_READING_INDEX.md §2. It is a working / detailed source — usable for reasoning and for grounding compatibility notes — subject to the open reconciliation items in §3 below.

Q6. Can architecture/ be treated as supreme / enacted by itself?

No. Two reasons:

  1. The Constitution is the declared supreme text: "Văn bản tối cao. Vi phạm Hiến pháp = vi phạm nghiêm trọng nhất." architecture/ cannot outrank it.
  2. existing-law-references.md itself subordinates architecture/ as "tham khảo chi tiết" under the Constitution as "tài liệu CHÍNH." A detailed reference is not the enacting instrument.

Therefore: architecture/ is the temporary/detailed working source for the text of Đ0 / 0-B / 0-G, but it is not supreme and not the enacting authority by itself. Supremacy and enacting authority remain with the Constitution. Where the Constitution and an architecture/ file disagree, that disagreement is an open reconciliation item (Owner-gated), not something architecture/ wins by default.

Q7. What should LAW_READING_INDEX say until source recovery is fully resolved?

LAW_READING_INDEX.md §2 already carries the correct navigation caveat and should keep it, refined by this report:

  1. For any index entry that points to Đ0 / 0-B / 0-G or "the embedded birth law," read the architecture/ file (information-atom-law.md / composition-level-law.md / birth-registry-law.md), not a non-existent laws/law-00*.md.
  2. State that architecture/ is a temporary / detailed working source, subordinate to the Constitution — not supreme, not the enacting authority.
  3. Flag that an Owner-gated source-recovery pass must reconcile (a) the Constitution's broken law-00*.md references, (b) the version drift (see §3), and (c) CONS-003 (6 Lớp vs 7), before any birth-related technical design.
  4. Keep laws/ as the source/provenance corpus and newlaws/ as the only workspace; this report does not change that.

Q8. What should future Birth / L4 / Đ36 / Đ38 amendment work depend on?

Future birth-related amendment/technical-design work should depend on, in order:

  1. A resolved source-recovery decision (Owner-gated): confirm whether the architecture/ Đ0 / 0-B / 0-G versions are the authoritative current texts, and reconcile the Constitution's broken references — before building new birth design on them.
  2. CONS-003 resolution (Owner-gated): the 6-vs-7 framing (§3) is rooted in Đ0-B + species-taxonomy and is the gate for cell_id and the canonical matrix (CELL-003/004/007).
  3. The Workstream A birth findings (reports/birth-embedded-…-2026-06-17.md): Đ4 stays KEEP+NOTE; the genuine AMEND pressure is L4 — Birth Gate Extension (relocate INSERT-time completeness/reuse/approval to the promote checker) and Đ38 v3.0 — not Đ0 / 0-G / Đ4 themselves.
  4. HOLD-2 (atomic promote transaction does not yet exist) and RISK-BYPASS remain carried; canonical/BIRTH_STAMP at promote (F4) is gated on them.

Until the source-recovery decision is made by the Owner, future birth work should treat the architecture/ texts as working/background, not as the settled authoritative current corpus.

Q9. What remains unresolved?

  1. Broken Constitution references. law-00-entity.md, law-00b-composition.md, law-00g-birth.md (and law-00sml-amendments.md) are named by the Constitution but absent from laws/. The Constitution itself has not been patched (and must not be, in this workstream).
  2. Version drift on Đ0-B. The composition-level-law.md file title reads v3.0 while its body header reads v3.1 (S111); existing-law-references.md cites it as v3.0. These should be reconciled to a single authoritative version label.
  3. CONS-003 — 6 vs 7. The architecture law composition_level enum is 6 Lớp (atom…building); the Constitution MỤC LỤC frames Đ0-B as "7 Lớp (33 species)" and Đ29 as "33 species, 7 dimensions"; the birth_registry schema comment says "6+1: …/building/meta." This 6-vs-7 (composition layers vs composition+species "dimensions") is the root of CONS-003 and is not resolved here.
  4. Authoritative-current question. Whether the architecture/ versions are the authoritative current texts (vs documentary ancestors that the Constitution intended to supersede via the missing law-00*.md) is an Owner decision not made here.
  5. law-00sml-amendments.md (Đ0-S/M/L) is referenced but absent; the present file appears to be architecture/constitution-amendment-measurement.md (v3.8). Out of B0 scope to confirm as the substitute — flagged for the same recovery pass.

All five are Owner-gated. This report records them; it does not decide them.

2. One-line recovery rule (recorded, not enacted)

Until an Owner-gated source-recovery pass reconciles the Constitution's broken law-00*.md references, read Đ0 / 0-B / 0-G from architecture/information-atom-law.md / composition-level-law.md / birth-registry-law.md as the temporary, detailed working source. The Constitution remains supreme; architecture/ is reference, not enacting authority. Do not build birth-related technical design on these texts until the recovery pass and CONS-003 are resolved.

3. What was NOT done (scope discipline)

No file under knowledge/dev/laws/ was edited, moved, renamed, deleted, or created. No Constitution patch. No canonical/current corpus created. No copy of laws into newlaws/. No technical design. No Phase-1. No live DB/runtime query (the birth_registry schema/trigger snapshots quoted above are read from the architecture/ law text's own documentary DDL, not from a live database). No resolution of CONS-002/003/004/005, CELL-003/004/007, HOLD-1/HOLD-2, RISK-BYPASS. No authority-order change. No change to the v0.1-stable / FIX7 V3 baseline.

4. Non-authorization

This report does NOT: enact, amend, rewrite, re-enact, supersede, move, rename, or delete any law; promote architecture/ to supreme or enacted status; patch the Constitution; 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 (CONS-004); or change the v0.1-stable / FIX7 V3 baseline. Default disposition until the Owner acts: HOLD. Engineering/navigation COMPLETE ≠ Owner authorization. Codex PASS ≠ Owner authorization.

Source Recovery rev1 | 2026-06-17 | COMPLETE (navigation) · 5 open items Owner-gated | read-only · non-authorizing | architecture/ = temporary detailed working source, NOT supreme