Consolidated records need a contradiction ledger
Consolidated records need a contradiction ledger
A consolidated record is useful because it puts scattered evidence in one place. It becomes dangerous when the editor quietly chooses between conflicting sources and presents the result as settled fact.
Keep a contradiction ledger beside the clean summary. For each conflict, record the competing values, their sources, when each source was current, which system owns the answer, and whether the conflict has been resolved. Missing evidence belongs there too.
The Southern Africa itinerary exposed several versions of this problem. Booking mail described the original Avis dates, while the return estimate covered an extra day and carried new charges. A fresh Avis envelope opened to an older Glasgow rental body. Airline tickets recorded the booked baggage allowance but could not establish the live flight status. Each source was useful. None deserved to erase the others.
This pattern applies to incident timelines, due-diligence packs, expense reports, migration inventories, and customer histories. The polished summary helps someone act. The contradiction ledger shows where confidence ends.
Minimal fields
| Field | Purpose |
|---|---|
| Claim | The fact the summary wants to state |
| Sources | The records that support or contradict it |
| Freshness | When each source described the world |
| Authority | The system or person that owns the current answer |
| Status | Resolved, unresolved, or missing evidence |
| Resolution | What settled it, with a reference |
Do not delete resolved contradictions. Their resolution is part of the audit trail.
A financial summary has one more trap: several records can describe the same purchase. Reconcile the underlying event before summing its evidence. Reconcile economic events, not transaction rows covers the classification and authority rules for that case.