Ordered checks
A single fixed gate sequence declares the order. The engine groups it into phases without changing that order.
There is no gateway-health gate. Workflow launch permission is separate: a launch check decides whether a run may be created, while this engine judges each protected dispatch, inside an admitted run or on another dispatch surface such as chat or a factory.
Pass, block, and hold
- Pass: every applicable enforced check allowed the dispatch; the owning runner may continue.
- Block: the first enforced refusal ends this attempt; later applicable gates are recorded as skipped.
- Hold: the action is otherwise admissible but needs a human release; the owner creates or reuses an approval human task and parks durably.
not_applicable means a check was outside this path; skipped means an earlier refusal cut it off. Retries re-resolve mutable authority unless a durable contract explicitly freezes it.
See Approval lifecycle and Workflow execution.
Related
- Trust Fabric concepts: the gate sequence and the four rungs.
- Approvals and human tasks: what happens after a hold.
- Workflow execution: where a run’s dispatches meet the pipeline.

