Branch I — First Pilot Scenario: WF-001

Goal: take one existing workflow, bind its design to IU refs in draft/proposal mode, view it in the UI data contract, validate it — no runtime.

---

1. Candidate selection criteria & choice

Criterion	WF-001	WF-002
status	active	draft
step count	10 (manageable)	60
has BPMN narrative (design IU source)	yes (7993 chars)	no (bpmn_len 0)
has structured config / triggers	yes (10/10)	no
relations (DAG)	present	present

Selected: WF-001 "Quy trình duyệt công việc" — active, small (10 steps), rich design source (BPMN + config + triggers), exercises every binding type (design IU, step IU, guide IU, dot_ref, event refs, condition_iu_ref). WF-002 is the scale follow-on.

2. Data needed

• WF-001 header (id=1, process_code WF-001, v4, category 3).
• 10 steps (ids 6–15): types wait_for_event/human_checkpoint/agent_call/condition/action; config holds source_bpmn_id, role, reviewer, condition, result.
• Step relations for the DAG (subset of the 80).
• Source for design IU: workflows.bpmn_xml (WF-001).
• Owner: GOV-MOW.

3. DOT sequence (all design-only; mutating ones via proposal→approval)

1. dot_mow_design_get(1)                      -- baseline read
2. dot_mow_design_propose_change(1, 'bind_owner', {owner_gov_code:'GOV-MOW'})
3. [human approve ≥2]  dot_mow_design_bind_iu(1, <design_iu_uuid>)   -- mint design IU from BPMN first
4. dot_mow_design_bind_step_iu(step_id, <step_iu_uuid>[, guide_iu]) -- ×10 (batch B1, doc 05)
5. dot_mow_design_bind_dot(step_id, <command_name>)     -- where a DOT applies (e.g. agent_call→a DOT)
6. dot_mow_design_bind_event(step_id, <domain>, <type>) -- for wait_for_event steps
7. dot_mow_design_validate(1)                  -- expect GREEN after full binding
8. dot_mow_design_render_tree(1)               -- DAG for UI Surface 2
9. [council] dot_mow_design_activate(1, version=5, apr_id) -- only if validation GREEN + ≥2 signs
10. dot_mow_design_audit(1)                     -- evidence trail

Owner set + version bump go through the proposal/approval flow (doc 07). Binds are MOW-owner; activation is council.

4. Expected evidence

• v_mow_design_workflow row for id=1: owner_gov_code='GOV-MOW', bound_step_count=10, step_count=10, light=GREEN.
• v_mow_design_step: all 10 is_iu_bound=true; dot_ref/event refs resolve.
• Validation harness (doc 06 §5): WF-001 → GREEN; dangling sweep all 0.
• Governance: ≥2 apr_approvals for the activation request; dot_mow_design_audit shows propose→approve→activate.
• UI Surfaces 1/2 render WF-001 GREEN with drill-down to IUs.

5. Rollback

• Pre-activation: un-bind via dot_mow_design_bind_* set NULL; minted IUs soft-retired (Điều 30).
• Post-activation: dot_mow_design_rollback(1, to_version=4, apr_id) forward-only version-pin to the pre-pilot design; freeze if unsafe.
• Whole pilot is reversible without data loss; legacy inline columns untouched until VALIDATE.

6. Pilot scenario verdict

Ready. WF-001 selected with rationale, data identified, full DOT sequence, expected evidence, and rollback specified. Exercises every Phase 1 binding/validation/governance path without any runtime.