Contradictory company documents require an authority decision, not a confident blend. Establish whether the sources address the same product, date, audience, and condition before deciding which one governs the answer.
Document conflict is contextual
A knowledge conflict occurs when applicable claims cannot all hold under the same conditions. A regular schedule and a holiday exception may be compatible once scope is clear; two current policies with incompatible eligibility rules may require owner review.
For a proposed source model, retain owner, effective version, status, audience, relevant scope, and supersession relationships. Use the approved precedence policy rather than whichever document ranks highest for the query.
Do not treat document recency as universal authority. A recently edited draft may be less authoritative than an older approved policy. Likewise, a title containing “official” is not a trusted permission or governance signal by itself.
Resolve a fictional expense-policy disagreement
One document says a category is reimbursable, while another says it requires manager review. The assistant first checks whether one applies to a different region or effective period. If both apply and conflict, it should surface the unresolved condition and route to the policy owner.
Averaging the rules or choosing the more generous option would invent a policy. The final answer should distinguish verified general context from the unresolved eligibility decision.
| Source relationship | Expected handling |
|---|---|
| Current policy supersedes old copy | Current authority governs |
| General rule and valid exception | Apply the scoped exception |
| Draft versus approved policy | Respect publication status |
| Different region or product | Align scope before comparing |
| Genuine unresolved contradiction | Qualified answer and owner review |
Build fixtures for true contradictions and apparent conflicts that disappear after scope alignment. Evaluate both missed conflicts and unnecessary escalation.
Repair the knowledge base after resolution
The policy owner should approve the corrected source relationship or content. Update index metadata and regression fixtures so the same conflict does not recur indefinitely. Preserve relevant history under the actual records policy.
Conflict handling adds latency and may frustrate users seeking a quick answer. It is still preferable to inventing certainty where company guidance disagrees. Keep the explanation concise and provide a usable route to the responsible owner.
This conflict process is proposed. The voice integration case study describes knowledge retrieval work. Pair it with agent-answer conflict detection, which addresses a later interpretation boundary.
Contradictory document FAQ
Should the newest file always win?
No. Approved authority, scope, and effective status matter.
Can the assistant merge both answers?
Only when they are compatible under explicit conditions. Do not blend incompatible business rules.
What should the user receive during uncertainty?
Supported context, a clear limit on the unresolved claim, and the approved next step for policy clarification.