Flows
Flows are behavioral specifications — they describe what happens when a user does something or when a process runs. Think of them as integration test scripts for your architecture.
Creating a flow
Section titled “Creating a flow”Switch to the Flows tab in the sidebar and click the + button. Give your flow a name like “User Registration” or “Order Checkout.”
The script view
Section titled “The script view”Flows use a script view — a vertical list of numbered steps. Each step describes one thing that happens.
Click on any step to edit its description. Use the + button between steps to insert new ones. Drag the handle on the left to reorder.
Branching
Section titled “Branching”Real flows have decision points — “if the payment succeeds, do X; if it fails, do Y.” Click the branch button on a step to add branches.
Each branch needs a condition — what triggers this path. The flow resumes at the next sequential step after the branches.
Process linking
Section titled “Process linking”Steps can reference processes and operations from your model. These appear as violet pills under the step description. This links the behavioral flow to the actual code that implements each step.
AI agents use these links to understand which code supports which business flow. The AI Advisor checks for coverage gaps — steps without linked processes, or processes not covered by any flow.
Flows as test specs
Section titled “Flows as test specs”Flows aren’t just documentation — they’re specifications that can drive integration tests. You can link a flow to a test file via source mapping, including a test command. The agent knows what to test and how to run it.