11 — Topic-Axis & Information-Work Integration

One mechanism, two axes

AX-PROCESS and AX-TOPIC are sibling rows in the same axis_registry, sharing the generic mechanism (node_source + relation_source + lifecycle_field + substrate_resolver + pivots_ref). No topic-axis progress is lost; AX-PROCESS is purely additive (axis_registry 1→2, AX-TOPIC untouched: still CANDIDATE, 25 assignments/7 nodes, PIV-310..332 intact).

Cross-axis relations (how process meets topic/IU)

• topic → process: a topic node tags the workflows/DOTs that implement it (future axis_assignment rows AX-TOPIC target_type='workflow'/'dot_tool' — today PIV-327/328 = DEFER_NO_SOURCE, 0; they become computable once these edges exist).
• process → IU: each workflow step should bind an IU (SOP/narrative) — currently 0 IU-binding columns (the Doc-04 gap); fn_process_node_substrate.iu_sop_ref=null surfaces it.
• process → document: IU/SOP docs in knowledge_documents (PIV-310 = 5,737).
• process → workflow/task: workflows↔tasks via task_id; steps↔checkpoints via workflow_step_id.
• process → DOT/event: steps reference DOTs (config jsonb) + event_type_registry (45) routing.

Edge substrate (planned, not wired)

universal_edges already exists (2,199 edges). Topic↔workflow / topic↔DOT / process↔IU edges are architecturally mapped but not populated (matches doc-08 four-mothers "honest status"). Populating them is owner-gated edge work, not part of this pilot.

Effect on the content map

With both AX-TOPIC and AX-PROCESS live, the information-piece content macro can now map a piece along two governed axes:

• which topic it belongs to (AX-TOPIC, 7 candidate nodes, knowledge_graph hub 10 IU), and
• which process produces/consumes it (AX-PROCESS, e.g. an SOP IU bound to a workflow step, or a cut-pipeline output). This upgrades the content map from "topic-only" to "topic × process" — a piece is no longer just about something, it is produced by / used in a process.

Roadmap integration (one track, not two)

• AX-TOPIC and AX-PROCESS advance in parallel under one RP surface.
• Next content work consumes both surfaces (see 12): it does not need to wait for process-axis ratification, because the candidate surfaces are already queryable read-only.
• Owner decisions (FAC-08 roots for topic; Điều-XX + GOV-MOW for process) drain in parallel via their respective gap/queue surfaces.