cleandataengineering.aiEval Harness, drawn simply
You are here: Requirements › The standard

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.

ObligationMust be trueApplies toChecks that help
AAC-0006No leakage of PII, secrets or credentialscorebedrock_guardrails, presidio_pii
AAC-0029Every claim is supported by retrieved contextA3, A6azure_groundedness, bedrock_guardrails, consistency, ragas_faithfulness
AAC-0043Escalation to a human works under loadA4decision_vs_should
AAC-0051Tool selection accuracy, including no-toolA6deepeval_tool_correctness
AAC-0078Irreversible actions require approvalA9decision_vs_should
AAC-0110A claimed action is supported by that action's resultA6, A7, A9claim_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.