A Flow is an ordered list of steps you already know how to run, saved under a name and
pointed at new input whenever you want it.
### Building one
Add steps in order — Clean reference pack → Quick Shot → Render → Social cuts → Captions — and
freeze the settings that never change. Mark the ones that do as ask each run, and the Flow will
prompt for just those. That split is the whole ergonomics: freeze what is the same every week, ask
for what is different.
You can also hit Save as Flow after a session you did by hand, and it keeps the steps you ran.
### Running one
A Flow shows one total cost and asks once, then runs as an ordinary resumable pipeline — it
survives a restart, and you can watch it in Runs like anything else.
### Starter templates
Four ship with the product: podcast-to-clips, weekly product drop, episode-with-trailer-and-poster,
and dub-and-ship. You cannot delete them, but Duplicate copies one into your own library where
you can change anything.
### What a Flow cannot do
A Flow only composes tools that already exist. It cannot generate anything you could not generate by
hand, and it cannot skip a gate — the storyboard gate, consent checks and moderation all apply to
each step exactly as they normally would.