Skip to main content
Trust Fabric evaluates current facts before protected work. The governance engine returns a recorded decision; the platform supplies current identity, role, permission, budget, policy, and approval facts for workflow, Convex-native, and procedure dispatch.

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.
A hold is not a soft pass. Completion rechecks the approval’s release policy before recording a decision. The release applies to the concrete governed attempt, not later calls. Policy clauses are parsed at authoring time against whitelisted facts. Exact targets use server-resolved identities, including a run’s persisted workflow version. External-delivery policy waits until the concrete operation is classified, then runs before credentials or effects. Every decision records gate outcomes, actor and role snapshots, applicable limits, and the first cause. 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.