Điều 38 — Text as Code, Phụ lục 01 (Objectives) — Compatibility Note

Reading category: READ_OLD_WITH_COMPATIBILITY_NOTE (catalog record #16, KEEP+NOTE). Status of this note: READ-ONLY · NON-AUTHORIZING · NOT enacted law. 2026-06-17, rev1.

1. Old source

• Path: knowledge/dev/laws/dieu38-appendix-01-objectives.md — "Text as Code — Mục tiêu — Phụ lục 01 Điều 38" (BAN HÀNH 2026-04-24).
• Status: ENACTED. This is the objectives / problem-statement appendix ("Phụ lục 02 = Giải pháp" is a separate, later file). Distinct from the Điều 38 v3.0 DRAFT (dieu38-normative-document-law.md, catalog record #6 = AMEND) and from L4 (record #5 = AMEND).

2. Preserved goal

Build a PG-native platform that turns every governance document into intelligent data — value chain Text → Code → Workflow → Knowledge ("Luật là pilot — không phải đích"; design once, serve all document types). Key objectives preserved: MT1 atomization into addressable, versionable units; MT2 birth gate = completeness at INSERT (extends Đ0-G) vs DOT/checker = correctness (extends Đ22); MT0A SSOT Catalog / MT0B Component Registry / MT0C Reuse Decision (reuse→config→variant→new).

3. How F0→F5/FX interprets it

• This appendix is the closest enacted analogue to D4 (Information Unit / Smart Brick) + D5 (Temp Store / Candidate). Compatible and kept: atomization → brick = subject; "the authoritative content lives in the unit, the vector chunk is a projection, never the SoT" (aligned with LSL-01); reuse-first MT0C → the new model's reuse-first decision rule.
• MT2 completeness-vs-correctness split maps to: birth gate = completeness at the TEMP stage; checker = correctness at promote. Completeness ≠ canonical.
• NOTE (this enacted appendix, read with care): MT0A SSOT-Catalog + MT0B Component-Registry read as reference-only Module-Contract-First; the live IO contract in the new model is the thin 5-field one — which source wins is CONS-002 (open). MT14 dashboard ≈ the coverage-scanner that is DESIGN-ONLY / BUILD-NO-GO. List-oriented objectives map to scanner = list-only.

4. What is NOT authorized

• Not building SSOT Catalog / Component Registry as a central system now; not treating MT0A/MT0B as the live contract (the live contract is thin 5-field; CONS-002 must be resolved first).
• Not writing the Điều 38 v3.0 amendment (record #6, future Batch B) or the L4 amendment (record #5) — those are separate AMEND items.
• This appendix itself is KEEP+NOTE (enacted, keep). No technical design, Phase-1, live query, schema/registry change, or authority-order change.

5. Remaining blockers / caveats

• CONS-002 (BLOCKER) — IO Contract field-set: thin 5-field vs Module-Contract-First (MT0A/MT0B); blocks IO_STAMP.
• Coverage-scanner BUILD-NO-GO — the MT14-style dashboard / dot_governance_coverage_* is design-only, absent live.
• HOLD-1 — iu_staging_* temp store is documentary, Phase-1-gated.
• The AMEND siblings (Đ38 v3.0 = record #6; L4 = record #5) carry the "DOT 100% auto-fix" / "birth-at-INSERT" conflicts; this appendix does not.

6. Where this fits in the index

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

7. Bad readings this note rejects

• "MT0A/MT0B (SSOT Catalog / Component Registry) is the enacted IO/contract model to build now" → FALSE; reference-only; live contract is thin 5-field; CONS-002 open.
• "Text as Code means free text-to-code generation" → FALSE; the appendix itself states "Text as Code ≠ text sinh code tự do."
• "Điều 38 v3.0 / L4 should be amended now because of this note" → FALSE; those are future Batch B AMEND items.
• "This appendix should be AMEND/REWRITE" → FALSE; the enacted appendix is KEEP+NOTE; the DRAFT v3.0 (record #6) is the AMEND one.

Điều 38 Appendix-01 compatibility note rev1 | 2026-06-17 | read-only · non-authorizing | objectives kept · contract = CONS-002