Source A
Email thread
"The vendor first notified operations on April 11, after the weekend deployment window had already closed."
Sanitized visual example
Before and after: source-attributed reliability packet
This sample uses fictional source fragments to show the shape of a Reliability Review output. It is not legal advice and does not include private, client, or case material.
Before
Messy source set.
Source B
Invoice metadata
Notice field: April 8. Related ticket: INV-4408. Owner: Operations queue.
Source C
Meeting notes
"Team believed notice arrived before the outage, but no one confirmed whether the notification was read."
After
Reliability packet output.
Review item
Source state
Reliability result
Export-safe language
Vendor notice date
Source A says April 11. Source B says April 8. Source C is ambiguous.
Contradicted
The reviewed sources conflict on the vendor notice date.
Notice was read before outage
No reviewed source confirms read status before the outage.
Unsupported
The reviewed materials do not establish pre-outage read status.
Operations queue received ticket INV-4408
Source B identifies ticket and queue.
Supported
Invoice metadata identifies INV-4408 in the operations queue.
What changes for the reviewer?
- Assertions are separated from source support.
- Contradictions become explicit before downstream use.
- Unsupported claims are blocked from certainty language.
- Export language becomes safer and easier to defend.
Useful for
- Document-heavy disputes.
- Compliance evidence packets.
- Internal investigations.
- Forensic accounting reviews.
Next step
Bounded pilot review.
One document set, one review question, one reliability packet.