Workflows Should Name the Owner of Each Risky Transition

Risky workflow transitions should have named ownership so escalation, rollback, and approval do not become ambiguous during failure.

Many workflows define what the next state is without defining who is responsible for moving the system there safely.

Name the owner for

• Approval-dependent transitions.
• Writes that can affect shared state.
• Escalation and rollback decisions.

Use the architecture guide, blackboard schema, and examples to assign ownership explicitly.