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

White fingerprint and link-symbol panels with an open folder beside the Evidence Verification heading and David Medeiros original icon. — Compare the file’s bytes, then review its source and context. Presentation illustration; matching SHA-256 values do not establish authorship, truth or a legal finding.

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 3,499 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: 3,499
Cross-check mismatches: 0
Algorithm: SHA-256

Manifest root SHA-256: 75d4c101f5cfeaefc06bcf756f0b06a41b0b4a71d51f5f8c41e72e58e4684efb

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 covers selected public collections, the November 2023 public letters and America by Town videos; its current counts appear on the search page and in the discovery-index download. 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.

Read or download the forensic file manifest

Open the existing JSON download. This snapshot contains 3,499 records in entries. JSON is a text format for structured data; the field names below identify its columns or properties.

Field names, value types and coverage

These are observed keys and data types, not findings or a review of the records. “Present” includes empty or null values; an absent key is different from a false value. An array is a list; an object contains nested fields. Counts describe this snapshot, not a current agency total. This guide describes the JSON download only, not every CSV or other format.

Forensic file manifest: `entries` record fields
Field	Observed value types	Records with this key
`id`	string	3499 / 3499
`relativePath`	string	3499 / 3499
`fileName`	string	3499 / 3499
`extension`	string	3499 / 3499
`encodingFormat`	string	3499 / 3499
`byteSize`	number	3499 / 3499
`sha256`	string	3499 / 3499
`sourceModifiedUtc`	string	3499 / 3499
`contentUrl`	string	3499 / 3499
`delivery`	object	3499 / 3499
`mediaRecord`	null, object	3499 / 3499
`evidenceRecord`	null, object	3499 / 3499

Verify the downloaded bytes and understand reuse limits

Published file size: 3191306 bytes. SHA-256: f7c2c3565880bb1f3728a7689a5b79d4ab2c2b86da6b4c3a19719167f34e50dc. A matching digest checks bytes only, not authorship, accuracy, authenticity, legal custody or an official finding. Paths and filenames are archive metadata, not proof that a source is available.

Public availability is not a blanket reuse license. Follow the applicable rights and privacy limits of each original record. This guide grants no new permissions and does not change the evidence. Verification guidance.