Skip to content

Answer archive

Verify an evidence bundle

An evidence bundle from Recognly holds AI answers as they were captured, with the proofs that they have not changed since and the timestamps that date them. Upload one to check it, or check it yourself with the verify.py script inside it.

  • Each answer was hashed into a sealed record when it was captured.
  • The records of each capture form a Merkle tree; each week's root chains the week before.
  • Every root was dated by an RFC 3161 timestamp authority.
  • Changing any byte of an answer, record, proof or chain makes a check fail.

The bundle is checked in memory and not stored. Only its consistency and signatures are checked: the page never says whether a bundle matches data held by anyone.

What a passing bundle proves

This proves the product captured this text no later than the timestamp. It does not show what the engine says to other people or at other times, and it says nothing about the engine's intent. A timestamp from an authority you do not trust proves nothing about time: the demo authority used for sample data is always labelled "not trusted". This is not legal advice.

The checks

  • Every file matches the SHA-256 listed in manifest.json, and no file is missing or added.
  • Each answer's text, stored payload and provider response match the hashes in its sealed record.
  • Each record is canonical JSON (PM-CJSON-1); its leaf hash and audit path lead to its batch root (RFC 9162).
  • Each batch is in its week's tree, and each weekly root chains the previous week's, from the first week.
  • Each RFC 3161 token is over the right root, with the recorded nonce and time; its signature, signed attributes and certificate (time-stamping use, valid at the time) check out, and its chain is compared with the trust list.
  • The manifest's Ed25519 signature, when the bundle is signed, against the product's published keys.

Verify offline

Unzip the bundle and run python3 verify.py (Python 3.9 or newer, nothing else needed). With the Python package cryptography installed it also checks every signature; add --trust root.pem for each timestamp authority root you trust, taken from the authority's own site. README.txt in the bundle lists one OpenSSL command per timestamp for full certificate path validation.

Trusted authorities

The authorities whose roots this page trusts are listed at /api/v1/public/archive/trust, and the keys that sign bundle manifests at /api/v1/public/evidence/keys.