> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sphinx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve controversies

> Understand how Sphinx conveys unresolved conflicts to agents, review the evidence, and resolve disagreements when you are ready.

A **controversy** records a disagreement between sources. For example, a sales handbook might say customers can request a refund within 30 days, while a support policy says 14 days. Until someone confirms which policy applies, an agent should not confidently promise either refund window.

## Unresolved controversies are fine

You do not need to resolve every controversy before agents can use Sphinx. When relevant knowledge contains an unresolved controversy, Sphinx automatically conveys the conflicting claims and uncertainty to agents. This helps prevent hallucinations and lets agents express appropriately lower confidence instead of presenting one claim as settled fact.

In the refund example, an agent can explain that the sources disagree, describe both policies, and ask for confirmation before promising a refund. The disagreement remains useful context while your team investigates it.

Resolve a controversy when you have enough evidence to establish the correct rule or explain when each claim applies. It is fine to leave it unresolved when the answer is still uncertain.

## Before you start

Select your workspace and identify someone who can confirm the correct business rule. Have the authoritative source or decision available before submitting a resolution.

## Investigate the disagreement

1. Open **Controversies** from the sidebar. The default view shows **Open** and **Elevated** controversies; use the status filter to change the view.
2. Expand the controversy and read each competing claim.
3. Follow the page title to see the disagreement in context. Inspect its citations and **References** to understand the evidence.
4. Use **Copy link to this controversy** to obtain a direct link for the relevant knowledge owner.

## Provide a resolution

Under **Resolution options**, select an offered option if one matches the confirmed decision, or select **Write a resolution** to explain it yourself.

A useful resolution states:

* The correct definition or rule.
* Its scope, version, and effective date where relevant.
* Which source supports it and what happens to the competing claim.

For example, if the policy owner confirms that the 30-day refund window applies to annual plans and the 14-day window applies to monthly plans, state that distinction and cite the policy that establishes it. If one policy has replaced the other, specify the effective date and which rule it supersedes.

Click **Submit** to request the resolution. Follow any resulting update in **Ingest** and [Review Changes](https://docs.sphinx.ai/knowledge-base/review-changes.md), and check the affected page after the update is accepted.

## Prioritize or postpone

Use **Elevate controversy** to flag an issue for priority attention. To remove that priority flag, click **Return controversy to open**. The controversy stays open and unresolved; this does not resolve or dismiss the disagreement.

If you cannot decide yet, use **Defer** rather than guessing a resolution. Deferring does not supply a corrected business definition.

An item marked **Resolving** is already being processed. Check its **View ingest** link, when present, before submitting another update for the same issue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.