Design flow logic in Designer

Open Designer

Signed-in navigation: Build opens Builder (/builder). One flow is one Blueprint. Check and Design are available without a paid plan. Compile and Runs require the paid runtime entitlement (Deploy + Operate, or the plan that unlocks Start Run).

Build the Blueprint

1. Name the flow. The compile record keeps Blueprint version lineage; a Run always names the Blueprint version that produced it.
2. Add stages in order. The compiled package projects those stages onto GitHub as a state machine.
3. Mark human gates where a person must decide. Each human stage becomes a Human Review Task at runtime (functional, code, or release).
4. Open Builder settings — not sibling apps — for Governance, Artifacts, Verification, Product, Connections, and Environments.
5. Resolve every principal. Placeholders such as @code-owner are not principals. Empty production reviewers block an enforced package.

Validate before compile

Use Validate and Simulate on the canvas. Compile evaluates contracts for authority, artifacts, verification, connections, and environments. A Compiled Workflow exists only after those checks pass.

Compile fails closed when:

• a human gate has no resolved reviewer
• a required artifact contract is missing
• a connection or environment is undeclared
• the account is not entitled to compile

Hand-off

A successful compile is the only path to a Run. Next: export the GitHub package, then install it in the bound repository. See the Quickstart and Installing the compiled package in your repository.