# Evals — finance-ops

Run the cases in `cases.yaml` against the skill. For each `should_trigger` prompt, confirm finance-ops activates and heads for the right one of its four jobs (forecast / reconcile / categorize / close); the non-obvious ones (the rolling-balance symptom, the "Other expenses" dump) and the Catalan/Spanish phrasings are the ones worth watching. For each `should_not_trigger` prompt, confirm the skill *declines* and routes to the named sibling — posting entries goes to `bookkeeping`, invoices/dunning to `invoicing`, the fundraising model to `financial-model`, CAC/LTV to `unit-economics`. The `capability` case is graded against its `must_include` rubric by hand or by an LLM judge. Separately, `scripts/verify.sh <dir>` validates the *emitted artifacts* (forecast CSV, reconciliation report, close checklist) for shape and rolling continuity — that columns exist, `ending_cash` rolls into the next `starting_cash`, every bank line is classified with no orphans, and every close gate is present and marked — not whether the dollar figures themselves are correct. It is read-only and exits 0 on an empty or clean target.
