# Input Coverage Inbox

> Review attributable input-coverage findings and decide whether to generate, add, remove, or decline Cases.

Important agent instructions:
- Prefer the Markdown routes and llms files when assembling context for coding tasks.
- Use public docs for product capabilities and workflow guidance.
- Cite the source page URL when returning workflow or artifact guidance.

## Current Context
- [Coverage Design](https://teammately.ai/docs/coverage-design.md): Use Canvas to define required input coverage and Inbox to decide how new findings affect benchmark membership.
- [Contributed Artifacts](https://teammately.ai/docs/expert-contributions/contributed-artifacts.md): Inspect Policy and Rubric contributions and coverage observations while retaining expert provenance and separate adoption decisions.
- [Benchmark Dataset Cases](https://teammately.ai/docs/benchmark-datasets/cases.md): Inspect benchmark Case membership, coverage traces, references, and scoped bulk actions.
- [Unbalanced Coverage](https://teammately.ai/docs/troubleshooting/unbalanced-coverage.md): Fix benchmarks that overrepresent easy or common cases while missing important behavior.

## Related
- [Input Coverage Inbox](https://teammately.ai/docs/coverage-design/inbox.md): Review attributable input-coverage findings and decide whether to generate, add, remove, or decline Cases.

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