Explore Runs
The public ledger of every sealed Factory run. Each row is an opaque commitment — a permanent proof a run happened, holding none of its content. Verify any of them yourself, right here in your browser.
—runs sealed
0verified by you
0failed
Reading the public ledger…
How you can trust this without trusting us
- 1Reconstruct the entry. Each run published exactly
{ kind, seq, head, at }— nothing else. We rebuild it byte-for-byte from the stored fields. - 2Recompute the Merkle leaf. The same RFC-6962 hash the log used. This runs in your browser with Web Crypto — the exact engine behind /transparency.
- 3Match it against the signed root.If the head, sequence, or timestamp were altered after sealing, the recomputed leaf won't match — and the check fails. No operator can fake a pass.
honest edges
- Each run seals a single-entry log, so inclusion confirms the head under its own signed root; the anchor chain then binds every run into one tamper-evident order across the whole ledger.
- A run anchors only when a quorum of independent witnesses cosign — each its own network service holding its own stable Ed25519 key, and you re-verify every cosignature yourself above. (If the witness network is unreachable, sealing falls back to in-process witnesses, marked by their ephemeral keys.)
- The chain tip is notarized on Bitcoin via OpenTimestamps — a real public-network proof you can download and verify with the standard
otsclient. Once a block confirms it, not even we can backdate or rewrite the ledger's order. - The remaining trust surface is honest: the witness services still share one host here (true multi-operator federation is the next step), and Bitcoin confirmation is asynchronous — a fresh anchor is pending until a block commits it, which is the price of needing no trusted party.
- The ledger holds only opaque heads and hashes. It proves a run happened and when, never what it was — that content lives only in your private receipts.