Forensic readiness · interpretation boundary

A structured lead and preservation archive—not a substitute for an investigation.

The archive can reduce the time required to locate, compare, and prioritize records. It can support investigative triage and preservation. It cannot independently create probable cause, authenticate every source, complete a legal chain of custody, or establish guilt, liability, intent, or an agency finding.

Three separate checks: SHA-256 compares bytes; origin and custody need evidence; receipts, allegations and findings differ. Matching bytes do not prove claims. — File check: SHA-256 compares bytes. Source check: origin and custody need evidence. Claim check: receipts, allegations and findings differ. A matching hash does not establish authenticity, truth, legal admissibility or an agency finding. The source-acquisition and corroboration steps below explain these separate checks.

What is verifiably available now

3,499

Files in the unified forensic manifest

789

Distinct supplied-evidence records

2,137

Indexed public images and videos

Manifest cross-check mismatches

Current build root SHA-256: 75d4c101f5cfeaefc06bcf756f0b06a41b0b4a71d51f5f8c41e72e58e4684efb

What the archive can support

Lead organization: persistent record IDs, filenames, categories, timelines, and direct source links help reviewers locate related material.
Byte-identity testing: SHA-256 and byte-size comparisons can identify an exact match, later alteration, or corruption.
Acquisition planning: aliases and source categories can help identify which custodian, agency, account, or storage location should be independently examined.
Triage and corroboration: machine-readable ledgers allow investigators to filter and prioritize documents before requesting originals or testimony.
Public-source citation: permanent detail pages supply a stable reference for a specific archived byte sequence.

What it does not establish by itself

A complete forensic chain of custody from the original creator or custodian.
Authentication or admissibility under any particular rule of evidence.
Probable cause, reasonable suspicion, criminal intent, civil liability, or an adjudicated violation.
That an agency opened an investigation merely because it issued a submission receipt or tracking number.
That a filename-derived description is OCR, visual identification, authorship verification, or a verbatim transcript.
An independent timestamp, digital signature, blockchain record, IPFS pin, or third-party notarization.

Defensible investigative workflow

1. Identify
Use the permanent evidence ID, exact filename, category, byte size, and all known aliases.
2. Verify
Download or obtain the file, calculate SHA-256 locally, and compare every hexadecimal character and the byte size.
3. Acquire independently
Seek the original from the custodian, account, device, agency, legal process, or documented collection source where appropriate.
4. Document custody
Record who collected the item, when, from where, with what tool, and every subsequent transfer or transformation.
5. Corroborate
Compare the content with primary records, testimony, metadata, agency responses, court records, and other independently obtained sources.
6. Separate conclusions
Distinguish submission, receipt, allegation, author interpretation, agency action, and adjudicated finding.

Examined PDF examples

The two supplied examples were read without modifying their bytes. Both already contain searchable text layers; automatic OCR was unnecessary.

EV-000004 · DOJ Civil Rights submission receipt

3 pages; extractable text detected on all 3 pages; SHA-256 06529afbf908ef63efe773d64acf72f9e2677a08d24217acd2e13e77f425ed3c.

Open permanent record

EV-000198 · OSC disclosure filing

43 pages; extractable text detected on all 43 pages; SHA-256 ba7c4edae841506a0dfb1b93b3dbf0dd2a5f05f2b5f79fd82bfa632de87ff87f.

Open permanent record

Verification and machine-readable access

Open browser hash verifier Forensic manifest JSON Build root record Complete evidence ledger