Flows and versions
One flow is one Blueprint. Each compile creates a version. Runs keep the version they started with.
Last updated September 27, 2026
Flow
A flow is the Blueprint you edit in Build. Check and Design allow one flow free. Unlimited flows require Deploy or Deploy + Operate.
Do not split one product path across multiple flows unless the bound repositories are different. Start Run is flow-scoped. The Run list empty state is: this flow has never been dispatched.
Version
Compile writes a Blueprint version. Export packages that version. A Run records the version that produced it.
Editing the canvas does not change GitHub or an open Run. Re-compile, re-export, and re-install to publish a new version. See Re-export when the flow changes.
What stays on the old version
- Open Runs
- Human Review Tasks tied to a candidate SHA from that Run
- Native PR approval on that SHA
A new version needs a new install and a new Start Run. Approval on a previous SHA does not satisfy merge for a new SHA.
Lineage
Compile also records artifact lineage for that version. Do not delete or rewrite generated lineage files to make two versions look like one. If the graph is wrong, change the Blueprint and compile again.