Every decision Cascade makes comes with a signed receipt, so you can prove what happened and why. Below is a real one. Five checks run in your browser and need nothing from us except keys we published in advance: a root key held in AWS KMS that no one can export, and the public anchor log that no one can rewrite. Change one byte anywhere and the checks name the entry that was altered.
By default signatures are checked against the public key embedded in the pasted bundle. Paste the key you obtained independently, for example from a certificate you saved earlier, and the checks pin to that instead, which is what catches a bundle re-signed by someone else.
Same checks, same code path as the demo above — chain integrity, signatures, exclusivity, zero-token, anchors. Verdicts render in the panel above and name the broken entry on failure. Works offline: disconnected, every check runs except the comparison with the public anchor log, which reports SKIP.
A log you can edit is not evidence. If the same company that made the decisions also controls the record of those decisions, an auditor is being asked to take your word for it — and a serious auditor will not.
Cascade signs each decision as it is made and chains it to the one before. We cannot alter the record after the fact without breaking it, and neither can you. That is the whole point.
Everything an auditor needs to repeat the verification without contacting us — and nothing else.
Verification requires no Cascade service and no network access. Paste the bundle into cascadedynamics.ai/verify.html, saved or live, and pin the key above.
The bundle contains every decision, its signature, the certificates of the keys that signed it, and its anchors. The checks on this page fetch nothing from us except the public anchor log, so they work with the network off (the log comparison then reports SKIP). The same checks run from the command line with npx cascade-verify bundle.json, open source and with no dependencies. Source on GitHub.
Free key, public beta. Alter any decision in a run of your own and see how fast the chain names it.