Supplier review v3 · run 01k7m2
- CompletedFind changes
- CompletedAssess risk
- CompletedCheck policy
- ApprovedDecide · reviewed by a specialist agent, then approved
- CompletedShare the report
Zero Flow
Follow the distinction between a flow definition, a released version and a run, then see how steps, branches and decision points organise an executable process.

01
Design
The flow: its steps, data, decisions, and order.
02
Release
A flow version: fixed, and callable on its own.
03
Run
One execution of that version, with a record of every step.
A flow is designed, a flow version is released, and a run is executed.
Write the process in plain language, and Zero Flow turns it into a flow.
Connect capabilities on a canvas, and see the process take shape.
Define the same flow directly, for teams that prefer to work in code.
A flow is the definition of a business process: its steps, data, decisions, and order. It can include agents, datasets, approvals, schedules, and other flow versions.
Releasing a flow produces a flow version, such as Supplier review v3. It fixes the defined steps and decisions for each run; a change to that definition produces a new version.
A run is one execution of a flow version. It can last seconds or days, it can wait for a decision and pick up where it stopped, and it keeps a record of every step.
Describe it in plain language, compose it on a canvas, or define it in code. All three produce the same flow.
A decision step directs work to the check, agent, or person authorised to decide. The run pauses for the answer and continues from the outcome.
The definition of a business process: its steps, data, decisions, and order.
A released flow with fixed steps and decision points. Each run follows that definition.
One capability, or one flow version, placed in a flow.
One execution of a flow version, with a record of every step.
Passing a decision to another agent or an authorised person when their assessment or authority is required.
Zero Flow is part of Zero, the agentic orchestration platform.