Select a folder of your own receipts. The page re-runs each one from its recorded inputs and lists which results differ under a condition you choose: the published kernel as it is today, or a parameter value you edit. Each line is a pair of recomputable hashes.
Runs in your browserNo network after loadNothing storedCaps: 2,000 files, 20 MB
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
1. Choose receipts
Every .json file in the folder is read. Other files are ignored and counted.
Receipts are read into memory and dropped when you close or reload the page.
No files selected.
2. Choose the condition
Each edit sets one value in the recorded policy parameters, addressed by a JSON pointer such as /threshold. The value is read as JSON when it parses (a number, true, a quoted string) and as plain text otherwise. A receipt that has no such pointer is reported as unresolved for that edit.
Vintage mode (moving a dated fact to another year) is not offered yet.
3. Report
File
Node
Receipt kernel digest
Result
Recorded execution hash
New execution hash
Differing pointers
Note
A result of CHANGED means the output differs under the stated condition. It does not say the recorded receipt was produced incorrectly. Whether an earlier kernel needed correcting is the claim of a published erratum, which this page does not read.
How the results are named: SAME (identical output and hash), CHANGED-VERDICT (the verdict moved class), CHANGED-VALUE (the verdict class held, another member differs), REFUSED (the new run refused or raised a structured error), UNRESOLVED (the node is not on this site, or the receipt cannot be re-run from its file), TAMPERED-OR-MALFORMED (the file does not match its own hash, so it takes no part). Signatures, proofs and anchors are checked on the receipt bundle verifier. How this page works.