Flow
A flow is the unit SwiftTune composes and deploys: a directed graph of blocks whose connections carry data from a trigger to a response. It is the whole application, not a step inside one — the graph, the configuration of every block in it, and the version history of both.
What it means
A flow describes what happens to a request, from the moment it arrives to the moment an answer goes back. Each node is a block with a job — call a model, search an index, write a blob — and each connection states that one block’s output feeds another’s input.
The graph must be acyclic and every connection must join compatible ports. Those two rules are checked before a version can be saved, which is what makes a flow reviewable as a plan rather than only observable as a running program.
How SwiftTune uses it
Editing happens on the composer canvas; saving stores a new immutable version of the graph. A deployment publishes one of those versions as a Cloudflare Worker, so the flow you reviewed is exactly the flow that answers on the URL, and the previous version stays available to roll back to.