Skip to main content
Why · A Transaction Science Open Standard

The sink is a computer. Build for it.

Every hop between a source and a screen does work. The encoder splits content and chooses a representation for each piece, the edge selects what to forward, and the sink rebuilds what it receives and checks it. This is how WAI is built for that, starting with how each era of delivery changed the pipe.

History

Every era changed the pipe. WAI changes the cargo.

Each era of video delivery moved the same kind of cargo — pictures coded for display — and rebuilt the pipe around it: new transport, new caches, new ways to pay for delivery. Codecs got better at packing pictures and pipes got better at moving them. WAI keeps the pipe and changes what rides in it.

  1. about 1940s–1990s

    Broadcast

    Technology
    Radio-frequency transmission from towers and satellites, and cable; late in the era, digital multiplexes of coded pictures replaced analog signals on the same channels.
    Infrastructure
    Transmitters, satellite uplinks, cable headends and set-top tuners, sized in channels.
    Economics
    Cost sat in fixed transmission capacity; one more home inside the footprint cost the sender nothing.
    Cargo
    One continuous signal, the same for every receiver.
  2. about 1995–2008

    Progressive download and streaming servers

    Technology
    Files that played while they downloaded over HTTP, dedicated streaming protocols and plug-in players; one bitrate per file.
    Infrastructure
    Origin servers, and the first caching edges for popular files.
    Economics
    Bytes delivered per viewer became a running cost, and rebuffering became the main quality risk.
    Cargo
    One coded file per title, the same for every viewer.
  3. about 2009–2015

    Segmented adaptive streaming over HTTP caches

    Technology
    Segmented HTTP delivery — HLS (RFC 8216) and MPEG-DASH (ISO/IEC 23009-1) — with a ladder of renditions; the player switches rung at segment boundaries.
    Infrastructure
    Encode farms that produce every rung, packagers, and large HTTP caching networks, including caches inside access networks.
    Economics
    Encode work and storage grew with the number of rungs, and delivery with bitrate times viewing hours; rebuffering fell.
    Cargo
    The same pictures coded several times over, cut into segments.
  4. about 2015–2020

    Content-aware encoding and newer codecs

    Technology
    Per-title and per-shot encoding chose each ladder from rate–quality analysis; HEVC, VP9 and then AV1; high dynamic range.
    Infrastructure
    Analysis-driven encode pipelines, several codecs stored per title, origin shielding, and steering across delivery networks.
    Economics
    Fewer bytes for each quality level, paid for with more encode work and more storage per title.
    Cargo
    The same pictures, packed tighter, still coded several times over.
  5. about 2018–2024

    Low-latency live and server-side ad insertion

    Technology
    Chunked CMAF (ISO/IEC 23000-19) and low-latency HLS and DASH; ad insertion at the server driven by SCTE-35 cue messages; contribution over SRT and RIST.
    Infrastructure
    Live origins with short cache windows, per-session manifests, and splicing at the edge.
    Economics
    Live encoding and per-session manifest work grew with the audience; advertising paid back part of delivery; peak concurrency set capacity.
    Cargo
    Smaller chunks of coded pictures, wrapped in a manifest per viewer.
  6. 2025–2026

    The current state of the art

    Technology
    AV1 at scale; the AV2 specification, published in May 2026; VVC where it fits; content steering; client and server data reporting (CTA-5004, CTA-5006); HTTP/3 over QUIC; Media over QUIC as IETF Internet-Drafts; browser APIs for decoding and transport.
    Infrastructure
    Multi-codec ladders, steering control planes, QUIC at the edge, and Media over QUIC relays in trials.
    Economics
    Bytes per quality level keep falling while encode work grows with codec complexity; delivery still scales with viewers, hours and bitrate, and storage with rungs and codecs.
    Cargo
    Coded pictures, decoded for display — the same kind of cargo as the first digital era.
  7. WAI

    Same pipes, different cargo

    Each piece of a stream names the capability that rebuilds it: a standard codestream, an integer learned codec, or instructions the sink evaluates. The origin, the edge and the last mile stay. What changes is the work each hop does.

    Encode

    Split the content and choose a representation for each piece.

    • In the standard per-object capabilities, renditions in one envelope, content-hashed segments
    • In the standard a packaging policy, scene cuts and the integer video encoder
    • In the standard packages with a stage index, a signed receipt and HLS, DASH and Media over QUIC views
    Edge

    Select what to forward, without rewriting it.

    • In the standard relays forward envelopes and receipts byte for byte; a binding to Media over QUIC, tracking its drafts
    • In the standard HTTP delivery: a head checked before more is fetched, and byte-range fetch of one rendition
    • In the standard a deriving edge that re-packs under its own receipt
    Decode

    Rebuild each piece, check it, and refuse what does not match.

    • In the standard
    In the standard

    Between them, staggered compression: a base first, refinements after.

    Measured, not projected: Cargo, measured runs one clip both ways in your browser.

The path, hop by hop

  1. 01 Encode

    Encode

    Splits the content into pieces and names the capability that rebuilds each.

    • In the standard per-object capability · renditions
    • In the standard packaging policy · scene cuts · integer video encoder
    • In the standard packages: stage index · signed receipt · HLS, DASH and MoQ views
  2. 02 Origin

    Origin

    Stores one object per piece with its content hash; identical segments are stored once.

    • In the standard content-hashed packaging
  3. 03 Edge

    Edge

    Forwards objects and their receipts byte for byte, and serves the tracks a sink subscribes to.

    • In the standard relay preservation · Media over QUIC binding (drafts) · a layer per track, receipts recovered
    • In the standard HTTP delivery · a checked head · byte-range fetch of one rendition
    • In the standard deriving edge
  4. 04 Last mile

    Last mile

    Carries the pieces the sink picked — a base first, refinements after.

    • In the standard per-object receipts travel with objects
    • In the standard staged delivery
  5. 05 Device

    Device

    Rebuilds each piece, checks it by hash, refuses a mismatch and falls back to another rendition.

    • In the standard
00 · The thesis

Every hop does work.

The sink is a computer. A WAI file names the capability each piece of content needs — a standard codec, an integer learned codec, or instructions the sink replays — so the representation is chosen per piece, and a conforming sink rebuilds what it receives.

For the integer and instruction capabilities, conformance requires the same state, samples or per-frame identity on every machine, so a reconstruction made anywhere checks by hash. Each class pins what it owns: a film or a world pins its state and leaves the render to the sink; a world model pins its action trace; a spatial-audio mix is exact for its stereo floor, given the sources' decoded samples.

So every hop does work. The encoder splits content and chooses a representation for each piece. The edge selects what to forward without rewriting it. The sink rebuilds what arrives and proves it. Staggered compression, a base first and refinements after, is what WAI's packager automates next, for on-demand video, live channels and live content alike.

  • In the standard

    Per-object capabilities with declared fallbacks, envelopes that carry several renditions for the sink to choose among, receipts that relays preserve, and a binding to Media over QUIC in which each object is one envelope.

  • In the standard

    Content-hashed packaging whose deduplication totals a verifier recomputes, one manifest generation per session class, and an enhancement layer bound to its base.

  • In the standard

    Refinements delivered as separate objects after their base.

  • In the standard

    Edges that rebuild content under their own receipt.

01 · Name it, don't ship it

The file names what it needs. The sink supplies it or says so.

  • In the standard

    The model a neural payload needs is named and pinned by digest, and it is never carried in the envelope; a mismatch is refused. A pinned prior can declare its artifact's wire form, and the NNC bitstream is registered as one.

  • In the standard

    The normative model pin: one digest over a whole parameter set, a set of several files pinned through its listing, a closed determinism vocabulary and a predecessor link. Each rendition in a multi-rendition envelope can carry its own id, payload digest and pin, and a sink decodes only from the bytes it verified.

  • In the standard

    A sink that lacks a capability uses a declared fallback or reports the file inert — it never guesses. A fallback decodes the same payload; alternate content travels as renditions.

02 · What can ride the wire

Coded samples, integer learned codecs, or instructions.

  • In the standard

    Standard codestreams. Each capability in the codec registry carries a licence class a deployer queries in code.

  • In the standard

    Broadcast and streaming codec registrations, each licence-classified, never a default, and decoded by the sink's own libraries.

  • In the standard

    Integer learned codecs for images, video, audio and 3D splats, whose conformance requires byte-identical output on every machine — among them wai.neural.int_mlicpp, the MLIC++ entropy topology, integer end to end.

  • In the standard

    A pinned binary payload format for each integer codec, an integer decode path that needs no machine-learning runtime, and a cost a sink reads from the header before it decodes.

  • In the standard

    Instructions the sink evaluates: worlds, film, reels, score, avatars, feeds, 4D splats and haptics.

  • In the standard

    Derived tracks: derivation operations over decoded samples, each with a stated determinism tier.

  • In the standard

    A deriving edge that evaluates those operations.

03 · Encode

Break it up. Choose per piece.

Because each object names its own capability, a stream changes representation from one object to the next: a coded picture, a learned latent, or instructions.

  • In the standard

    Several renditions of one piece in one envelope, and a licence class for each capability in the codec registry, queryable in code.

  • In the standard

    Integer codecs let an encoder predict the decoder's output exactly. The integer video encoder closes its loop on the reconstruction, not on the source.

  • In the standard

    Segmentation on group-of-pictures boundaries into content-hashed pieces, whose deduplication totals a verifier recomputes from the signed segment map.

  • In the standard

    wai-pack's policy and segmenter: a declared packaging policy, digested over its canonical form, and pieces cut at scene changes.

  • In the standard

    wai-pack writes packages: a stage index, a package receipt signed over its policy, a floor checked against its keyframe plan, and HLS, DASH and Media over QUIC views.

04 · Staggered compression

A base first. Refinements after.

A sink that computes starts from a base and improves it as more arrives. WAI does this in three forms.

  • In the standard

    Temporal: a learned integer keyframe, then integer motion-compensated frames, byte-exact down the whole group of pictures.

  • In the standard

    Layered: a standard enhancement layer bound to exactly one base rendition in the same envelope; the sink supplies its decoder.

  • In the standard

    Staged delivery: WAI-native refinements delivered as separate objects after their base, each linked to its base by hash, with a stated determinism tier for every prefix — so a partly refined picture carries its own tier, and a missing refinement leaves the base intact. A sink bounds the work and memory of every layer and of the whole chain.

  • In the standard

    Staged delivery rebuilt in the browser by the same sink, every stage checked by hash; and measurement of what each stage costs in counted bytes and gives in integer quality, with a stall bound proved for a delivery plan.

Across media types

How each class of content is carried, and its staged forms. Video has two staged forms in the standard besides staged delivery; staged delivery, refinements as separate objects after a base, covers images, video, audio and 3D splats.

Staged compression by media class, with status
Media Carried now Staged form
Video Coded or integer video, packaged on group-of-pictures boundaries into content-hashed segments.
  • In the standard temporal base and refinements
  • In the standard an enhancement layer bound to its base
  • In the standard refinements as separate objects
Still images Standard codecs and integer learned codecs, one picture per object.
  • In the standard refinements as separate objects
Audio Coded audio, integer learned audio, or a scene of sound objects the sink mixes.
  • In the standard refinements as separate objects
3D and splats An integer splat codec, and 4D splats as keyframed tracks.
  • In the standard refinements as separate objects
Worlds, film and feeds Signed instructions and operation logs the sink replays. —
Haptics Haptic signals. —
05 · Edge

Select without rewriting. Rebuild under its own receipt.

  • In the standard

    A conforming relay forwards envelopes and their receipts byte for byte: no transcoding, no manifest rewrite, no re-signing. A relay that attests does so in a separate, parallel receipt.

  • In the standard

    A binding to Media over QUIC, tracking IETF Internet-Drafts: each object is one whole envelope, and the catalog lists every capability a track uses, so a sink decides before it subscribes.

  • In the standard

    One manifest generation per session class, served to every viewer in that class.

  • In the standard

    A deriving edge that rebuilds or re-packs content and signs its own step, chained to the source's receipt.

06 · Decode

Pick, check, rebuild.

07 · VOD, live and live content

On-demand, live channels and live content, in one envelope.

  • In the standard

    On demand: renditions in one envelope, packaged into content-hashed pieces.

  • In the standard

    Live channels: attested playback windows that chain into a record of what aired, with session-class manifests, ad-insertion records and key-release records. The demonstration runs the manifest and ad-insertion steps.

  • In the standard

    Live content: signed operation logs that the reference relay verifies at the door and that late joiners re-derive. The browser reaches the relay over a WebSocket.

  • In the standard

    Live rooms over Media over QUIC: several people publish and many watch, every object is checked against its receipt before it is decoded, events are signed and chained per sender, and every sink computes the same layout. Standard encoders and players join over WHIP and WHEP, and each hop signs a record of what it carried.

Shared world-model sessions run on a bidirectional companion relay, reached through a WebSocket bridge. It lives outside the open-standards repository and carries its own licence. The live room's relay is the reference relay in the open-standards repository. Shared world model

08 · Portable rebuild

One source, native and in the browser.

  • In the standard

    The same Rust source builds natively and for WebAssembly; for the integer-exact capabilities both produce the same output hash, which the browser demonstrations check in the page with a 64-bit FNV-1a hash per frame. Receipts commit with BLAKE3.

  • In the standard

    WebAssembly runs the integer kernels single-threaded. High-resolution learned decoding belongs to the decoder a sink registered for that capability.

  • In the standard

    The browser sink builds for wasm32 in CI. Keys, decoder modules and pinned parameter sets carry signing authority and revocation through a key log the origin publishes; a sink that holds the log refuses what it revokes.

09 · Receipts

What arrived, what ran, what it cost.

  • In the standard

    Publisher-signed group receipts: a content hash per object, a Merkle root per group, an Ed25519 signature, and a link to the previous receipt.

  • In the standard

    Decode receipts that separate what anyone holding the codestream can recompute from the energy figure, which only the signer attests.

  • In the standard

    Energy acquisition classes: CalibratedInstrument and OnChipCounter (each with a declared uncertainty), ModelBased, or Estimator. An energy claim signs an object's figure together with its class, and decode receipts carry the class as a signed label. HwShunt is legacy. Work that was not metered carries no figure and reads as not metered.

  • In the standard

    Typed claim classes with an independent verifier, and a soft binding: a receipt reached through it attests the ancestor, never the object in hand.

  • In the standard

    Measurement and operating-point reports on an energy figure, a figure, class and origin bound into each object's Merkle leaf, labelled group totals, power readers that count only while live, and "unmetered is never 0" on every receipt path.

10 · Measurement

How the thesis is measured

Two pages measure in your browser. /cargo measures the bytes, the quality and the decode time of one open-film excerpt as it arrives, and /measure runs the staged-measurement method over its corpus, giving the native tool's figures byte for byte.

  • Byte figures are counted from envelopes in their binary framing, never from the JSON and base64 encodings the demonstrations use.
  • Quality per stage is computed in integers, alike on every target: squared error, PSNR and an SSIM that covers every pixel.
11 · Status

What the standard does

Every capability in the standard, area by area, each linked to its specification text and its conformance: the WAI status page.

12 · Scope

What WAI is, and is not

  • WAI defines no transport and no caching network; it rides existing carriers.
  • Each capability in the codec registry carries a licence class. The registry classes the mandatory floor and the recommended set as royalty-free: each is licensed royalty-free by the body that publishes it. The class records that licence; it is not a finding about third-party claims.
  • The Media over QUIC binding tracks IETF Internet-Drafts.
  • Energy figures cover the work measured, not displays.
  • The specification and the reference implementation are Apache-2.0. Companion implementations carry their own licences.
13 · Read next