# Evals — decision-records

These cases are routing prompts plus one capability rubric; there is no automated runner here. To evaluate, read `cases.yaml` and judge by hand (or with an LLM grader): for each `should_trigger` prompt, confirm a router would reach for `decision-records`; for each `should_not_trigger`, confirm it routes to the named sibling instead and not here. For the `capability` case, have the model produce the ADR end to end and check it against every bullet in `must_include` — a numbered/dated file, problem-framed context, ≥2 compared options, an explicit decision, two-directional consequences, an index row, and correct supersession if a prior decision is replaced. A produced ADR file can additionally be linted mechanically with `../scripts/verify.sh <path-to-adr.md | decisions-dir>`, which checks status, date, required sections, ≥2 options, and filename convention.
