Every workflow here computes inside your browser tab and needs no AINumbers server. The one step that goes online is optional and sends a 32-byte hash to our anchor service for timestamping. Tick network off to watch the whole run without it.
Show seven workflows running in your browser as one database turned inside out, where the pages hold the logic and you keep the receipts. Only a 32-byte hash ever needs to leave your device.
| Usual database | Here |
|---|---|
| Schema on a server | Public tool pages. Same bytes for every visitor, versioned and hashed. |
| Query engine | The page's own kernel, running in your browser tab. |
| Index and joins | ChainGraph: which page feeds which, published as one JSON file. |
| Rows | Receipts. A result plus a hash of what was computed. You keep them. |
| Commit log | A Merkle root over the receipts, signed by independent timestamp authorities. |
| Change history | The lineage registry, checkpointed into the public Sigsum log and cosigned by witnesses. |
| Audit | The Verification Desk replays every layer offline against public evidence. |
| Your data at rest | Nowhere on our side. Inputs live in tab memory and go when the tab closes. |
Each lane is a real ChainGraph workflow and each card is a real tool page from it. Gold same page tags mark one public page serving two workflows with two different sets of private inputs.
Finished chains drop a receipt into the audit-trail aggregator (cry-05). The Merkle batch verifier (cry-04) folds all seven into one root.
The bottom band is the anchor and verify layer. Only the root goes to the anchor service. Timestamp authorities sign it, and an auditor later replays lane two in the Verification Desk. An edited copy fails at the first check and the original passes.
Chains and steps come from chaingraph.json. Two lanes show the first three steps of longer chains. Input values are synthetic. Hashes are real SHA-256 computed in this page over the demo values shown; they show the shape of a receipt and differ from the kernels' canonical execution_hash. The anchor service, the three authorities, the Sigsum log at seasalp.glasklar.is and its lineage checkpoint (leaf 70,299, eleven witnesses, 4 October 2026) are real and described in the anchors explainer. Their part in this run is staged: no token here was actually requested.