Development
v5 · draft- Edited today
- Not callable by Production keys
The whole path, drawn where the team can read it.
Put agents, tools, branches and a human review on one canvas. Try the draft with real input, release a version, and point each environment at it.
Draft to release
Three environments. A release never changes after it is made.
Callers reach a deployment, and a deployment points at one release. Moving Production forward is a deliberate step, not a side effect of saving the canvas.
Staging
v4 · release- Released, and fixed from then on
- Evaluations attached to the version
Production
v3 · release- Moved forward on purpose
- Allowlisted for the service keys that may call it
Review requested
run_8f2c…
Illustrative
- Workflow
- Inbound email · v3
- Step
- Lead review
- Proposed action
- linear.create_issue · priority urgent
- Eligible
- Members with the reviewer role
Human in the path
Pause for a person where a person should decide.
Add a review step before anything irreversible. The run waits with its state visible, only an eligible member can continue it, and the decision stays attached to the run.
Your first workflow
Draw it, try it, release it, watch it.
-
Draw the path
Drop a trigger, the agents and tools it needs, and a branch for the cases that differ.
-
Try it with real input
Run the draft in Development and read every step in the trace before anyone depends on it.
-
Evaluate, then release
Score the version on saved examples and release it. The released version is fixed.
-
Deploy and watch
Point Production at the release, then follow runs, cost and failures as they happen.
Keep reading
Draw the path your product depends on.
Start from a template or an empty canvas, try it with real input, then release it.