# e-signature evals

`cases.yaml` holds two kinds of checks. `should_trigger` and `should_not_trigger` are routing assertions for the skill's description: each prompt is matched against the catalog router and we confirm e-signature is (or is not) selected, with `should_not_trigger` naming the real sibling that should win instead. `capability` is a rubric-graded scenario: a model implements the described DocuSign integration and a grader (human or LLM) checks the produced code against the `must_include` list — JWT auth, sandbox base path, envelope with explicit status, HMAC webhook verification on the raw body, idempotency, retrieval of both the signed PDF and the audit trail, no hardcoded secrets, and a deliberate legal-tier choice. Run them through the catalog's standard eval harness; routing cases are automatic, the capability case is graded against a generated artifact (and `scripts/verify.sh` can pre-screen that artifact mechanically).
