# Low expert agreement

> Investigate disagreement as evidence about context, applicability, source authority, or unresolved product policy.

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
- [Resolve conflicting correctness evidence](https://teammately.ai/docs/governance/conflict-resolution.md): Reconcile disagreement without hiding the Cases, expert judgments, sources, or versions that produced it.
- [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.

## Related
- [Low expert agreement](https://teammately.ai/docs/troubleshooting/low-expert-agreement.md): Investigate disagreement as evidence about context, applicability, source authority, or unresolved product policy.

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