Status · as of

Where waiOS stands

waiOS is not yet operating. This page lists every part of the service, labelled Roadmap, and the open WAI components each part builds on, with the label and notes the WAI status page gives them. Open-component labels are as of the WAI status page dated .

Operating now: none. Roadmap: every service below.

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.

Fleet runtime management

Will keep an inventory of the WAI runtimes in a fleet and what each can decode, and will roll out and revoke parameter sets by digest. The fleet runtime management page

Fleet runtime management: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
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· waiOS —
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. In the standard A runtime host that loads signed modules is on the roadmap.
Capability dispatch with a declared fallback. A sink without the capability reports the file inert. In the standard A fallback decodes the same payload; alternate content travels as renditions.
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. In the standard 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.
A sink bounds the work and memory of every base and every layer, and refuses past each bound before decoding. In the standard —
A host that runs signed, revocable modules. Roadmap· WAI —

Policy

The capabilities, licence classes, determinism tiers and energy budgets an organisation allows will be written once, digested and applied to every runtime and delivery. The policy page

Policy: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
Policy authoring, and distribution to the fleet. Roadmap· waiOS —
A policy-decision record format and its verifier. New work, not in the standard. Roadmap· waiOS —
A licence class for each capability in the codec registry, queryable in code. In the standard The deployer enforces it.
Capability constraint sets, evaluated before dispatch. In the standard Specification text.
Determinism tiers, typed in code. In the standard —
A packaging policy digested over its canonical form, so two spellings of one policy have one digest. In the standard —
Rendition switching in integers, within stated bounds. Under a joule budget the choice is never raised. In the standard —
A payload's cost read from its header, so a sink can refuse by its own limit before decoding. In the standard The header bounds the work; a small payload may describe a large output, and a sink applies its own size policy before decoding.

Energy and carbon reporting

Will total energy from signed figures, each with its acquisition class, and keep carbon labelled as modelled. Per-reconstruction C2PA manifests are in the standard; a report form for totals will be new waiOS work. The energy and carbon reporting page

Energy and carbon reporting: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
Fleet and period energy and carbon reports, in a report form that is new waiOS work. Roadmap· waiOS —
Energy acquisition classes, signed beside each figure. In the standard Unmetered work carries no figure and reads as not metered.
A receipt object's figure, class and origin bound into its Merkle leaf, and a labelled group that signs its total's class, its coverage and the parent link. In the standard —
Measurement claims report on a figure without changing the receipt that seals it, and ratios and verdicts are derived by every reader, never stated. In the standard —
Unmetered work is never a figure of zero joules. In the standard —
C2PA manifest emission binding an energy figure to the one reconstruction it was measured over. The binding forbids presenting a carbon figure derived from a grid factor as measured. In the standard An optional build feature. The manifest validates; signer trust comes from the verifier's trust list.
Energy receipts for origins, hops and relays. Roadmap· WAI —

Private registries

Registries of decoder modules and parameter sets that will run in the organisation's own infrastructure, under its own key log, refusing anything revoked. The private registries page

Private registries: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
Private and on-premises registries, with replication between sites. Roadmap· waiOS —
The normative parameter-set pin. A sink verifies it before decoding and decodes only from the bytes it verified. In the standard A pin that does not resolve makes its capability unsupported for that envelope: dispatch continues at the fallback, and selection at the next rendition.
A key log at a web origin the signer names. Verifiers confirm receipts, claims and module grants against it offline. In the standard —
Decoder and reconstruct modules, and pinned parameter sets, authorised by digest and revoked by digest. In the standard A runtime host that loads signed modules is on the roadmap.
The wire forms a pinned prior may declare, the NNC bitstream among them. In the standard A replicate whose prior declares a wire form the sink cannot read is refused.
The WAI capability registry's machine-readable export, generated from one table and checked for drift in CI, so a private registry names capabilities by their registered strings. In the standard —
Parameter sets, key statuses and grants served over HTTP and checked on every fetch path. Building —
A host that runs signed, revocable modules. Roadmap· WAI —

Audit and compliance

Will retain the organisation's WAI receipts and claims and export them for an auditor to check offline with the open verifiers. The audit and compliance page

Audit and compliance: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
Retention, audit bundles and transparency registration. Roadmap· waiOS —
Typed receipt classes, among them lawful-basis, log-inclusion and delivery-gap, with an independent verifier. In the standard —
A relay cannot splice, replay or hold back a track's receipts unnoticed. In the standard —
Transparency: an external receipt encoding and transparency-service registration, and log-inclusion claims. In the standard A log-inclusion claim carries the log's evidence verbatim; accepting the claim is not verifying the inclusion.
Offline verification of receipts and claims against a key log. In the standard —
One signature rule for every Ed25519 signature WAI defines. In the standard OER/2 keeps the signature rule its own extension settles. The quantum toolkit's receipts are verified by its own verifier, which does not yet apply this rule.
Key-release decision records: every release and every refusal is a signed receipt. In the standard Records decisions; speaks no licence protocol.

Service levels and support

Service levels will be written into each contract, with support on the reference implementation. The service levels and support page

Service levels and support: each part of the service and each open component it builds on, with its status, notes and where it is described
Part Status Notes Where
Contracted service levels and support. Roadmap· waiOS —
The Draft specification freezes the container for 1.x and the manifest schema in a stated sense, and records one deliberate exception; a registered capability's payload format is fixed. In the standard A Draft Standard. This revision makes one exception to the freeze: a member it defines, carried with another JSON type, makes the manifest malformed rather than ignored.
Conformance corpora, fast-kernel equivalence, the OER C kernel and C2PA isolation, run in CI. In the standard —
Byte equality of the integer decode paths, checked in CI on each platform the WAI status page lists. In the standard —
A C interface over the reference implementation (libwai), built as a shared and a static library with a generated header. In the standard Built by the ffi feature, which a default build turns on. Without the codec libraries, CI builds it with --no-default-features --features ffi and runs its envelope tests.

The standard has its own status page.

Every open component above links to its row on the WAI status page, which is dated and covers the standard only.

The WAI status page Ask about design partnership