Most AI output asks for trust. These three clips — one per product — earn it. Each is rendered deterministically — same inputs, same bytes, every time — and the exact bytes are fingerprinted with a SHA-256 digest and countersigned by a neutral endpoint. Below each video is a button that re-hashes the file in your browser, right now, and shows the digest matches. No key, no cloud round-trip, nothing to take on faith.
Headless Chrome draws each frame from data; ffmpeg encodes single-threaded with a pinned toolchain. Re-render and you get the identical file — byte for byte.
The clip's exact bytes are SHA-256'd to a digest and countersigned (HMAC-SHA256) with a server timestamp. Change one pixel and the digest changes.
The button below each clip re-hashes the video your browser just downloaded and compares it to the attested digest. Proof you run, not proof you're told.
The reproduced v1.2 leaderboard (18 models, 13,171 pairs, bootstrap B=600, seed 20260606). Trust = 100·(1 − mean ECE). The premium #1 is shown beside the cheap model that ties it — calibration doesn't grade on brand.
Illustrative of the verification method — a real, calibrated probability, not investment advice. The point is the auditable record, not the ticker.
debounce<T> + cancel()The routing arm is chosen by a cost/quality scorecard, shown in the clip. The output is the model's real code, not a sample.
A hash-locked clip turns a claim into a checkable record: the bytes can't drift without the fingerprint changing, and a neutral endpoint has timestamped and signed that fingerprint. The same primitive underwrites Aequara's calibration work — every methodology carries a hash, every verdict an attestation. Watch the medium; verify the message.
An append-only, content-addressed ledger. Each row is a real claim from a NEXUS or AEQUARA proof surface, its fingerprint timestamped and countersigned by a neutral third party. Press re-verify and your browser re-derives the fingerprint locally — sorted-key canonicalisation, then SHA-256 — and checks it against the published head. No server in the loop, no key, no trust required: just arithmetic.