awai.networkNetwork architecture

AWAI NETWORK / ROADMAP

Roadmap

Five evidence gates from published architecture to independent hosting and service economics.

Read the document View source on GitHub

Updated 2026-10-25. Architecture owner: ADR 0015. Tracking: JUN-413 and KOTOBA-73. This is a sequence of evidence gates, not a delivery schedule.

Stage User-visible result Exit evidence Current position
0. Clear boundaries Public documents distinguish artifact delivery, state reads, direct service operations and hosting control. ADR, roadmap, hosting and connection guides merged and publicly read back. This documentation task.
1. Verified dapp release An immutable bundle is discoverable by CID and a stable name points to a qualified release. Pinned source revision, digest/CAR and independent byte comparison, signed release record, browser load, rollback candidate and consent for artifact downloads. Individual pilots, including Dougaka preview; no network-wide contract or production promotion claim.
2. Public read bridge A registered, bounded GET/HEAD view exposes a public Cell or graph projection with source/head provenance. Native valid/invalid fixtures; private/stale/fork/unknown-view rejection; exact response contract; external origin and abuse controls. Design only.
3. Independent hosting Reads and artifacts survive one host failure without losing validation or freshness guarantees. At least two qualified failure domains, Kura retention/repair evidence, signed node identity, Cell lifecycle and recovery readback. Components and local pilots; integrated independent-host proof open.
4. Open service economy External host participation and transparent terms can be offered. Admission, measured capacity/availability, pricing, metering, receipts, disputes and settlement proven end to end. Not an operating service or income promise.

The current node readiness record gives component-level evidence and omissions. Holo comparison is a role map, not implementation compatibility. Source integration, static preview, public HTTPS, native operation and economic settlement are separate results. A production route change requires its own release evidence and approval.