Example
Rebuild the graph from what was written
Every write is enough on its own to say what the graph is: replay them anywhere and you get the graph Flow serves, and the same answer about what is next.
12 steps, driven by an agent. Every step is a step in an end-to-end test, run against a listening server on every pull request, so the graph moves the way the run moved it.
Why it is shaped this way
The console draws the graph in a browser, with the same package the server computes it with, and the documentation draws each flow by replaying the calls it made. That only means something if the two computations agree. So this flow writes a small feature the ordinary way — pieces filed in one call, a decision holding one of them, a spec cited, work closed with its outcome, a bug triaged from the inbox, an edge and a reference withdrawn — then folds every write it made back into a graph from nothing, and holds it against the one the server derives from its own rows: the same tasks in the same states, the same edges, the same open waits and references, the same order and the same readiness. A meaning that survives only inside one interface is a meaning that can be lost.