Verify any Fulcrum prediction.

Every prediction, edge alert, and daily brief we publish is timestamped and hash-chained — tamper-evident proof that we called it when we said we did. Paste a record ID below to see the receipt.

Find a record ID at the bottom of any prediction page or in our daily briefs. Min 8 characters; full UUID also works.

How verification works

  1. Every Fulcrum prediction gets stamped with: record_id, created_at, observed_at, source_url, payload_hash, and prev_hash (the hash of the prior record in the chain).
  2. The payload_hash is a SHA-256 of the canonical JSON of (payload + observed_at + source_url). If a single character of the payload changes, the hash changes.
  3. The prev_hash field links each record to the one before it. Tampering with any record breaks every record after it. We can't backdate predictions or change them after the fact.
  4. This page hits the public read endpoint at /api/provenance/{record_id}. The record served from Cloudflare's edge cache is exactly what we wrote — Cloudflare doesn't see our private log.
  5. For the most paranoid: take the payload, observed_at, and source_url shown below, compute SHA-256 of JSON.stringify({payload, observed_at, source_url}, sort_keys), and confirm it matches payload_hash. We use the same canonical form. Math doesn't lie.