Persisted gate submissions carry an action_id and the immutable snapshot_id
used for evaluation. This makes a decision reproducible even after policy
configuration changes.
Review flow
- The gate evaluates the completed outbound payload.
- A hard violation returns
BLOCKED.
- Reviewable or workspace-required submissions return
QUEUED.
- A reviewer opens
review_url and approves or rejects the item.
- Your integration polls the action or receives the configured downstream
signal before continuing.
A hard BLOCK is never converted into a queue item. It is a mechanically
enforced stop.
Audit fields
Keep these identifiers with your campaign or CRM record:
action_id: the persisted submission identity.snapshot_id: the immutable governance configuration used.X-Request-Id: the request correlation identifier.idempotency_key: your stable retry identity.
The audit trail records the original policy decision and any human decision. It
does not silently mutate historical snapshots. 
