Buy proof, and data you can prove.
Two products, both built on the same attestation spine you just verified with the button above. Verification is free; you only pay to anchor or to license.
A live attestation instrument, and the key to put your work through it
A signed physics beacon and a witness key that turn any file into a receipt anyone can verify offline with standard Ed25519. Verification is free forever. Curious? The $5 door is always open.
page proof Look inside → Data · provenance-attestedTraining datasets you can audit before you buy
Oracle-verified code pairs and provenance-gated text, each with a signed chain you can re-verify yourself. Free sample first. From $199.
page proof Browse datasets →One language under most of what you just verified.
The compiler. The MHD simulation that becomes the beacon. The server that publishes each pulse, and the signer on the witness. A TLS 1.3 stack. Each of those is Rail, and all of it compiles from a single ~1.0 MB seed binary you can read end to end. The rest, named plainly: the pulse signer is Python, this page is served by a Cloudflare Worker, and the button up top checks signatures with your browser's own WebCrypto.
the compiler you run is the compiler you read
Being readable is the prerequisite, not the point. A compiler small enough to audit and reproducible enough to trust can act as a referee, which is what machine-written code has never had. A model's claim that its output is correct can't be checked by anyone. A compile can be re-run by everyone.
Same primitive. Every scale.
A signature you can re-derive in your browser, anchored to a public, hash-chained physics beacon and countersigned by a witness on separate hardware (a Raspberry Pi that Ledatic runs). That primitive runs from one artifact at your doorstep all the way out to every deploy of this site, and to every record in a public archive. Same chain. Different scope.
Verify
One record, one chain, "ok" in your browser. Drop any artifact and its signed record: your browser re-hashes the bytes and checks the Ed25519 signature against the pinned witness key and the entropy pulse it was anchored to.
page proof FleetSystem
Mission control, sentinel-checked. Every surface renders unknown until a signed check passes; nothing glows that hasn't proven itself.
page proof ArchiveReplay
Every full deploy of this site since 2026-06-10 in one ledger, each pulse-anchored and Ed25519-signed. Diff any two and see what changed; prove either one in your browser.
page proof MachineThe oracle
What the compiler is for. A model's claim that its code is correct can't be checked; a compile can. We train against the checker, and publish the month that method lied to us.
page proof52 tagged releases and counting.
the first four figures are injected at deploy time from a generated
registry, not typed by hand; the last is a fact about the seed binary
(otool -L lists only libSystem). all but one tagged release
carries a signed attestation on the changelog, and the proof you can
press right here is the signed deploy manifest at the top of this page.
Every pulse now commits to the one before it.
The beacon ticks every 2 s. Kept up, that is roughly 220 million pulses by 2040. Since pulse format 2 (2026-10-19) each one hashes the one before it, and every deploy of this site is signed against the chain. Rewrite any old pulse and every later one changes, so every copy saved anywhere would disagree.
fourteen years from now, this page will be able to prove what it said today