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

# Violations

> Define expected agent behavior and review evidence when it is not followed

An **SOP** is an expected rule for agent behavior. A **violation** means an
analyzed conversation did not follow that rule.

## Configure rules

Open **Violations** in the Agnost AI sidebar. Create rules that are specific enough
to evaluate from a conversation, for example:

* Confirm identity before exposing account information.
* State the cancellation policy before completing cancellation.
* Escalate when the user reports a safety issue.

Avoid rules that depend on information Agnost AI never receives.

## Review violations

For each rule, compare the number of violations with the number of analyzed
conversations. Open **Evidence** to read the supporting messages before treating a
match as a product issue.

<Note>
  A violation is a classified finding, not an enforcement action. Keep critical
  safety and authorization checks in application code.
</Note>

## Next steps

* [Conversations](/using-conversations): inspect the evidence behind a violation.
* [Alerts](/using-alerts): monitor important rules and thresholds.
* [Improvements](/using-improvements): turn repeated violations into agent changes.