Teammately Docs
Docs menu

reference

Outputs

Distinguish managed Run responses, imported output-only Runs, and Case-scoped reference outputs.

Outputs

Understand the outputs Teammately reviews, compares, and turns into correctness evidence.

Definition

An output is response evidence associated with a Case, but its identity depends on the workflow that produced it. A managed Evaluation Run generates a response from a saved Harness Version. An imported output-only Run maps externally produced responses to immutable Case IDs. A Case may also expose a golden or reference response where the current surface supports it.

Do not collapse these into one generic “accepted output” lifecycle. Imported outputs are not Harness Versions, Run responses are not automatically reference answers, and reviewer comments are not outputs.

Fields, states, or lifecycle rules

  • A managed Run response is bound to the Run, saved Harness Version, Benchmark Version, and Case.
  • An imported output-only Run joins external rows to immutable Case IDs and retains imported candidate metadata.
  • Output-only Runs can be scored and inspected, but cannot be activated, optimized in Improve, or used as Harness columns in Compare or Arena.
  • A golden or reference output is Case-scoped example evidence where exposed; it does not become a global Policy.
  • Mapping errors can make evidence misleading even when the external response data is unchanged.
  • This page documents object boundaries, not model execution, provider behavior, or public output schemas.

Read outputs with Cases, Reference and golden outputs, Run an evaluation, and Map external outputs.

Worked example

Target model outputs boundary

01

Start

Behavior input

Case
A user asks whether a product is compatible with equipment they own.
02

Middle

Judgment into standard

Candidate output
The assistant says the product will work.
03

Result

Interpretation

Interpretation
The benchmark failure belongs to the candidate output, but the reviewer still needs the case context and applicable rubric to explain why it failed.

Source confidence

Code-backed: Benchmark Dataset output mapping and Evaluation Run detail distinguish imported output-only evidence from managed Run responses; review and Case-content sources preserve the Case boundary. Provider execution and customer serialization are outside this reference.

Related task pages

Task / Benchmark EvaluationsRun a Benchmark EvaluationLaunch exact active Harness Versions against an immutable Benchmark Version as standard or repeated Run Groups.Task / Benchmark EvaluationsMap External Evaluation OutputsImport reference outputs, map them to immutable benchmark Cases and attempts, and inspect the resulting output-only Run.Task / Benchmark EvaluationsConnect Model OutputsMap externally produced outputs to immutable Benchmark Cases and create an output-only reference Run.Task / Benchmark EvaluationsInspect Evaluation ResultsTrace Dashboard and List signals to Run, Case, Policy, Rubric, completeness, and telemetry evidence.

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. Benchmark Evaluations Map External Evaluation Outputs Import reference outputs, map them to immutable benchmark Cases and attempts, and inspect the resulting output-only Run. Object Model Reference and golden outputs Understand Case-scoped example responses without treating them as generic approval state or candidate behavior.
AI context