# Unclear Cases

> Repair Cases that informed reviewers cannot interpret consistently from the supplied input, context, and output identity.

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
- [Unclear Cases](https://teammately.ai/docs/troubleshooting/unclear-cases.md): Repair Cases that informed reviewers cannot interpret consistently from the supplied input, context, and output identity.
- [Cases](https://teammately.ai/docs/assets/cases.md): Understand canonical project cases, their input and materials, and how they become members of benchmark datasets.
- [Complete an Expert Contribution](https://teammately.ai/docs/expert-contributions/complete-contribution.md): Work through form, chat, interview, case-review, and checkpoint tasks while keeping specialist judgment attributable.
- [Boundary Cases](https://teammately.ai/docs/coverage-engineering/boundary-cases.md): Use edge and ambiguous cases to sharpen policies, applicability logic, and rubrics.

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