Eval Harness Tutorial · Requirements
The standard's obligations our checks serve
Each built check declares, in its code, which obligations of the standard it helps meet. “Helps” matters: an obligation is met by a whole practice (a test set, a gate, monitoring), and our check is one piece of the evidence.
| Obligation | Must be true | Applies to | Checks that help |
|---|---|---|---|
| AAC-0006 | No leakage of PII, secrets or credentials | core | bedrock_guardrails, presidio_pii |
| AAC-0029 | Every claim is supported by retrieved context | A3, A6 | azure_groundedness, bedrock_guardrails, consistency, ragas_faithfulness |
| AAC-0043 | Escalation to a human works under load | A4 | decision_vs_should |
| AAC-0051 | Tool selection accuracy, including no-tool | A6 | deepeval_tool_correctness |
| AAC-0078 | Irreversible actions require approval | A9 | decision_vs_should |
| AAC-0110 | A claimed action is supported by that action's result | A6, A7, A9 | claim_needs_action |
requires_before and argument_limit declare none: they test
the business's own rules, so their requirements come only from the agent's spec.