Workflow authoring

Start from a trigger: an API request, an event, a schedule, a webhook, or a person. Then describe every state transition that matters. A good workflow makes its waits, branches, owners, and actions visible before it runs.

For each step, decide:

• What input it accepts and output it produces.
• Whether retrying it is safe.
• Which identity and permissions it uses.
• How long it may run or wait.
• What evidence an operator needs when it fails.

Author a draft, run it against representative inputs, then promote the immutable version that passed review.