> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datavibe.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Human review and audit

> Route reviewable output to people and preserve the decision chain.

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

1. The gate evaluates the completed outbound payload.
2. A hard violation returns `BLOCKED`.
3. Reviewable or workspace-required submissions return `QUEUED`.
4. A reviewer opens `review_url` and approves or rejects the item.
5. Your integration polls the action or receives the configured downstream
   signal before continuing.

<Warning>
  A hard `BLOCK` is never converted into a queue item. It is a mechanically
  enforced stop.
</Warning>

## 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.