What waiTransport will host.
- Decoder modules and parameter sets, each addressed by its digest.
- Each artifact authorised by its signer, under the key log that signer publishes at its own origin, and revoked by digest, so a sink that holds the log refuses a revoked parameter set and falls back.
- Artifacts served close to the sinks that fetch them, on the HTTP serving rules WAI is building, with availability set in each contract.
- Curated entries: each hosted artifact passes the conformance check for its capability's class before it is listed.
The capability registry stays open
The WAI capability registry lists capability strings and identifiers. It is public, any runtime reads it and its exports with no account, and its terms are never tied to waiTransport. It holds no decoder modules and no parameter sets, and no public registry of those artifacts exists today. waiTransport's registries will hold them under the pin and grant rules WAI defines, so a sink checks a hosted artifact exactly as it checks one from any other origin.
Open components, each with its WAI label.
- In the standard
The normative parameter-set pin: one SHA-256 over a whole parameter set. A sink verifies the pin before it decodes, and decodes only from the bytes it verified.
Notes A pin that does not resolve makes its capability unsupported for that envelope: dispatch continues at the fallback, and selection at the next rendition.
- 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 its dispatch falls back.
Notes A runtime host that loads signed modules is on the roadmap.
- In the standard
A key log at a web origin the signer names: revisions under a root key that pre-commits to its successor, each key's authorities and its status, confirmed offline.
- In the standard
One rule for every Ed25519 signature WAI defines, applied by the reference verifier and an independent one.
Notes 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.
- In the standard
The model a neural payload needs is named, pinned by digest and never carried in the envelope; a pinned prior can declare its artifact's wire form, and the NNC bitstream is registered as one.
Notes A replicate whose prior declares a wire form the sink cannot read is refused.
- In the standard
The WAI capability registry: every registered string in one table, with a machine-readable export generated from it and checked for drift in CI.
In active development in the standard.
- Building
Parameter sets, key statuses and grants served over HTTP and checked on every fetch path.
Planned, in the standard and in the service.
- Roadmap· waiTransport
Hosted, curated decoder and parameter-set registries from Transaction Science.
- Roadmap· WAI
A host that runs signed, revocable modules.
What this page does not claim.
- No public registry of decoder modules or parameter sets exists today. The standard defines how such an artifact is pinned, authorised and revoked; serving artifacts over HTTP is being built.
- No WAI runtime loads decoder modules yet: a runtime host that loads signed modules is on the WAI roadmap.
- Hosting an artifact does not change its licence. The capability registry records each capability's licence class; it is not a finding about third-party claims.
- Availability is set per contract. None is offered before the service opens.