Module 08 Summary

What this module established

Streaming node completions is the cheapest available improvement to how a long workflow feels, and it turns a hang into something visible. Stream steps for workflows and tokens for answers - streaming tokens for a six-node run is worse than not streaming, because the user takes the first node's output for the answer.

Carry forward

• Map node names to human labels in one dictionary and always show the position in the sequence. Both are static text; neither needs a model.
• Cancellation is cooperative - a flag checked at the top of every node, before any effect. Killing the process leaves state and external systems in an unknown condition.
• Per-node time budgets are what separate a hung run from a slow one. One global timeout is too coarse to detect anything.

Before moving on

Move on when a user-visible progress line shows labelled steps with positions, a mid-run cancel leaves consistent state, and every node has a time budget derived from observation.

Mark complete