Điều 39 — Knowledge Graph (v2.3) — Compatibility Note

Reading category: READ_OLD_WITH_COMPATIBILITY_NOTE (catalog record #23, KEEP+NOTE). Status of this note: READ-ONLY · NON-AUTHORIZING · NOT enacted law. 2026-06-17, rev1. Basis: FX execution report reports/fx/fx-governance-one-roof-dieu39-compatibility-execution-report-2026-06-16.md (§5).

1. Old source

• Path: knowledge/dev/laws/dieu39-knowledge-graph-law.md — "LUẬT KNOWLEDGE GRAPH v2.3 — BAN HÀNH" (S159, Council 3 rounds).
• Status: ENACTED — but runtime-EMPTY. "Enacted ≠ implemented." 0 DOT executions, 0 KG events; KG owner unregistered in governance_registry; registry IUs lifecycle_status=draft despite the BAN HÀNH header. EKGF Cấp 1 / Phase 0.

2. Preserved goal

All Điều 39 goals are preserved (Q1 = directly compatible):

• Vision: "Tạo ra Knowledge Graph đủ tin cậy để AI ra quyết định và điều hành hoạt động kinh doanh."
• 5-tier value chain: Data → Data Graph → Knowledge Graph → Priority Graph → AI quyết định → Con người giám sát.
• Golden rule: "AI ĐƯỢC ĐỀ XUẤT, KHÔNG ĐƯỢC TỰ BAN HÀNH TRI THỨC CHUẨN" + "KHÔNG CÓ rule = CẤM auto = mặc định human."
• TBox (schema/scaffold/ontology) = human-approved; ABox (data/link/weight) = AI auto.
• Provenance/trust: trust_score with provenance weighting; "Không provenance = quarantine."
• C5 narrow output: Điều 39 produces an Ordered Task List + static Goal State only.

3. How F0→F5/FX interprets it (under FX)

• Điều 39 is the mandatory FX compatibility source. The golden rule maps to laws-new fail-closed / escalate to Mức 3 / Đ32; TBox-human/ABox-AI maps to Mức 3; provenance/trust maps to stamp + provenance, missing-stamp → quarantine (scanner); C5 maps to "DOT = một việc hẹp"; self-learning may touch ABox weights only, never TBox / canonical.
• Recommended FUTURE artifact (not written here): a "Điều 39 Compatibility / Reinterpretation Note" whose verdict is: preserve Điều 39 goals; deliver them incrementally through F0→F5 + FX + Phase-1 + technical design — one KG fact-type, one PG-only DOT, one stamp/provenance at a time. This is a recommendation; FX writes/rewrites nothing, and the Điều 39 text stays enacted and unchanged.

4. What is NOT authorized

• Not the Điều 39 rollout as one block: 36 DOT-KG / 18 pairs (22 need Agent API, 14 PG-only), 14 kg_* config tables defined together, 24/7 self-learning (C9 RLKGF), scaffold auto-build, per-person HTN trees. That big-bang conflicts with the staged, gated, reuse-first model.
• Not treating Điều 39 as live, implemented, or production-ready.
• Not writing the "Điều 39 Compatibility/Reinterpretation Note" now — that is a future Owner-gated artifact (Batch A / route A).
• No technical design, Phase-1, live query, schema/registry change, or authority-order change. Self-learning must never change TBox/canonical.

5. Remaining blockers / caveats

• Điều 39 runtime EMPTY — registered ≠ executed ≠ live ≠ production-ready (36/36 DOT registered, last_executed NULL, 0 runs).
• RISK-BYPASS — kg_auto_approve_rules auto-posture must be closed/fail-closed before any KG auto-approve path; relates to the live fn_auto_approve_add bypass (Đ35 note).
• GOV-016/017, GOV-REUSE-001 — no risk/blast-radius calculator; unproven whether universal_edges/governance_role/owner can hold the minimal governance graph.
• Phase-1 must verify KG runtime liveness and the kg_* tables before any rollout.

6. Where this fits in the index

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

7. Bad readings this note rejects

• "Điều 39 is live because it is enacted (BAN HÀNH)" → FALSE; runtime-EMPTY.
• "36 DOT-KG registered means executed / live / production-ready" → FALSE; registered ≠ executed.
• "Self-learning can update the schema/ontology (TBox)" → FALSE; ABox-only, never TBox/canonical.
• "KEEP+NOTE means the Điều 39 compatibility note is enacted / already written" → FALSE; it is a future Owner-gated recommendation.

Điều 39 compatibility note rev1 | 2026-06-17 | read-only · non-authorizing | enacted ≠ live · preserve goals, stage rollout