Updated 2026-10-25. ADR 0015 defines the Web Bridge read role; hosting postures and node readiness track implementation evidence. AWAI Network, L.L.C. operates its hosted service surfaces. Kotoba Foundation owns the open language/runtime/specification direction; this document does not transfer legal ownership or grant host enrollment.
| Service role | What it supplies | What it does not supply by itself | Position |
|---|---|---|---|
| Static app and artifact delivery | HTTPS delivery of a verified immutable release through a stable location; CID and file digests identify the bytes. | Browser workflow, per-user API, app command execution or permission to call another service. | Existing static sites and CID pilots; release registry/promotion gate in progress. |
| Awai Node hosting | Machine resources, placement/observation and a selected runtime for qualified service/Cell workloads. | Cell author identity, grant, native qualification or public host admission. | Local/component evidence; independent always-on operating claims require separate proof. |
| Kura and Yataverse | Retention/repair evidence and CID-addressed bytes. | App validation, verified head, private-data policy or an HTTP query result. | Distinct components; integrated service availability gate open. |
| Awai Web Bridge | A narrow public GET/HEAD view with source/head provenance, backed by verified app state or projection. | Arbitrary node proxy, write API, inference, payment, hosting control or browser consent. | Contract design; no live integrated endpoint. |
| Direct application services | Murakumo inference, Aozora PDS/AppView/XRPC and other declared services chosen by the app. | An implicit shared authorization. Each browser operation needs fresh approval; bots use separate grants. | Product-specific implementations and qualification vary. |
An operator can publish a static dapp without offering a Cell or Web Bridge view. A public view requires an allowlisted schema, public-data policy, source identity, verified head, bounded query cost and response proof. Host capacity and HTTPS reachability do not satisfy those requirements. The future Web Bridge service will be on an origin separate from the static app origin; bridge.awai.network is a proposed name only.
No general external-host signup, availability SLA, published price, automatic host payout or market settlement is offered by this document. Participation begins with the current guide and the node setup preview; readiness and terms must be checked for each role. Holo's EdgeNode and Web Bridge descriptions inform this role separation without implying Holochain interoperability.