# Evals — case-studies

These cases are run by the catalog harness or read by hand. `should_trigger` asserts that the description plus body would route a request to `case-studies` (including the non-obvious "reads like a brochure" symptom and the Spanish phrasing). `should_not_trigger` asserts that the named real sibling — `pitch-deck`, `article-writing`, `retention`, `review-management`, `brand-voice` — owns the request instead. `capability` is a rubric-scored generation: produce a case study from the brief and score it against the `must_include` list (results headline with a number, snapshot box, Challenge→Solution→Result spine, a baseline→result→timeframe metric line, a named attributed quote, a decision-stage CTA, a consent marker, 600–1,200 words, no banned superlatives). There is no bundled automated runner beyond `scripts/verify.sh`, which statically lints a generated case-study markdown for the structural and legal contract.
