Experiences and engines
Worlds, games, viewers, editors, studios, renderers, physics, avatars, AI, multiplayer, discovery, publication, and commerce.
Open world ABI · browser + Hara
Hodos defines how a world is packaged, loaded into Hara, connected to browser capabilities, and engaged by people and agents. Rendering, physics, editors, storage, and wallets remain replaceable.
01 / Layers
Hodos stays durable by standardising the boundary between world meaning and host capability. Product choices remain outside that centre.
Worlds, games, viewers, editors, studios, renderers, physics, avatars, AI, multiplayer, discovery, publication, and commerce.
World definition, Browser–Hara messages, capabilities, lifecycle, engagement, profiles, and conformance.
Hara, WebAssembly, browser APIs, permission systems, operating systems, devices, networks, chains, and wallet custody.
02 / Invariants
The world sees stable values and explicit authority. The host retains implementation objects and enforces the boundary.
03 / Reference implementation
This first reorganisation adds the specification and site boundaries without relocating the working runtime. The current PlayCanvas, GitHub, Hara, OPFS, Web Audio, authoring, publication, and Studio stack remains the reference implementation while adapters are extracted incrementally.