---
id: playbooks.alongside-existing-evals
title: Using Teammately Alongside Existing Evaluation Infrastructure
summary: Position Teammately as correctness infrastructure that can complement existing tests and metrics.
kind: recipe
product_area: playbooks
status: stable
updated: 2026-09-07
canonical: /docs/playbooks/using-teammately-alongside-existing-evaluation-infrastructure
---

# Using Teammately Alongside Existing Evaluation Infrastructure

Use this playbook when a team already has tests, traces, dashboards, or offline evals and wants Teammately to add expert-grounded correctness evidence rather than replace everything.

## Choose the integration boundary

Use this when existing infrastructure already owns candidate execution, CI status, traces, or metrics and the team wants Teammately to own deliberate coverage, expert-grounded standards, and Benchmark evidence. Keep external systems authoritative for facts Teammately does not ingest or compute.

## Two supported evidence paths

1. Inventory the external Case identity, candidate identity, metrics, CI status, and links needed by customer operators.
2. Import representative inputs as Teammately Cases and design their coverage and governed evaluator boundary.
3. For a candidate Teammately can execute, save it as a Harness Version and create a managed Run.
4. For responses produced externally, export immutable Teammately Case IDs, generate one response per intended Case, and map them into an output-only Run.
5. Store useful external candidate or run identifiers in the configured Run Metadata fields. Do not claim Teammately verified an external metric merely because its identifier is present.
6. Inspect Teammately Rubric evidence in List. Use Compare and Arena only for saved Harness Versions; output-only Runs are not Harness columns.
7. In customer-owned human review context, present Teammately evidence and external CI or telemetry as separately sourced facts.

## Ownership matrix

| Evidence | Owning system |
| --- | --- |
| Coverage Facets, Policies, Rubrics, Benchmark Versions | Teammately |
| Managed Harness response and Rubric outcomes | Teammately Run |
| Imported response mapping and Rubric outcomes | Teammately output-only Run |
| External latency, CI status, trace, or deployment fact | External system |
| Downstream operational decision | Customer |

{% example-demo title="CI benchmark handoff" %}
A team keeps latency and regression tests in CI. It exports Teammately Case IDs, produces candidate responses externally, and imports them as one output-only Run with the CI run ID in Run Metadata. Teammately reports must-level Policy failures for those responses; CI remains authoritative for latency. The customer's review context shows both facts with their sources and does not treat the imported candidate as a saved Harness Version.
{% /example-demo %}

## Evidence to collect

- External eval artifacts and the identifiers needed to trace candidates or runs.
- The Teammately-owned Cases, standards, coverage, Benchmark Version, output mapping, Rubric evidence, and Run Metadata.
- Mapping notes that explain which metrics remain outside Teammately.
- Benchmark comparisons under approved human standards.
- Review context that keeps external CI status separate from Teammately benchmark evidence.

## Related docs

{% related-card-grid title="Related docs" %}
- [Map external outputs](/docs/benchmark-evaluations/output-mapping)
- [Configure Run Metadata](/docs/benchmark-evaluations/run-metadata)
- [Compare Harness Versions](/docs/benchmark-evaluations/compare)
- [Read run results](/docs/benchmark-evaluations/inspect-results)
- [Run a benchmark](/docs/benchmark-evaluations/run-evaluation)
- [Importing cases](/docs/operating-manual/import-and-prepare-cases)
- [Agent Setup](/docs/agent-setup)
{% /related-card-grid %}

## Source confidence

Doctrine-backed: the approved product boundary keeps Teammately correctness evidence separate from external infrastructure facts and customer decisions. Linked code-backed pages define managed Runs, output-only Runs, Run Metadata, and comparison eligibility.