ClearFrame

Verification

Verify a ClearFrame receipt — check it yourself, offline

Check a ClearFrame receipt in your browser. The checker runs on your machine, uploads nothing, and states what it can and cannot prove.

Last updated

This page checks a ClearFrame verification receipt. The checker runs entirely in your browser: your receipt is never uploaded, no ClearFrame server is contacted, and the page works with your network disconnected. It is the same checker the repository ships, built for the browser from the same source.

A clearframe-receipt-*.json exported from the ClearFrame review panel.

What this page can and cannot tell you

Every result lists each check separately and names the ones that did not run. A receipt that passes everything it was possible to check is reported as valid_with_gaps, not valid, and the difference is stated rather than hidden.

What a passing result proves

  • The receipt has not been edited since it was issued. Its content digest is recomputed from the bytes in front of you, so changing a field, a level, or a finding breaks the match.
  • The signature verifies. The result says where the key came from, because verifying against a key you obtained independently and against the key stapled to the document are different claims.
  • The disclosure is explicit. The receipt lists what it published and what it withheld, so you can tell a redaction from an omission.

What it does not prove

  • It does not grade the work. A receipt from a local ClearFrame profile states level none, because the verified mark's ladder re-derives from a compiled constraint ledger and a change request, and a single machine has neither. A level here would be a claim its own evidence does not support.
  • It cannot re-derive the level without the ledger and the change request. If you do not supply those, that check is reported as not run. It never counts as a pass.
  • It cannot detect a receipt forged wholesale — key, signature and content minted together. Nothing re-derived from forged evidence can detect forged evidence. That is what the ledger's own signature and its transparency log are for, and both travel with the ledger rather than this file.
  • It does not tell you who issued the receipt. The signer is a key held on the machine that made the correction, not a ClearFrame identity.

Checking it yourself, without this page

You do not have to trust this page either. The same checker runs offline from the repository:

node tools/offline-check.mjs --receipt <your-receipt.json>

It needs no network, no account and no ClearFrame software. If this page and that command ever disagree, believe the command and tell us.