03 — Content Map by Topic (Workstream B)

All 7 candidates as actionable content packages. Mapping only — no IU body edited, no topic promoted, no tag deleted. Source for every IU below: knowledge/dev/laws/dieu39-knowledge-graph-law.md (law_unit, draft).

---

1. knowledge_graph — STRONG (10 IU) — PILOT TOPIC

• node_code: TOPIC-CAND:knowledge_graph
• IUs (10): 09682146 (#1-26-bai-toan), 10649925 (#7-36-dot-kg), 3676cc0c (#0-tam-nhin), 57553011 (#9-11-nt), 620f7646 (#3-4-nhom-a-b), a448e397 (#2-dinh-nghia), a7bba115 (#8-kien-truc), c96b53fd (#12-quan-he), e97fc334 (#5-nhom-c), f1273184 (#title)
• Related documents: the KG Law doc itself (anchor); no derived knowledge_documents yet (bridge unpopulated).
• Related process candidates: KG_DOT_CLUSTER (18 dot-kg DOTs) — SHARED_IU+DOMAIN, the strongest cross-axis tie in the system. Also CUT_PIPELINE (shared IU 620f7646) and APPROVAL_WF (promotion route).
• Relation gaps: no document-template, no enrichment workflow, no edges (universal_edges topic↔topic empty for this node).
• Content value: HIGH — a complete, sectioned law defining the KG; ready to become a curated KG knowledge cluster.
• Business/process value: HIGH — directly governs 18 live DOTs.
• Confidence: HIGH.
• Next editorial action: (a) author the 10 sections into a coherent KG cluster; (b) attach a KG document-template + enrichment workflow (queued AXR-TOPIC-14); (c) link to the dot-kg process cluster via the joint map.
• Governance decision needed: GOV-COUNCIL FAC-08 root (AXR-TOPIC-03) + content owner.
• Recommendation: ROOT TOPIC.

2. architecture — STRONG (5 IU)

• IUs (5): 1b0f91d3 (#7c-moi-truong-thuc-thi), 3676cc0c (#0-tam-nhin), a7bba115 (#8-kien-truc), a8e7f4db (#13-no-ky-thuat), f1273184 (#title)* — *3 shared with knowledge_graph.
• Related process: KG_DOT_CLUSTER (INFERRED — arch sections describe DOT architecture).
• Relation gaps: no docs/edges; 3/5 IUs borrowed from knowledge_graph → strong related edge candidate.
• Content value: HIGH (architecture/tech-debt sections). Confidence: HIGH.
• Next editorial action: promote root; add related edge architecture↔knowledge_graph (shared 3 IUs).
• Governance decision needed: GOV-COUNCIL root (AXR-TOPIC-04).
• Recommendation: ROOT TOPIC (sibling-of-KG with related edge).

3. dot_trigger — MODERATE (3 IU)

• IUs (3): 10649925 (#7-36-dot-kg, shared w/ KG), 1b0f91d3 (#7c, shared w/ architecture), e5d9bed3 (#7b-bien-phap-quan-ly).
• Related process: KG_DOT_CLUSTER (SHARED_IU+DOMAIN via 10649925) + TAC_DOT_CLUSTER (SHARED_DOMAIN). This topic is the content face of the entire Type-1 DOT-contained process family.
• Relation gaps: thin (3 IU, all borrowed); but process-side evidence is very strong (57 Type-1 DOTs).
• Content value: MEDIUM. Process value: HIGH. Confidence: MEDIUM.
• Next editorial action: GOV review → root; gather more IUs from DOT spec docs.
• Recommendation: ROOT TOPIC (or child of a future process/automation parent) — strong process anchor.

4. governance — MODERATE (3 IU)

• IUs (3): 1cded144 (#changelog), 57553011 (#9-11-nt, shared w/ KG), e5d9bed3 (#7b, shared w/ dot_trigger).
• Related process: APPROVAL_WF (SHARED_DOMAIN) — content face of the approval/birth-gate process.
• Content value: MEDIUM. Confidence: MEDIUM.
• Next editorial action: GOV review → root; couple to approval-workflow process docs.
• Recommendation: ROOT TOPIC.

5. workflow — WEAK (2 IU)

• IUs (2): d933ec87 (#6-10-quy-trinh, shared w/ cut_pipeline), f17d8fda (#10-roadmap).
• Related process: CUT_PIPELINE (SHARED_IU+NAME) + WF_HUMAN (SHARED_DOMAIN). The workflow topic literally shares its key IU with the cut_pipeline topic and names the WF/job processes.
• Relation gaps: overlaps cut_pipeline; decide hierarchy.
• Content value: LOW. Process value: HIGH (it is the content face of AX-PROCESS itself). Confidence: LOW (as topic), HIGH (as process anchor).
• Next editorial action: DEFER as standalone topic; consider making cut_pipeline a child of workflow.
• Recommendation: DEFER / candidate parent for the pipeline siblings.

6. cut_pipeline — WEAK / SIBLING (1 IU)

• IU (1): d933ec87 — identical to workflow's IU. Its only evidence is borrowed.
• Related process: CUT_PIPELINE (DIRECT_NAME_MATCH — the one topic whose label exactly names a live process object). Strong process tie, weak content tie.
• Recommendation: CHILD of workflow (or fold in). Resolve before promote (AXR-TOPIC-08). It is a real process but a derivative topic.

7. render_pipeline — WEAK / SIBLING (1 IU)

• IU (1): 620f7646 — identical to a knowledge_graph IU (#3-4-nhom-a-b). Borrowed evidence.
• Related process: SIBLING_TOKEN to CUT_PIPELINE; no render process object exists (gap).
• Recommendation: FOLD into knowledge_graph (shares the IU) or DEFER under a pipeline parent. Has neither independent content nor a process object (AXR-TOPIC-09).

---

Editorial classification summary

• Promote as ROOT (work now): knowledge_graph, architecture, dot_trigger, governance.
• Defer / parent candidate: workflow.
• Child / fold (resolve siblings first): cut_pipeline (→ workflow), render_pipeline (→ knowledge_graph).

Key content insight

The 7 topics are facets of a single law document, and their overlap graph (shared IUs) is the seed topic-DAG: architecture↔knowledge_graph (3 shared), dot_trigger↔knowledge_graph/architecture, workflow↔cut_pipeline, render_pipeline↔knowledge_graph. Editorial parent/child/related decisions should be driven by shared-IU adjacency, not per-topic counts. The two weakest topics' only evidence is borrowed from stronger topics — a concrete dedup signal, not noise.