Skip to main content
waiOS · Fleet

Know every runtime in the fleet, and what it may decode.

waiOS will keep an inventory of the WAI runtimes an organisation runs on its devices, servers and edges, and will stage the rollout and revocation of the parameter sets they use. The report a runtime would send for that inventory is new waiOS work; the standard has none.

Roadmap Not yet operating. Each open component below is labelled with where it stands on the WAI status page.

The three labels

In the standard
The open component is in the main branch of the WAI open standard. Its link goes to its row on the dated WAI status page, and its notes are that row's.
Building
The open component is in active development, as the WAI status page lists it.
Roadmap
Planned: a WAI roadmap item, or a waiOS service. Every waiOS service is on the roadmap; none is operating yet.

Attested, in WAI, means signed by the party that did the work and measured it: a reader can check the signature, not re-measure the figure. It is not hardware attestation.

01 · The service

What waiOS will track and roll out.

  • An inventory of runtimes by version, capability set and determinism tier, built from a runtime-inventory report that is new waiOS work. No such report is in the standard.
  • Staged rollout of parameter sets, each authorised by digest under the organisation's own key log, and of decoder modules once a WAI runtime host can load them.
  • Revocation by digest, so every runtime that follows the log refuses a revoked parameter set and falls back.
  • A view of where a capability failed, fell back or was refused, read from delivery telemetry and session claims.
02 · Builds on

Open components, each with its WAI label.

  • In the standard

    Decoder and reconstruct modules, and pinned parameter sets, authorised by digest and revoked by digest. A sink that holds a key log refuses a revoked parameter set and falls back.

    Notes A runtime host that loads signed modules is on the roadmap.

  • In the standard

    Capability dispatch with a declared fallback. A sink without the capability reports the file inert.

    Notes A fallback decodes the same payload; alternate content travels as renditions.

  • In the standard

    Delivery telemetry: player and server reports that point at receipts by hash. They never restate an energy figure, and never carry a URL query, a fragment or credentials.

  • In the standard

    The signed session claim: what a sink presented when, what arrived and what was missed.

    Notes Timings, missed deadlines and switches remain the signer's statements, as do the facts of an encrypted envelope that only its payload shows. A sink that received a multi-rendition envelope only as byte ranges cannot yet state its classical length.

  • In the standard

    A sink bounds the work and memory of every base and every layer, and refuses past each bound before decoding.

03 · Roadmap

Planned, in the standard and in the service.

  • Roadmap· waiOS

    Fleet inventory, staged rollout and revocation.

  • Roadmap· waiOS

    A runtime-inventory report: a runtime's version, capability set, the parameter sets and modules it holds and the key log it follows. New work, not in the standard.

  • Roadmap· WAI

    A host that runs signed, revocable modules.

04 · Limits

What this page does not claim.

  • Delivery telemetry reports what happened in a session: requests, presentations, switches between primary and fallback with their reasons, and capability outcomes. It reports no runtime version, capability set, module inventory or key log.
  • No WAI runtime loads decoder modules yet: a runtime host that loads signed modules is on the WAI roadmap. Until it exists, a rollout covers parameter sets.
  • Telemetry is advisory. It points at receipts and never replaces them.