KB-3901

IP Content Work — 02 Joint Topic×Process Inventory

6 min read Revision 1
information-piecetopic-process-mapjoint-inventoryworkstream-a2026-06-04

02 — Joint Topic × Process Inventory (Workstream A)

Live artifact: v_information_piece_topic_process_map (11 rows, applied this run — see doc 09). Classification (relation_class) is editorial from evidence; all counts are live-computed from axis_assignment, v_axis_process_inventory, approval_requests.

7 topic candidates (live)

node_code label IU evidence confidence
TOPIC-CAND:knowledge_graph knowledge_graph 10 10 sections of dieu39 KG-law HIGH
TOPIC-CAND:architecture architecture 5 KG-law arch sections (#8, #7c, #title, #0) HIGH
TOPIC-CAND:dot_trigger dot_trigger 3 KG-law #7-36-dot-kg, #7c, #7b MEDIUM
TOPIC-CAND:governance governance 3 KG-law #9-11-nt, #7b, changelog MEDIUM
TOPIC-CAND:workflow workflow 2 KG-law #6-10-quy-trinh, #10-roadmap LOW
TOPIC-CAND:cut_pipeline cut_pipeline 1 KG-law #6-10-quy-trinh (shared w/ workflow) LOW (sibling)
TOPIC-CAND:render_pipeline render_pipeline 1 KG-law #3-4 (shared w/ knowledge_graph) LOW (sibling)

16 distinct IUs / 25 assignments → avg ~1.5 topics/IU. All IUs ∈ one doc.

5 pilot process candidates (live)

candidate type substrate confidence health
cut_pipeline (PIPELINE:cut) TYPE_2_AUTOMATED_MULTI 13 job_queue rows, 8 step-kinds, UNBORN STRONG WARN — 7 jobs queued/stuck since 2026-05-26, worker disabled
topic-axis candidate/approval pipeline TYPE_2/3 hybrid (implicit) axis_assignment 25 → decision_queue 7 → 14 AXR-TOPIC pending STRONG (data) OK — human gate, inert
RP aggregation / pivot-update TYPE_2 (implicit, trigger-chain) trg_pivot_def_refresh → refresh_meta_catalog + refresh_pivot_results; dot-pivot-update staged/unborn MODERATE OK
queue refresh / job workflow TYPE_2 (dormant) queue_heartbeat + v_queue_health, worker DISABLED MODERATE IDLE — no drainer
approval workflow TYPE_3 (implicit, trigger-embedded) 225 approval_requests + apr triggers; ⚠ action='add' auto-approves MODERATE OK

Process inventory shape (60 objects)

  • TYPE_1_DOT_CONTAINED = 57 (GOVERNED_NOT_BIRTH_TRACKED): 18 dot-kg-* (KG cluster), 15 TAC (schema/collection/role/birth gate), 4 COL (collection health/sync), + ~20 others (HC executor, etc.).
  • TYPE_2_AUTOMATED_MULTI = 1: cut pipeline (UNBORN, 13 components).
  • TYPE_3_HUMAN_IN_LOOP = 2: WF-001 (active, 10 steps), WF-002 (draft, 60 steps).

The joint map (11 classified relations — the live view)

topic (IU) process cluster (members) relation_class evidence
knowledge_graph (10) KG_DOT_CLUSTER (18) SHARED_IU+DOMAIN IU 10649925 = KG-law #7-36-dot-kg; 18 dot-kg DOTs implement it
knowledge_graph (10) APPROVAL_WF (14) INFERRED KG promotion (AXR-TOPIC-03/14) routes via approval_requests
knowledge_graph (10) CUT_PIPELINE (13) SHARED_IU render_pipeline IU 620f7646 is also a KG IU
architecture (5) KG_DOT_CLUSTER (18) INFERRED KG-law arch sections describe DOT/KG architecture
dot_trigger (3) KG_DOT_CLUSTER (18) SHARED_IU+DOMAIN IU 10649925 dot-kg section; trigger semantics
dot_trigger (3) TAC_DOT_CLUSTER (15) SHARED_DOMAIN DOT trigger cron/event/on-deploy
governance (3) APPROVAL_WF (14) SHARED_DOMAIN governance ↔ approval/birth-gate workflow
workflow (2) CUT_PIPELINE (13) SHARED_IU+NAME workflow IU d933ec87 shared with cut_pipeline; Type-2
workflow (2) WF_HUMAN (2) SHARED_DOMAIN workflow ↔ WF-001/WF-002
cut_pipeline (1) CUT_PIPELINE (13) DIRECT_NAME_MATCH topic label == process name
render_pipeline (1) CUT_PIPELINE (13) SIBLING_TOKEN shares token pipeline; no render process object exists (gap)

Relation-strength legend

DIRECT_NAME_MATCH > SHARED_IU+NAME/DOMAIN > SHARED_IU > SHARED_DOMAIN > INFERRED > SIBLING_TOKEN > NO_EVIDENCE.

Overlaps surfaced

  • Topics that process-link to cut_pipeline: cut_pipeline (direct), workflow (shared IU d933ec87), render_pipeline (sibling token), knowledge_graph (shared IU 620f7646).
  • Topics → workflow/queue/approval/RP: workflow→WF_HUMAN; governance+knowledge_graph→APPROVAL_WF; (RP-aggregation pilot has no topic IU — it is a pure infra process, INFERRED only).
  • IUs shared topic↔process: the single strongest cross-axis IU is 10649925 (KG-law #7-36-dot-kg) carried by both knowledge_graph and dot_trigger topics and describing the dot-kg process cluster.
  • Documents that anchor topic↔process relation: exactly one — dieu39-knowledge-graph-law.md. It is simultaneously the source of all 7 topics and the specification of the 18 dot-kg processes. It is the natural anchor document for the pilot.

Gaps (no-evidence / missing object)

  • render_pipeline topic has no process object (no PIPELINE:render, no render DOT). Either fold into knowledge_graph or create the process later.
  • RP aggregation, queue refresh pilots have no topic IU — they are infra processes invisible to the content axis. Acceptable: not every process is content-bearing.
  • architecture topic → all process links are INFERRED (cross-cutting, no direct IU↔process tie).
Back to Knowledge Hub knowledge/dev/reports/architecture/information-piece-content-work-on-topic-process-surfaces-2026-06-04/02-joint-topic-process-inventory.md