Source Verification Process

Complete transparency on how we verify document authenticity

Last Updated: January 2026

Our Verification Philosophy

Every document is verified through multiple independent methods to ensure authenticity. We maintain complete transparency about our process.

1. Direct Source Verification

Documents are obtained directly from the U.S. Department of Justice with complete chain-of-custody documentation.

Verification Steps:

Obtain documents from official justice.gov source
Verify source URL and SSL certificate authenticity
Document download metadata
Generate SHA-256 checksum immediately
Compare against any official checksums
Store original copy as reference

2. Cryptographic Hash Verification

Each document is protected by cryptographic checksums that prove it has not been modified.

How Cryptographic Verification Works:

Original DOJ Document: Downloaded from justice.gov
Hash Generation: SHA-256 creates a fingerprint
Storage: Hash stored separately from document
Future Verification: Users can generate same hash if unchanged
Hash Mismatch: Indicates document has been altered

3. Metadata Verification

Document metadata is verified against official DOJ records to ensure consistency.

Verified Metadata Fields:

Document ID (matches DOJ record)
Document date and timestamp
Sender and recipient information
Subject line and document type
Page count and redaction indicators
Source agency
Release date

4. Cross-Reference Verification

Documents are cross-referenced with related documents and official records.

Cross-Reference Checks:

Compare with original DOJ database
Cross-reference with media coverage
Verify mentions in news articles
Check for related documents in email chains
Verify dates align with known events

5. Redaction Verification

Redactions are verified as official DOJ redactions, not tampering.

Redaction Process:

Document received with redactions from DOJ
Redaction type identified
Verification that redactions match standard format
Notation of redacted information
Clear indication to users of redactions

6. Correction Handling

When agencies issue corrections, we follow a transparent process:

Receive official notice of amendment
Create new version, preserve original
Mark document with status and date
Explain what was corrected and why
Make both versions accessible
Maintain public correction history

7. Complete Audit Trail

We maintain complete audit trails for every document.

Date document was acquired
Source and method of acquisition
Chain of custody history
Verification checks performed
Any modifications or corrections
Anonymized access logs
Checksum history and verification dates

Report Verification Issues

If you discover a document that appears inauthentic:

Document what you found
Note the document ID and date
Contact us with detailed information
We will investigate immediately
Public update issued if issue confirmed

Verification Workflow Diagram

The following represents our complete verification workflow from document acquisition to public access:

Source Identification

Identify official .gov source URL - Verify SSL certificate - Document source metadata

Secure Acquisition

Download via HTTPS - Log timestamp and file size - Generate immediate SHA-256 hash

Initial Verification

Validate file format - Check for corruption - Compare against any official checksums

Metadata Extraction

Extract embedded metadata - Run OCR processing - Assign Document ID

Cross-Reference Check

Compare with DOJ database - Verify against media reports - Check related documents

Quality Assurance

Manual review if flagged - Verify metadata accuracy - Document redactions

Secure Storage

Store original + derivatives - Create geographic backups - Log chain of custody

Public Access

Index for search - Enable download - Continuous integrity monitoring

Chain of Custody Tracking

Chain of custody is the documented, unbroken history of who possessed a document from its source to the archive. This is essential for establishing authenticity and defending against claims of tampering.

What We Track

Acquisition Phase

Source URL (exact path)
Download timestamp (UTC)
Downloading system identifier
SSL certificate details
HTTP response headers

Processing Phase

Processing system identifier
Tools and versions used
Processing timestamps
Operator identification
Verification results

Storage Phase

Storage location(s)
Backup creation dates
Integrity check results
Any file operations
Access grants/revocations

Modification Phase

Any corrections applied
Reason for modification
Authorizing party
Previous version preserved
Public notification date

Custody Record Format

{
  "document_id": "MME-2012-10-15-E-001",
  "custody_chain": [
    {
      "event": "acquisition",
      "timestamp": "2026-01-30T14:23:45Z",
      "source": "https://justice.gov/epstein-files/...",
      "hash_sha256": "a7b3c9d2e4f6...",
      "operator": "system-auto-001"
    },
    {
      "event": "verification",
      "timestamp": "2026-01-30T14:24:12Z",
      "result": "passed",
      "checks": ["format", "hash", "metadata"]
    },
    {
      "event": "publication",
      "timestamp": "2026-01-31T00:00:00Z",
      "status": "public"
    }
  ]
}

Version Control for Updates

When documents require updates - whether due to agency corrections, metadata fixes, or processing improvements - we maintain complete version history. No version is ever deleted.

Version Numbering

v1.0: Original document as acquired from source
v1.1, v1.2...: Metadata corrections or processing improvements (document unchanged)
v2.0: Agency-issued correction to document content
v2.1, v2.2...: Subsequent metadata updates to corrected version

What Triggers a New Version

Major Version (x.0)

Agency issues corrected document, Content change from official source, Document replacement

Minor Version (x.y)

Metadata correction, OCR quality improvement, Related document linking, Category reclassification

Accessing Previous Versions

All versions remain accessible. Document pages display the current version by default, with a version history link showing all previous versions with their checksums and change descriptions.

Public Audit Trail

Transparency requires accountability. We maintain a public audit trail documenting all significant changes to the archive. This allows the public to verify our practices and hold us accountable.

What We Publish

New Document Releases: Date, count, and source of new documents added
Corrections: Document ID, nature of correction, and reason
Methodology Updates: Changes to our processes with rationale
Removal Requests: Any removal requests received and our response (without disclosing requester identity)
Technical Changes: Infrastructure or format changes affecting access
Error Reports: Significant errors discovered and remediation steps

Audit Trail Format

The public audit trail is published as both human-readable pages and machine-readable JSON. Researchers can programmatically monitor the archive for changes.

Retention

Audit trail entries are permanent. We do not delete audit history. The complete history of the archive from its inception remains publicly accessible.

Invitation for Independent Review

We welcome independent verification of our processes and document integrity. Researchers, journalists, and archival professionals are invited to audit our work.

How to Conduct Independent Verification

Download Original: Obtain the original document from justice.gov or other official source
Generate Hash: Compute SHA-256 checksum of the original
Compare: Compare your checksum against our published checksum
Verify Metadata: Cross-reference our metadata against document content
Report Discrepancies: Contact us if you find any discrepancies

Tools for Verification

Windows

certutil -hashfile document.pdf SHA256

macOS/Linux

sha256sum document.pdf

Academic and Institutional Review

We welcome formal review by academic institutions, journalism organizations, and archival professionals. We will provide additional documentation and access to support serious verification efforts. Contact us to arrange institutional review.