When a claim shapes a decision, people deserve a way to examine it. Explore how sources, review, disagreement and corrections could stay together in one record
The person living with a decision deserves more than our confidence. They deserve to see what supports it and what might change our minds.
Sample records for exploring the interface. Hashes and links are examples, not live attestations.
| Claim | Status | Digest |
|---|---|---|
| Procurement bid award in contract GC-2026-88 coincided with undisclosed sub-tier beneficial stake.Reply: Pending | Sample: inferred | cca2c84c61… |
| Nitrate concentrations in upper basin exceeded legal threshold by 142% between June and August 2026.Reply: Received | Sample: verified | e3b0c44298… |
cca2c84c61…e3b0c44298…Imagine a team measures a river and writes down what it found. Another person asks about the instrument, the date and a later correction. A useful notebook keeps those questions with the original file and the review. A digital fingerprint helps check whether the file changed. People still need to examine whether the measurement and conclusion deserve trust. Evidence Ledger explores how that record could stay together.
A notebook that keeps the evidence and the corrections together.
Check the file’s integrity and see what the evidence actually supports.
You see a confident claim that could affect people’s lives. The chart looks careful, but you cannot find the original measurement, the reviewer or what changed after an objection. Those gaps deserve attention before the claim becomes a decision.
Imagine an illustrative record that keeps the source, the method, independent review and corrections within reach. People can examine the same material and disagree about what it supports. That is the design ambition. A matching fingerprint establishes file integrity, while the quality and meaning of the evidence still require scrutiny.
A polished chart, an official logo or a confident voice can make a claim look settled. If the source, method and changes are missing, readers cannot properly examine it.
Keep the claim beside its source, evidence status, review and objections. Use cryptographic checks for file integrity and human scrutiny for meaning and reliability.
People can disagree more precisely when they can inspect the same record. A pilot must test whether the tools actually improve traceability and review.
People need to know what they are being asked to trust. Follow the proposed steps, the responsibilities and the checks that a real operation would need
Record where evidence came from, when it was collected and which claim it supports, subject to privacy and access rules.
Design: source metadata and a SHA-256 digest for checking file integrity.Distinguish observation, inference and uncertainty. Preserve the basis for a reviewer’s assessment.
Design: governed evidence classes with review notes; a percentage alone is not a validation method.Preserve how a result was produced, what was reviewed and why later edits were made.
Design: versioned provenance with explicit limits on what each attestation establishes.Provide relevant records to authorized reviewers without exposing protected personal or sensitive information.
Design: inspectable export packages with clear source, integrity and access limitations.Ambition needs evidence. These are pilot goals, not measured or independently verified results
Test whether file fingerprints and version history make material changes easier to identify.
tamper-evidentHelp people preserve sources, collection methods and reviews. Legal admissibility still depends on jurisdiction and procedure.
documented provenanceGive readers a common record to inspect, challenge and correct.
check, do not trust