Every team works differently. Define your states, draw the transitions, and see your workflow take shape.
States are the statuses your tickets can be in. Mark them terminal when they are end states. One state is the default — where new tickets start.
Transitions are the allowed moves. Each one has an actor type:
The diagram builds itself as you configure. Purple animated edges are bot paths. Blue edges are human-only. If a terminal state has no bot path leading to it, the ⚠ warning tells you — that is a human checkpoint.
This is how OpenWeave handles execution governance. The state machine is workspace-level config — no code, no deploys. Admins draw the lines, bots follow them.