What a waiOS contract will cover.
- Service levels for the parts of waiOS that Transaction Science will run, such as reporting and audit retention, set per contract.
- Support contracts on the WAI reference implementation: integration through its C interface, upgrades across revisions of the standard, and conformance review for teams building their own.
- Deployment of waiOS as a service Transaction Science will run, inside the organisation's own infrastructure, or both. Private registries always sit inside the organisation's own infrastructure.
Open components, each with its WAI label.
- In the standard
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.
Notes 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.
- In the standard
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.
Notes 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.
Planned, in the standard and in the service.
- Roadmap· waiOS
Contracted service levels and support.
What this page does not claim.
- No service level is offered or implied before a contract states it.
- The specification is a Draft Standard. Support follows its revisions; it does not freeze them.
- Support never gates the standard. The specification and the reference implementation are Apache-2.0.