Module 01 Activity

Scenario

Someone on your team has proposed rebuilding an existing workflow as a graph. Before agreeing, you have to establish whether it needs one.

What you build

A structure decision for a real workflow you have access to, argued from the four-row table in Unit 04 rather than from preference.

Steps

1. Pick a workflow you actually run - a script, a scheduled job, an existing LLM pipeline. Write its steps as a numbered list.
2. For each step, state whether what happens next depends on a value computed at run time. Count how many do.
3. Sort the workflow into one of the four structures from Unit 04, and name the specific requirement that forces it above a plain function.
4. If it is a graph, count the transitions the way Unit 02 does, and state what you get in return for each one.
5. Write the decision as three sentences a colleague could disagree with.

Evidence to hand in

• The step list with the run-time-dependency column.
• The chosen structure and the requirement forcing it.
• The transition count and what it buys, if a graph.
• The three-sentence decision.

Review checklist

• Every step is marked for whether control flow depends on it.
• The forcing requirement is named specifically - a cycle, a pause, or a failure path - not 'it is complex'.
• Model calls are not counted as evidence of needing a graph.
• If the answer is 'a function', that is written down plainly rather than argued around.
• The transition count is reported if a graph was chosen.

Mark complete