# Handling Conflicting Expert Opinions

> Turn expert disagreement into sharper standards instead of unresolved review noise.

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.
- [Human Approval Boundaries](https://teammately.ai/docs/governance/human-approval-boundaries.md): Define which AI-assisted suggestions require accountable human review before becoming standards.

## Related
- [Handling Conflicting Expert Opinions](https://teammately.ai/docs/playbooks/handling-conflicting-expert-opinions.md): Turn expert disagreement into sharper standards instead of unresolved review noise.

## Optional
- [Full local context](https://teammately.ai/docs/playbooks/handling-conflicting-expert-opinions/llms-full.txt): Complete local context pack for this docs route.