09 — Pilot Process Candidates

Five concrete candidates, live-evidenced. Selected pilot for future live registration: cut_pipeline (strongest evidence; materialised job rows; clear start/end; isolated blast radius). No active process registered (CANDIDATE only).

1. cut_pipeline — SELECTED (Type 2, fully automated)

• start: cut.request enqueued; end: cut.complete/cut.cleanup_checkpoint.
• components: 13 job_queue rows across cut.request/copy_to_staging/mark/cut/verify_*/complete/cleanup_checkpoint.
• DOTs/scripts: cut-pipeline operator; triggers: queue lease; queue/jobs: 7 queued stuck since 2026-05-26 (worker_enabled=false); events: system domain; IU/SOP: none (gap).
• owner/gov: OWNER_MISSING; birth: UNBORN; RP: PIV-342/344/347/350/353.
• health/SLA: WARN (stuck jobs; executor warn iu_outbound_default).

2. topic-axis candidate/approval pipeline (Type 2/3 hybrid, implicit)

• 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); DOTs: candidate scan; events: governance domain.
• owner/gov: GOV-COUNCIL (topic side); birth: assignments unborn by design; RP: PIV-320..332.

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).
• owner/gov: GOV-DOT execution; birth: cache-only (no business birth); RP: meta pivots.

4. queue refresh / job workflow (Type 2, dormant)

• start: worker tick; end: queue drained. Components: queue_heartbeat 3 + v_queue_health (substrate+worker DISABLED). Currently idle — no drainer. Owner: GOV-DOT.

5. approval workflow (Type 3, implicit, embedded in triggers)

• start: approval_requests insert; end: applied/rejected/expired. ⚠ action='add' auto-approves; insert births. Components: 225 approval_requests + apr triggers + apr_approvals. Owner: GOV-COUNCIL.

WF-001 / WF-002 (already governed Type 3 — the registered baseline)

WF-001 "duyệt công việc" (active, 10 steps, 1 human_checkpoint + 1 wait_for_event, TSK-004). WF-002 "xử lý đơn hàng xuất khẩu 60 bước" (draft). Both BORN; both lack IU-SOP/owner/health (gov-gap).

Pilot registration plan (owner-gated, NOT executed)

Promote cut_pipeline: (1) owner approves; (2) insert workflows row PRC/WF-003 type=2 automation_level=automatic start=cut.request end=cut.complete; (3) add job_workflow parent table + link existing job_queue rows via workflow_id; (4) bind IU-SOP; (5) assign GOV-MOW owner. Each step disclosed as additive + birth-aware.