Điều 4 — Birth Process (Luật Sinh sản) — Compatibility Note

Reading category: READ_OLD_WITH_COMPATIBILITY_NOTE (catalog record #13, KEEP+NOTE). Status of this note: READ-ONLY · NON-AUTHORIZING · NOT enacted law. 2026-06-17, rev1. Companion: reports/birth-embedded-dieu0-dieu0b-dieu0g-check-2026-06-17.md (the Đ0/0-B/0-G read).

1. Old source

• Path: knowledge/dev/laws/law-04-birth-process.md — "ĐIỀU 4: LUẬT SINH SẢN — KHÔNG AI ĐƯỢC 'ĐẺ BỪA BÃI'" (changelog: S178 Fix 23 / Fix 28).
• Status: ENACTED/active (Council 2-round APPROVE). No top version label in the file — flag for a source-recovery pass.
• Related foundation text: Điều 0-G "Luật Khai Sinh" lives at knowledge/dev/architecture/birth-registry-law.md (v1.0/S157), not in laws/ and not embedded in the Constitution.

2. Preserved goal

No entity is created without process: create via DOT/script, auto-assign ID, auto-register to the registry, assign minimum metadata, notify related systems. The Birth Description Guard (fn_description_birth_guard, BEFORE INSERT) enforces completeness at the moment of birth. All preserved.

3. How F0→F5/FX interprets it

• Birth grants an identity-root, not canonical status. At INSERT, an entity gets its permanent PREFIX-NNN id and (per Đ0-G) an uncertified birth_registry record (certified=false). It does not become canonical/certified at INSERT.
• Mapping: {PREFIX-NNN + certified=false at INSERT} ⇒ TEMP_ID / workspace stage (F1); {certified=true / certified_at} (Đ0-G) and {BIRTH_STAMP / PROMOTE_STAMP} ⇒ canonical birth = output at promote (F4).
• fn_description_birth_guard (Đ4 §2.1) = a TEMP-stage completeness stamp, not a canonical-birth gate — completeness ≠ canonical (Đ38 Appendix-01 makes the same completeness-vs-correctness split).
• Đ0-G's async DOT-inspector certification (PEN→STAMP→GATE→auto-certify) is the documentary ancestor of the F4 promote checker. Under the new model, certification of canonical / kernel / enacted entities must pass the fail-closed promote checker + Owner gate (Mức 3 / Đ32), not async auto-certify alone.
• Why KEEP+NOTE, not AMEND: Điều 4 (and Đ0-G) do not force canonical-at-INSERT; a compatibility note that supplies the lifecycle split is sufficient. The AMEND pressure lives in L4 — Birth Gate Extension (record #5), which front-loads completeness + reuse-decision + human-approval at INSERT, and in Điều 38 v3.0 (record #6) — not in Điều 4. Keep Điều 4 conservative.

4. What is NOT authorized

• No birth amendment text (that is a future Batch B item, focused on L4 / Đ38 v3.0, not Đ4).
• No treating a birth_registry INSERT as canonical birth.
• No change to Điều 4 or Điều 0-G; no technical design, Phase-1, live query, schema/registry change, or authority-order change.

5. Remaining blockers / caveats

• HOLD-2 (BLOCKER) — atomic promote has no real transaction; blocks the canonical / BIRTH_STAMP write at promote.
• RISK-BYPASS — fn_birth_gate (Đ35-scope) is warn-mode + kill-switch and co-resides with fn_description_birth_guard on dot_tools; cannot be trusted until Phase-1-verified.
• CONS-003 + CELL-003/004/007 — the birth CELL (layer × species × store × domain) is the only canonical matrix and is unmaterialized.
• Source-location caveat — Đ0-G is in architecture/, not laws/; the Constitution's law-00g-birth.md reference is broken; reconcile in source-recovery.

6. Where this fits in the index

LAW_READING_INDEX.md §3.2, record #13, category READ_OLD_WITH_COMPATIBILITY_NOTE.

7. Bad readings this note rejects

• "Birth registry INSERT means canonical birth now" → FALSE; the record is created certified=false; canonical = output at promote (F4).
• "fn_description_birth_guard at INSERT is the canonical-birth gate" → FALSE; it is a completeness stamp at the TEMP stage.
• "Because of Đ0-G, Birth must move to AMEND" → FALSE; Đ4 = KEEP+NOTE; the AMEND targets are L4 (#5) and Đ38 v3.0 (#6).
• "This note amends Điều 4 / Điều 0-G" → FALSE.

Điều 4 compatibility note rev1 | 2026-06-17 | read-only · non-authorizing | TEMP_ID at birth · canonical at promote