What waiTransport will run on the delivery path.
- Hosted packaging: sources packed under your declared policy, with pieces cut at scene changes, a representation chosen for each piece, and a stage index and a signed receipt for every package.
- Delivery over Media over QUIC, with each refinement layer on its own track beside its receipts track, so a sink subscribes only to the layers it can use.
- Delivery over HTTP, as immutable objects named by their content hash, with HLS and DASH playlists generated from the same package.
- Delivery over one-way bearers (terrestrial broadcast, satellite and multicast), where a receiver has no return path, once a bearer binding exists.
- Relays that forward envelopes and receipts byte for byte, and that record any transform as its own signed step.
- Sessions steered by what each sink declares it can decode and the energy budget it states.
Open components, each with its WAI label.
- In the standard
A packaging policy, read with every refusal named and digested over its canonical form, so two spellings of one policy have one digest.
- In the standard
Pieces cut at scene changes by a streaming segmenter that looks ahead, so a flash or a cut back does not start a piece.
- In the standard
An integer video encoder that writes the pinned video payload, with the step for each piece chosen under the policy's distortion bound.
- In the standard
Packages: a stage index and a signed package receipt bound to the policy it was packed under, a floor checked against its keyframe plan, and HLS, DASH and Media over QUIC views of one package.
Notes Packages carry a base and its floor; refinement layers in packages, rule ladders and other media come next.
- In the standard
Staged delivery: a base first and refinements as separate objects, each linked to its base by hash, with a stated determinism tier per stage. A missing or refused refinement leaves the base intact.
- In the standard
A sink bounds the work and memory of every base and every layer, and refuses past each bound before decoding.
- In the standard
The Media over QUIC streaming format, with one whole single-payload envelope per object and an optional per-object receipt property.
Notes Tracks IETF Internet-Drafts. Each object is one whole single-payload envelope. An energy claim carries an object's class under a signature.
- In the standard
Refinement layers over Media over QUIC: each layer its own track with its own receipts track, so a subscriber caps layers and receipts together.
Notes The binding follows the Media over QUIC Internet-Drafts it names, which may still change.
- In the standard
WAI objects over HTTP, named by their content hash and immutable.
- In the standard
A head a client checks against the content hash before it fetches the rest.
- In the standard
Byte-range fetch of one rendition from a multi-rendition envelope, checked by its digest, with the whole object as the fallback.
- In the standard
Cache rules, with a public driver that checks a cache against them.
- In the standard
Playlists sealed in a receipt and verified strictly, revision by revision.
- In the standard
Unidirectional delivery.
Notes Specification text; no bearer binding.
- In the standard
Relay preservation: envelopes and receipts forwarded byte for byte, with no transcoding, rewriting or re-signing.
Notes A relay attests in a separate, parallel receipt.
- In the standard
A transform recorded as its own signed lineage step.
- In the standard
A package played in the browser: every object checked against the stage index, and every rebuilt frame checked against the native reference.
Notes One open-film excerpt at 256 × 128. Bytes, quality and decode time are measured in the tab; no saving is stated.
In active development in the standard.
- Building
Staged delivery on the measured excerpt: a base first and refinement layers after, every level checked by hash.
- Building
Receipts, key statuses, grants and parameter sets served over HTTP and checked on every fetch path.
Planned, in the standard and in the service.
- Roadmap· waiTransport
Hosted packaging and delivery from Transaction Science.
- Roadmap· waiTransport
Bearer bindings for broadcast, satellite and multicast.
- Roadmap· WAI
Live tracks over Media over QUIC end to end, with live packaging.
- Roadmap· WAI
An edge that evaluates derived tracks and rebuilds or re-packs content under its own receipt.
- Roadmap· WAI
Synthetic pieces packed as instructions the sink evaluates.
- Roadmap· WAI
Energy receipts for origins, hops and relays, and steering that reads them.
What this page does not claim.
- waiTransport will ride existing carriers: QUIC, HTTP and broadcast bearers. WAI defines no transport of its own.
- Hosted packaging will produce what the reference packager produces: a base and its floor, until refinement layers in packages are in the standard.
- No delivery figure (bytes, latency or energy) is stated here until it is measured under the published method.