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

# Concepts

> The five words you need to read the rest of these docs.

## Verdict

The decision ZeroDrift returns on a piece of content. There are four.

| Verdict      | Meaning                                      | Where you see it today                                                                                          |
| ------------ | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Pass**     | Compliant. Deliver as is.                    | `overall_status: "approved"`                                                                                    |
| **Fix**      | A compliant version exists. Deliver the fix. | `overall_status: "needs_changes"` plus a non-empty `fix.suggested_text`                                         |
| **Block**    | No compliant version exists. Do not deliver. | `overall_status: "do not send"`                                                                                 |
| **Escalate** | A human must decide.                         | Your code, when `fix.action` is `remove_or_escalate`, `suggested_text` is empty, or your policy requires review |

Every verdict is logged in Command and readable through the Activity endpoints for 30 days.

## Rulepack

A managed set of rules covering one regulatory area, built and maintained by ZeroDrift. You activate a rulepack in Policy and scope a call to it with `validation_scope.rulepacks`. See the [Rulepack Catalog](/api-reference/rulepacks).

## Policy (imported)

Your own rulebook, made enforceable. Upload a document or sync one from Notion, Linear, Confluence, or Google Drive. ZeroDrift extracts rules; you review and activate them; each import gets an `import_id` you can scope calls to. See [Import Policy](/api-reference/custom-policies/import-policy).

## Adapter

A policy-specific model trained in Training Studio on top of Anchor, from an activated import. Anchor handles regulations. Your adapter handles your policies. See [Train an Adapter](/guides/train-an-adapter).

## Sync and async

`mode` is required on every enforce request. `mode: "sync"` returns the verdict in the response when the job stays within the inline budget. On a completed sync call, read `overall_status` and `violations` from the nested `result` object. `mode: "async"` returns `202` with a `job_id` to poll. Best for long content and high volume. A sync call on long content falls back to async; the `mode` field in the response tells you which happened.