[VERIFICATION GUIDE]

How to Verify Our Findings

Every finding on this platform is designed to be independently verifiable. We publish the data, the sources, and the methodology — so you never have to take our word for it.

Step 1 — Get the Audit Bundle

Click the PROVE IT button on any finding card. This generates a cryptographically hashed bundle containing the complete evidence chain: every source URL, every database query, and the exact data snapshot used to produce the finding.

// JSON endpoint
GET /api/audit/{type}/{id}
// Markdown version
GET /api/audit/{type}/{id}?format=md
// Download JSON file
GET /api/audit/{type}/{id}?download=1

Valid types: finding, contradiction, money_flow, lie, pattern

Step 2 — Check the Sources

The bundle lists every source URL used to support the finding. Visit each one and confirm:

The source exists and is accessible (we prefer archive.org URLs for permanence)
The source says what we claim it says
The source is from a credible publication or official record
The date matches our recorded date

Step 3 — Verify the Data

The dataSnapshot field contains the exact database state at generation time. The queries field shows which tables and parameters were used. You can:

Compare the data snapshot against the live finding page
Check that entity names, dates, and amounts are consistent
Follow the verification steps listed at the end of each bundle

Step 4 — Validate the Hash

Every audit bundle includes a SHA-256 content hash computed from the data snapshot. This proves the data has not been modified since generation:

// Verify in any terminal
echo -n '{"dataSnapshot":...}' | sha256sum
// Or in Node.js
const hash = crypto.createHash('sha256')
  .update(JSON.stringify(data, Object.keys(data).sort()))
  .digest('hex');

The hash covers the data snapshot plus finding type and ID. Keys are sorted alphabetically before hashing to ensure deterministic output.

Hash Lookup

If you have a content hash from a downloaded bundle, you can verify it was generated by this platform:

Finding Types

Conflicts of Interest

Identified conflicts, revolving doors, and regulatory capture indicators

/api/audit/finding/{id}

Contradictions

Stated claims contradicted by documented evidence

/api/audit/contradiction/{id}

Money Flow Chains

Traced financial flows between entities with per-hop citations

/api/audit/money_flow/{id}

Documented Lies

Public promises broken or abandoned, with sourced violations

/api/audit/lie/{id}

Influence Patterns

Recurring structural patterns in the entity relationship graph

/api/audit/pattern/{id}

Principles

Transparency by default. Every claim is backed by named sources. Every source is a clickable URL. Every data point traces back to a database query you can inspect.

Cryptographic integrity. Content hashes let you detect if a finding has been modified after you downloaded it. The hash algorithm and input format are documented so anyone can reproduce it.

Immutable audit log. Every time someone generates an audit bundle, it is logged with a timestamp and the content hash. This creates a verifiable history of when findings were checked.

No trust required. We built this system so you do not have to trust us. Check the sources. Verify the hashes. Follow the money. If we got something wrong, the audit trail will show it.