Locker keeps every automation run in a signed chain and hands back a receipt for each one. This page is the receipt explained once, and a real one you can try to break.
The receipt carries a SHA-256 fingerprint of the run document, byte for byte. Hand anyone the document and the receipt and they can recompute the fingerprint themselves. A changed byte is a different fingerprint.
Every receipt names the one before it by fingerprint. The install signs each receipt with a P-256 key whose public half is in the receipt, so a signature that verifies ties the receipt to that install and to nothing else. Change a receipt and its own fingerprint changes; change an old one and every receipt after it stops linking.
Yes. The receipt page recomputes everything in your browser; the export bundle carries a verifier that runs under Node with no packages and no network; and the daily root of every chain is shown on the anchors page, so anyone who keeps a copy can show what the chains looked like that day.
What the workflow posted: inputs, outputs, status, in JSON, up to 1 MB.
SHA-256 of the document, and a fields root built from salted hashes of every field, so one field can be removed later and the rest still prove out.
Receipt id, install id, chain position, the previous receipt’s fingerprint, both document fingerprints, the time, the key id; fingerprinted and signed.
Each receipt links to the one before it back to the first. The install’s head moves one position per run; two writers racing for the same position lose, never both win.
Once a day the head of every chain is folded into one hash with the day before. It is shown on the anchors page and in the feed that page reads.
This is a real receipt from Locker’s published test vectors, with the run document it fingerprints, checked in your browser right now. Open Check it, change anything, and watch the checks turn. The private key is not here, so nothing you change can be signed again: that is what tamper-evident means.
The chain format is published in the FlurryPORT Core repository as docs/receipts/locker-receipt-chain.md, with a vector file three implementations assert.