Cases
Definition
Cases are the behavior situations Teammately uses for review, coverage, and benchmark results. 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.
- Use the integration guides for import schemas and export behavior.
Related objects
Cases should be read with Outputs, Case Versioning, Case Pool surface, and Benchmarks. Use Import and prepare cases when the next step is bringing source examples into Teammately.
Worked example
Cases boundary
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.
Middle
Judgment into standard
- Output
- The candidate answer is attached separately so reviewers know which behavior is being judged.
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.
