Skip to main content
The specification · extensions

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 or another signed record, 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 498e6b88 ().

The specification

Draft Standard

.WAI™ — 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 specification

Receipts and energy

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

Media classes

Content carried as instructions or state. The sink rebuilds it and checks the result by hash.

Dispatch, delivery and transport

What a sink checks before it decodes, and how envelopes travel to it.

Nodes, holdings and delivery records

What a node holds, serves and derives, and on whose authority; when an object is of use; and what a stream did, recomputed from signed records.

Channels, ads and settlement

A linear channel's lineup, its ad breaks and what each player presented, and what each party is owed, computed from signed records.

Live rooms

Rooms where several people publish and many watch: who may do what, what was said and shown, what it cost, and what was kept.

Together in a room

What people do together in a room: talk, watch, perform, take part as a whole venue, sound as a crowd, share a world or share a screen.

Made by people and models

What a piece of media is, who and what made it, and how much each contributed, as signed evidence bound to the output.

Sinks, platforms and formats

How a sink reports what it can do, the codecs a device already has, and the formats WAI identifies, probes and computes exactly.

Determinism, models and integrity

What a decode reproduces, which model it ran against, and how a claim about it is stated.

Quantum

Quantum computations carried as instructions and simulated classically, receipts for quantum operations, and the jobs, answers and devices around them.

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.