Extensions
The specification defines the envelope, the manifest, capability dispatch and the registry. Each extension adds to it: a media class the sink rebuilds, a receipt, a way to deliver envelopes, or a contract for what a decode reproduces. Every extension here is in the standard's main branch, and each page shows the status its text declares.
Mirrored from the canonical text at commit 117bad22 ().
The specification
Draft StandardWAI v1.0 — Web AI Media Transport & Execution
The container, the manifest, capability dispatch, the mandatory floor and the registered capabilities. Read it first; every extension builds on it.
Read the specificationReceipts and energy
What arrived, what ran and what it cost, signed so that a third party can check it.
-
JWP Receipt Chain
DraftSigned receipts for each delivered object, built from content hashes, per-group Merkle roots and group signatures, which relays forward unaltered.
Read the extension -
OER Receipts (outcome and energy)
DraftA receipt for one unit of work: what it was, what it cost, how that cost is graded, and what it rests on.
Read the extension -
Energy Measurement
DraftHow a joule figure is acquired and classed, so the same field means the same thing in independent implementations; unmetered work reads as not metered.
Read the extension -
Energy Binding
DraftBinds the energy a reconstruction cost to that reconstruction, written into a signed C2PA manifest.
Read the extension -
Asset Provenance
DraftA signed, energy-accounted lineage for captured content that WAI carries as opaque bytes rather than rebuilding.
Read the extension -
Reproducible-Reconstruction Binding
DraftA cryptographic binding over the deterministically decoded pixels of a neural-coded asset, rather than over its compressed bytes.
Read the extension -
Transparency Emission
DraftAn external encoding for receipts, so a party with no WAI tooling can check them, and registration with a transparency service so their existence is witnessed.
Read the extension
Media classes
Content carried as instructions or state. The sink rebuilds it and checks the result by hash.
-
Interactive Worlds
DraftMedia that consumes input: a deterministic world and a signed op log that every sink replays to the same state.
Read the extension -
Linear Film
DraftA film carried as the sealed world that generates it, a camera track and a frame schedule; the sink renders the frames.
Read the extension -
Avatars (Digital Humans)
DraftMotion carried as a signed stream of joint transforms that the sink uses to skin a mesh.
Read the extension -
State-Feeds
DraftTyped state, such as a scoreboard or telemetry, carried as signed updates that every sink replays to the same state.
Read the extension -
Object-Based Spatial Audio
DraftSound objects and a scene, mixed for the listener's own layout, with a mixdown that is exact for a declared layout.
Read the extension -
Score (Music as Instructions)
DraftMusic carried as note events that the sink synthesizes to a canonical mixdown.
Read the extension -
Haptics
DraftTouch carried as a keyframed intensity and sharpness envelope that the sink rebuilds into actuator samples.
Read the extension -
Volumetric / 4D Splats
DraftA moving Gaussian-splat scene carried as per-Gaussian keyframed tracks that the sink interpolates at any frame.
Read the extension
Dispatch, delivery and transport
What a sink checks before it decodes, and how envelopes travel to it.
-
Capability Constraints
DraftSupport is not binary: a capability can publish constraint sets, such as a resolution, frame rate or profile, and a sink checks an object against them before dispatch, not at decode.
Read the extension -
Derived Tracks
DraftTracks that carry a process the receiver evaluates rather than its result: the derivation operations of ISO/IEC 23001-16, each registered with its own determinism tier.
Read the extension -
MoQ Streaming Format
DraftWAI as a streaming format over Media over QUIC: one whole envelope per object, with catalog fields and an optional receipt property that relays preserve.
Read the extension -
Unidirectional Delivery
DraftBearers with no return path, such as broadcast, satellite and multicast, where a receipt attests what was sent, never what was received.
Read the extension -
Confidentiality (MLS + SFrame)
DraftPrivate channels from MLS group keys and SFrame object encryption, so relays route and meter ciphertext they cannot read.
Read the extension
Determinism, models and integrity
What a decode reproduces, which model it ran against, and how a claim about it is stated.
-
Determinism Tiers for Neural Decode
DraftNames what a neural decode reproduces, the entropy decode alone or the whole decode to the final medium, so a verifier knows what it may check.
Read the extension -
Prior Carriage
DraftThe wire forms a pinned model's digest may cover, including a parameter-set listing and the NNC bitstream of ISO/IEC 15938-17.
Read the extension -
Task Fidelity
DraftThe contract for media judged by a downstream model's behaviour rather than by its bytes, with the evidence graded.
Read the extension -
Balanced-Ternary MPS Transform (wai.ternary.tt)
Draft / reference prototypeA classical tensor-network transform whose reconstruction is byte-exact, portable and receiptable; registered for provenance, not for rate.
Read the extension
Quantum
Quantum computations carried as instructions and simulated classically, and receipts for quantum operations.
-
Quantum-Circuit Simulation
DraftA quantum circuit carried as a gate op log and simulated classically in fixed point, so the reconstructed state vector hashes the same on every machine.
Read the extension -
Quantum-Operations Attestation (wai.quantum.calibration · wai.quantum.job)
DraftSigned receipts over calibration runs and jobs that a third party can check from the bytes alone, each with its measured energy and acquisition class.
Read the extension
Each page here is the canonical text as it stands at the mirrored commit, under a line that names the commit. Only its links change: references between the specification and its extensions point to their pages here, and references to code and corpora point to the repository at that commit. The specification and its extensions are Apache-2.0 in the open-standards repository.
See the status page for what is in the standard, what is being built and the roadmap, and the demonstrations for the extensions that run in the browser.