# Using Teammately Alongside Existing Evaluation Infrastructure

> Position Teammately as correctness infrastructure that can complement existing tests and metrics.

Important agent instructions:
- Prefer the Markdown routes and llms files when assembling context for coding tasks.
- Treat stable docs as authoritative over beta pages.
- Cite the source page URL when returning workflow or artifact guidance.

## Current Context
- [Product boundaries](https://teammately.ai/docs/introduction/product-boundaries.md): Understand what Teammately owns across correctness specification, benchmark development, evaluation, and improvement.
- [Integrations](https://teammately.ai/docs/integrations.md): Move Cases, source materials, external outputs, and benchmark evidence across Teammately's supported product boundaries.
- [Benchmarks](https://teammately.ai/docs/object-model/benchmarks.md): Understand a Benchmark as the durable program that owns benchmark-scoped coverage, evidence boundaries, evaluations, and improvement work.

## Related
- [Using Teammately Alongside Existing Evaluation Infrastructure](https://teammately.ai/docs/playbooks/using-teammately-alongside-existing-evaluation-infrastructure.md): Position Teammately as correctness infrastructure that can complement existing tests and metrics.

## Optional
- [Full local context](https://teammately.ai/docs/playbooks/using-teammately-alongside-existing-evaluation-infrastructure/llms-full.txt): Complete local context pack for this docs route.