04 — Process Map by Candidate (Workstream C)

All 5 pilot process candidates as workflow/process packages. Live-evidenced. No active process registered, no process canonized, no workflow executed.

---

1. cut_pipeline (PIPELINE:cut) — TYPE_2_AUTOMATED_MULTI — SELECTED process pilot

• process_code: PIPELINE:cut (candidate; UNBORN — no workflows row).
• start: cut.request enqueued. end: cut.complete / cut.cleanup_checkpoint.
• components (13 job_queue rows, 8 step-kinds): request → copy_to_staging → mark → verify_mark → cut → verify_cut → complete → cleanup_checkpoint.
• DOT/script: cut-pipeline operator/worker. triggers: queue lease. queue/job/events: job_queue (system domain); 7 rows queued/stuck since 2026-05-26 16:xx; 6 succeeded 15:13–15:17 (an earlier full run); worker_enabled=false.
• IU/SOP/doc refs: none (gap). Closest content tie: topic cut_pipeline IU d933ec87 (= KG-law #6-10-quy-trinh) and topic workflow.
• related topics: cut_pipeline (DIRECT_NAME_MATCH), workflow (SHARED_IU), knowledge_graph (SHARED_IU 620f7646).
• health/status: WARN (stuck jobs, disabled worker).
• governance gap: OWNER_MISSING. birth/state gap: UNBORN; RP PIV-342/344/347/350/353.
• automation value: HIGH (materialised jobs, clear start/end, isolated blast radius).
• next action: content-map + candidate registration plan only (future owner-gated registration: insert workflows PRC/WF-003 type=2, add job_workflow parent linking the 13 jobs, bind IU-SOP, assign GOV-MOW). Not executed.

2. topic-axis candidate/approval pipeline — TYPE_2/3 hybrid (implicit)

• candidate_code: (implicit; no process object).
• start: topic candidate detected (iu_metadata_tag topic:*). end: owner approves taxonomy promotion.
• components: axis_assignment 25 → v_axis_topic_decision_queue 7 → 14 AXR-TOPIC approval_requests (pending). Human step = owner decision (Type-3 segment).
• DOT/script: candidate scan (this macro family). events: governance domain.
• IU/SOP/doc: the AXR-TOPIC rows themselves; KG-law as content source.
• related topics: ALL 7 (it is the meta-process over the topic axis). health: OK (inert human gate). gov: GOV-COUNCIL. birth: assignments unborn by design.
• automation value: MEDIUM (mostly human decisions). next action: content-map only; this is the governance pipeline draining AXR-TOPIC-*.

3. RP aggregation / pivot-update pipeline — TYPE_2 (implicit, trigger-chain)

• start: pivot_definitions change / refresh tick. end: meta_catalog + pivot_results refreshed.
• components: trg_pivot_def_refresh → refresh_meta_catalog + refresh_pivot_results; dot-pivot-update (staged, UNBORN, NOT registered).
• IU/SOP/doc: none (pure infra). related topics: none (no content IU) — INFERRED only.
• health: OK. gov: GOV-DOT execution. birth: cache-only (no business birth).
• automation value: MEDIUM (already trigger-automated; gap is the unborn dot-pivot-update tool). next action: defer — content-invisible infra; owner-gated dot-pivot-update registration is a separate track (see prior RP checkpoints).

4. queue refresh / job workflow — TYPE_2 (dormant)

• start: worker tick. end: queue drained.
• components: queue_heartbeat + v_queue_health (substrate present, worker DISABLED); currently no drainer → the cut_pipeline jobs are stuck for this reason.
• IU/SOP/doc: none. related topics: none. health: IDLE. gov: GOV-DOT.
• automation value: HIGH-leverage (un-sticks cut_pipeline) but out of content scope. next action: defer to operator/infra; note the dependency: pilot #1 cannot complete a live run until the worker is enabled.

5. approval workflow — TYPE_3 (implicit, trigger-embedded)

• start: approval_requests insert. end: applied / rejected / expired.
• ⚠ key behaviour: action='add' auto-approves (fn_auto_approve_add); every insert births. AI proposals must use action='review' (all 14 AXR-TOPIC rows correctly use review/modify, not add).
• components: 225 approval_requests + apr triggers + apr_approvals. related topics: governance (SHARED_DOMAIN), knowledge_graph (INFERRED).
• health: OK. gov: GOV-COUNCIL. birth: births on insert.
• automation value: MEDIUM. next action: content-map only; document the auto-approve hazard as an SOP (see doc 05 backlog).

---

Type-1 DOT-contained family (the 57 — context, not pilots)

Not in the 5 pilots but the largest process population and the strongest topic-tie: 18 dot-kg-* (KG quality/maintenance: completeness, consistency, constraint-check, converse/evict/explain/scope-verify, override/provenance-audit, priority/intent-recalc, self-learn, health, timeliness, validate, scaffold-validate, feedback, orphan), 15 TAC (schema/collection/role/birth gate ensure+verify), 4 COL (collection health/sync). Each is GOVERNED_NOT_BIRTH_TRACKED, DOT-owned (alias only), run via cron/event/dual/on-deploy. The 18 dot-kg DOTs are the process implementation of the knowledge_graph topic — the pilot convergence.

Cross-candidate summary

pilot	type	confidence	content tie	next action
cut_pipeline	2	STRONG	weak (1 borrowed IU)	candidate-registration plan (owner-gated)
topic-axis pipeline	2/3	STRONG	all 7 topics	content-map (meta-process)
RP aggregation	2	MODERATE	none	defer (infra)
queue refresh	2	MODERATE	none	defer (infra; unblocks #1)
approval workflow	3	MODERATE	governance	content-map + SOP