A quantum operation.
Signed, metered, and self-enforcing.
Every quantum-control stack in the field emits the same three unsigned things — an
HDF5 dataset, a JSON state snapshot, a dashboard. None signs, content-addresses,
ports, or meters the joules of a single operation. This page is the missing
object: your browser seals a wai.quantum.calibration receipt with the
same Rust native tools produce (Ed25519 + BLAKE3 Merkle, compiled to wasm), and then
the receipt enforces itself in front of you. WAI runs no hardware — the control
system does; WAI owns the receipt.
—
Gate ⊗ meter ⊗ receipt, in one object
The grant carries a joule ceiling, and the ceiling is checked inside verify(): a receipt whose measured joules exceed its grant is not valid — an
operation that blew its energy budget cannot produce a passing receipt. A job binds
the exact wai.quantum.calibration state the device was in when it ran, so a
third party can assert "this result was produced on a device in this attested
state" — the property the field reaches for (QCIVET, QBOM) but never signs, never meters.
Portable JSON, verifiable with only the public key, no vendor cloud. Reference engine +
spec in the open-standards repo, Apache-2.0.