Every team works differently. Define your states, configure the gates, and see your workflow take shape.
States are the statuses your tickets can be in. One state is the default — where new tickets start.
Gates control which states can transition to each state. If "Allowed from" is empty, tickets can move from any state. Otherwise, only specified states can transition in.
Access control can be added later with user restrictions — dashed amber edges indicate states with limited access.
The diagram builds itself as you configure. Gray edges show normal transitions. Dashed amber edges show restricted access.
This is how OpenWeave handles execution governance. The state machine is workspace-level config — no code, no deploys. Admins design the gates, teams follow them.