# Tessary cases

A case is Tessary's unit of investigation. Classifiers produce findings, triage runs on those
findings, and the ones ruled real issues turn into cases, each with a lifecycle to open, work, and
resolve.

A case contains what moved, by how much, and since when, in the detector's own numbers. It carries
the triage ruling in prose, with a confidence and its citations, and says which lane ruled it: from
trace evidence alone, or grounded in the repository, where the citations are file paths you can
open. It also holds before and after exemplars, real traces from each side of the shift, so you can
see what the numbers look like in practice.

From a case, Tessary runs root cause analysis: an agentic session in a fresh E2B microVM over the
failing cohort, with the trace evidence, a dossier, and the connected repo. It returns grounded
hypotheses plus the checks it ruled out, cites the files involved, and raises a PR with the fix
after attribution.

## Questions answered under this concept

- [How do I verify an alert webhook actually came from Tessary?](https://tessary.ai/answers/tessary-cases/how-do-i-verify-an-alert-webhook-came-from-tessary)
- [What happens after the same failure keeps recurring?](https://tessary.ai/answers/tessary-cases/what-happens-when-a-recurring-failure-reopens-a-case)
- [What is a case?](https://tessary.ai/answers/tessary-cases/what-is-a-case)
- [When does a finding become a confirmed problem?](https://tessary.ai/answers/tessary-cases/when-does-a-finding-become-a-case)
- [Where can agent monitoring alerts be routed?](https://tessary.ai/answers/tessary-cases/where-can-agent-monitoring-alerts-be-routed)
- [Why do a hundred failing traces need to become one thing to look at?](https://tessary.ai/answers/tessary-cases/why-a-hundred-failing-traces-become-one-case)

---

Source: https://tessary.ai/answers/tessary-cases
All concepts: https://tessary.ai/answers
From Tessary, agent reliability for AI agents in production: https://tessary.ai
