Teammately Docs
Docs menu

reference

Cases

Understand cases as the situations Teammately uses to represent important AI behavior.

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.

Cases should be read with Outputs, Case versions, Case pool, and Benchmarks. Use Importing cases when the next step is bringing source examples into Teammately.

Worked example

Cases boundary

01

Start

Behavior input

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.
02

Middle

Judgment into standard

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

Result

Interpretation

Interpretation
If the candidate fails later, the run result can point to the exact case and output rather than to a vague transcript.

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

Concept / AssetsAssetsManage reusable project cases, worlds, project tools, harnesses, weights, comparison directions, and review screens before selecting them for benchmark work.Concept / Coverage EngineeringCase PoolUse the Case Pool to collect, triage, enrich, and promote candidate cases.Reference / Object ModelCase Pool surfaceUnderstand Case Pool as the Assets view for reusable project Cases, candidates, and explicit Benchmark selection.Quickstart / Learning ManualProduct quickstartConfigure one project foundation, one benchmark slice, one expert contribution, one evaluation, and one evidence-backed improvement.Concept / Operating ManualTask indexRoute correctness work to the current project foundation, benchmark workspace, evaluation, or improvement surface.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Assets Cases Understand canonical project cases, their input and materials, and how they become members of benchmark datasets. Coverage Engineering Case Pool Use the Case Pool to collect, triage, enrich, and promote candidate cases. Object Model Case Pool surface Understand Case Pool as the Assets view for reusable project Cases, candidates, and explicit Benchmark selection.
AI context