# Detect and route stale correctness evidence

> Identify which current claims need review after Cases, standards, coverage, sources, or target behavior change.

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
- [Versioning and Staleness](https://teammately.ai/docs/governance/versioning-and-staleness.md): Know when correctness objects changed and when old evidence may need review.
- [Refresh coverage after product change](https://teammately.ai/docs/coverage-engineering/coverage-refresh.md): Reconcile coverage facets, Cases, benchmark membership, and Snapshots after the target system or its evidence changes.

## Related
- [Detect and route stale correctness evidence](https://teammately.ai/docs/governance/staleness-detection.md): Identify which current claims need review after Cases, standards, coverage, sources, or target behavior change.

## Optional
- [Full local context](https://teammately.ai/docs/governance/staleness-detection/llms-full.txt): Complete local context pack for this docs route.