Evidence integrity

Verify the files, then verify the claims.

This build includes a machine-readable manifest for 730 evidence files. Every row gives the exact relative filename, byte size, full 64-character SHA-256 digest, and UTC hashing time.

Download the SHA-256 manifest

What a matching hash proves

A matching digest shows that the downloaded file is byte-for-byte identical to the file hashed for this manifest. It can detect later alteration or corruption.

What a hash does not prove

A hash does not establish who created a document, whether every statement is true, whether an allegation is proven, or whether a court or agency reached a legal finding. Those questions require source and context review.

Manifest details

Algorithm: SHA-256
Files listed: 730
Hashing began: July 17, 2026 at 8:36:46 PM UTC UTC

Runs entirely in this browser

Verify a local file without uploading it

Choose or drop a file below. Your browser calculates its SHA-256 digest locally with WebCrypto and compares it against the unified manifest for 1,888 preserved files. The selected file is not transmitted to this website.

Drop a file here or choose a file Nothing leaves your device. Large files may take several seconds.

Waiting for a local file.

JavaScript is required only for this local verification tool. The manifests and all archive pages remain statically readable without it.

Unified forensic manifest

Files indexed: 1,888
Cross-check mismatches: 0
Algorithm: SHA-256

Manifest root SHA-256: be1f9bf26d8a6f938fb67d27d1fd7d81d60c6f86512c61c248c57f781ed098d3

This root is a build-generated consistency digest. It is not an independent timestamp, digital signature, notarization, or proof of when any file first existed.

JSON manifest CSV manifest NDJSON manifest Root record Forensic and law-enforcement use boundary

Review standard

1. Identify the exact file.
Match the relative filename and byte size.
2. Calculate SHA-256.
Use a trusted local hashing tool on the downloaded file.
3. Compare all 64 characters.
An abbreviation or partial digest is not sufficient verification.
4. Check provenance and context.
Review the source, date, surrounding correspondence, and any agency or court disposition.

How to verify a discovery result

The archive explorer is bounded to exactly 1,729 privacy-reviewed records across 11 selected public collections; quarantined and unreviewed collections are excluded. Search, timeline, and relationship views are finding aids, not evidence and not adjudicated conclusions. Open the linked permanent record, compare its identifier and source filename, confirm the separately labeled source-file and derived-record SHA-256 scopes, then review the underlying source and its documented limitations. A matching digest confirms matching bytes only; it does not prove authorship, accuracy, completeness, or legal admissibility.

Verify the claim label as well as the file

File identity is only one part of verification. Public records now link to a controlled evidence architecture that keeps source facts, attributed statements, allegations, editorial positions, unresolved questions, and quarantined material separate. It also records provenance, human-review status, limitations, and correction requirements without exposing private control files.