An AI answer needs evidence you can revisit.
An AI can sound confident even when its evidence is weak. A citation points to a source, but you still need to review the passage and know which version was recorded. Ledger keeps the claim, the source copy and their recorded connection so you can inspect them later and check for changes.
Fictional acquisition review · Atlas Components · Prerecorded, scripted answer. No live AI.
- 1 Claim
- 2 Evidence
- 3 Verify
- 4 Change & review
Start with a claim.
The recorded answer makes this claim. What evidence is behind it?
Research question
Claim from the scripted answer
Preserved source copy
The highlighted passage is the exact excerpt linked to this claim. Ledger preserves the claim, the full source bytes, the excerpt and their recorded identities. The link was declared by the scripted producer; it does not prove what an AI actually used.
Captured relationship and exact byte span
Checking: original preserved copy.
Your browser checks the preserved files against the recorded digital fingerprints (SHA-256): the manifest, all 8 records and both source bodies. It checks that the bytes match, not whether the claim is true.
Change one byte in a disposable copy of customer-summary.txt, then check again. The preserved original, its linked excerpt and every download stay available.
Browser byte integrity: not checked.
The original evidence is still reviewable.
You detected a change and restored a matching copy. A later reviewer can inspect the preserved claim and its exact source passage, even without the original producer store.
In the recorded example, a fresh reviewer recovered all three claims and their source links using only the downloaded bundle, without the original producer store. This browser checks file integrity; it does not run that reconstruction. Open the later-review details below to inspect the recorded result.
Integrity does not establish factual truth. Claim C still overstates its excerpt, even when the files pass verification.
Real digests, manifest and recorded reconstruction
The manifest pin is embedded in this page. Keep it independently if verifying a package received elsewhere. This is an integrity binding, not sender authentication.
Later review: independently recovered evidence
Independent Ledger reconstruction: recorded during qualification, not executed by this browser.
Recovered by a fresh reviewer · recorded result
The original producer store was withheld. A separate reviewer process received the portable Ledger bundle and pinned manifest digest.
- Import into a new, empty Ledger store: 8 records and 2 source bodies recovered.
- Run Ledger.why for each of the 3 claims: recover each recorded claim → excerpt → source relationship.
- Recheck source and excerpt digests, byte spans, record identities and relationships. Recovered records match the exported originals.
Byte hashing detects changed file bytes. Ledger reconstruction additionally checks recorded identities, spans and relationships in a fresh store. This browser did not run reconstruction. Both leave factual support for human review.
Reconstruct independently from the download
Unzip the portable bundle. From a checkout containing the existing Ledger Python modules and this demonstration command, run into a destination that does not exist:
The command runs the existing importer and Ledger.why with only the bundle and its pin. Inspect fresh-review/reconstruction.json for the recovered records and traces. Retain the pin independently.
Explore all 3 recorded claims
All three claims and their original links are preserved, including a claim with inadequate evidence. Labels about support are synthetic author annotations.
Observed Ledger execution order
These entries were emitted after actual Ledger calls completed in the correction run. Timestamps and operation IDs are in the downloadable execution evidence. Scripted output is preset; no model calls or inferred source usage are recorded.
Download observed execution logDemo limits and technical context
Integrity versus truth: verification does not establish whether a claim is supported or true. The browser checks byte integrity; a separate, recorded Ledger reconstruction checks identities, digests, spans and relationships. No sender authentication or inferred AI source usage is established. All sources and claims here are fictional; records remain NARRATIVE, authority NONE.
Email ryan@vajraya.com with a brief description of the workflow you would like to discuss.