---
id: object-model.cases
title: Cases
summary: Understand cases as the situations Teammately uses to represent important AI behavior.
kind: reference
product_area: object_model
status: stable
updated: 2026-08-23
canonical: /docs/object-model/cases
---

# Cases

## Definition

Cases are the behavior situations Teammately uses for review, coverage, and benchmark evidence. A case should preserve the input, source context, metadata, and version boundary needed to understand what behavior is being judged.

Use this reference when a workflow depends on whether an example is reviewable, benchmark-ready, stale, duplicated, or missing the context a reviewer needs.

## Fields, states, or lifecycle rules

- A case is not the same thing as an output; the case holds the situation and context, while the output is the behavior being judged.
- A case can be useful for coverage planning before it is ready for benchmark use.
- Case versions matter when source context, metadata, or expected behavior changes.
- A benchmark result is weak if the failed output cannot be traced back to the exact case version.
- Exact import schema and export behavior belong to source-backed integration pages, not this object reference.

## Related objects

Cases should be read with [Outputs](/docs/object-model/outputs), [Case versions](/docs/governance/case-versioning), [Case pool](/docs/object-model/case-pool), and [Benchmarks](/docs/object-model/benchmarks). Use [Importing cases](/docs/operating-manual/import-and-prepare-cases) when the next step is bringing source examples into Teammately.

{% example-demo title="Cases boundary" %}
Raw record: A transcript includes a customer question, assistant answer, account context, and later human correction.

Case: The reviewable unit preserves the customer question and account context.

Output: The candidate answer is attached separately so reviewers know which behavior is being judged.

Interpretation: If the candidate fails later, the run result can point to the exact case and output rather than to a vague transcript.
{% /example-demo %}

## Source confidence

Code-backed: Case view types and the Cases asset route establish the product object and its presentation; internal Case-content types establish how input and contextual material remain separate from outputs. These implementation sources support object semantics, not a customer-facing serialization contract.

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Case model overview](/docs/assets)
- [Case Pool](/docs/coverage-engineering/case-pool)
- [Case pool](/docs/object-model/case-pool)
- [Product quickstart](/docs/quickstart)
- [Task index](/docs/operating-manual/task-index)
{% /related-card-grid %}