Skip to main content
Live in your browser

Demonstrations.
The reference implementation, running in this tab.

The WAI sink is a computer. Each envelope names the capability that rebuilds its payload, so each piece of a stream can carry its own choice, and the sink rebuilds the result and checks its hash. These pages run the reference implementation, compiled to WebAssembly, in this tab, and every card below is in the standard.

For the format itself, see the specification and its extensions, the reference implementation, and why WAI is built this way.

In the standard
in the standard's main branch

Dispatch and adaptation

Each object names the capability that rebuilds it, so one stream can carry a different choice per piece, and one envelope can carry several kinds of content.

Learned codecs with byte-exact decode

Learned codecs whose decode is integer arithmetic, so the reconstruction reproduces byte for byte on every conforming sink.

Instructions rebuilt at the sink

The wire carries the instructions — ops, tracks, events, a prompt and seed — and the sink rebuilds the content and re-derives its hash.

Live and multi-party

Several tabs, one converged state, each op signed by the participant who made it.

Delivery and receipts

What arrived, what ran, and what it cost, signed so a third party can check it.

WAI Quantum

Quantum computations carried as instructions and simulated classically in the tab, against simulated devices. The engines are reference code in the standard's repository; a capability marked (receipt kind) names a receipt the engine seals, not a registered capability. WAI Quantum's home, with every way to install it →

Each badge compares the hash computed in this tab with the hash the native reference implementation recorded for the same input. Some demos run fixtures from a published conformance corpus; others run fixtures made for the demo. Where a page labels a hash FNV-1a, it is a 64-bit checksum of the decoded bytes used for that comparison; signed receipts hash with BLAKE3.

The specification, reference implementation and corpora are Apache-2.0 in the open-standards repository. Where a card names a companion implementation, that code lives outside the repository and carries its own licence.