Documentation
Managing Contradictions
Across a real project, documents disagree: an earlier board pack says one thing, a later model says another. LithicBlue finds where claims from your sources conflict and brings them to you to decide, rather than silently picking a winner.
Total Decisions
12
Awaiting Review
3
Validated
8
Overridden
1
Claim A
FY24 group revenue was £4.2bn
Sources:
Board Pack Q4 2024.pdf — 12 Jan 2025
AI chose this claim
Claim B
FY24 group revenue was £3.9bn
Sources:
Draft Financials v2.docx — 3 Nov 2024
AI Reasoning
Both figures describe FY24 group revenue. The board pack is the later, signed-off source and supersedes the earlier working draft, so its £4.2bn figure is trusted.
Where to find them
Open the project's Contradictions view. A stats bar across the top shows Total Decisions, Awaiting Review (highlighted when there's work to do), Validated and Overridden. You can also reach a specific conflict from a source file via its View contradictions action.
Two ways to work through them
- By Document: conflicts grouped into document pairs (File A vs File B), with an AI Summary and a side-by-side view. Accept the whole set with Validate All, or open Review Individual Claims.
- By Claim: each conflict on its own, showing Claim A and Claim B with their sources and the AI Reasoning for which one wins.
Use Show resolved to revisit ones you've already handled.
Validate or override
- If you agree with LithicBlue's decision, click Validate (or Validate All for a document pair).
- To decide differently, click Override. In the dialog choose Claim A wins, Claim B wins or No conflict (both are valid), add an optional note, and click Apply Override.
Document authority
Set authority levels on documents so that, when sources conflict, the more authoritative one is trusted to resolve the contradiction automatically: a later, signed-off model can outrank an early draft, for example.
Why it matters
Resolving contradictions keeps every downstream claim consistent, so a figure that was superseded by a more authoritative source won't quietly resurface in a deliverable.