06 — Workflow / MOW / MOT / MOIT Implications (Workstream E)

Mapping content/process discoveries to the 4 Mothers. Actionable, not generic. No Mother row written, no template selected, no event registered.

MOW (Mother of Workflows) — process canvas entries

process candidate	becomes MOW entry?	live substrate	missing substrate	draft rows/edges needed	risk	next action
cut_pipeline	YES (Type-2, strongest)	13 job_queue rows, 8 step-kinds	workflows row; job_workflow parent table; IU-SOP binding	1 workflows (PRC/WF-003); link 13 jobs via workflow_id	UNBORN birth on insert; worker disabled	owner-gated registration (doc 04 #1)
WF-001 / WF-002	already MOW	2 workflows rows (10+60 steps)	IU-SOP, owner, health	none	none	attach gov-gap fixes
topic-axis pipeline	partial (governance)	axis_assignment + approval_requests	—	none	—	keep as meta-process

• MOW home confirmed: AX-PROCESS is a lens, not the owner. Process ownership stays the MOW registry (Điều-34, Option-3 "not a 5th Mother").

MOT (Mother of Tasks) — task templates / JFT

process step source	becomes task template?	substrate	missing	next action
WF-001 10 steps (1 human_checkpoint + 1 wait_for_event, TSK-004)	YES (baseline)	task rows under WF-001	—	reference model for new templates
cut_pipeline 8 step-kinds	candidate MOT templates (request/copy/mark/verify/cut/complete/cleanup)	job_queue step-kinds	task_template rows	derive templates from step-kinds (owner-gated)
dot-kg-* 18 DOTs	each a single-step automated task	dot_tools	task↔DOT binding	bind via handled_by verb (AXR-TOPIC-13)

• MOT signal: the cut_pipeline's 8 distinct step-kinds are the most concrete task-template seed in the system.

MOIT (Mother of Improvements) — improvement inputs

content/process gap	becomes MOIT input?	route	next action
cut_pipeline 7 stuck jobs (worker disabled)	YES	improvement / approval_requests	log as operational improvement (doc 09 safe-issue)
render_pipeline topic with no process object	YES	improvement	resolve sibling (fold/defer)
approval action='add' auto-approve hazard	YES	improvement/SOP	document + guard proposal
dot-kg DOTs lack run-cadence/SLA docs	YES	improvement	D2 SOP backlog

• MOIT route note: improvements reference the topic via approval_requests (no separate engine). Use action='review' to avoid auto-approve births.

Document-template selection — which clusters need a template

cluster	template needed	consumer
KG cluster (D1/D2)	YES — KG document-template (queued AXR-TOPIC-14)	RP/docs render of the curated KG cluster
cut_pipeline (D3)	runbook template	MOW
governance (D4/D5)	review-packet + SOP template	GOV-COUNCIL

Event / staging inputs needed

• event_type_registry (45 live): reference, don't duplicate. cut_pipeline emits system-domain events; topic/approval pipelines emit governance-domain events.
• Staging: cut_pipeline already has a cut.copy_to_staging step — the only explicit staging in the process inventory. Reuse, don't invent.
• New event types needed: only if KG enrichment workflow (AXR-TOPIC-14) is registered — then topic.promoted, kg.enriched candidates. Defer until promotion.

Net 4-Mothers impact

• MOW: 1 concrete registration (cut_pipeline) — owner-gated, plan ready.
• MOT: 8 task-template seeds (cut step-kinds) + 18 DOT-task bindings — ready to derive.
• MOIT: 4 concrete improvement inputs — 1 safe to log now (stuck-jobs).
• Templates: 1 high-value (KG) queued AXR-TOPIC-14.
• Events: reuse 45 existing; no new types until promotion.