Skip to content

Begin typing to search this documentation.

Hodos

Open world ABI · browser + Hara

One world format.
Many engines.

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.

Semantic kernel
Hara
Host
Standards-based web
Projection
Replaceable adapters

01 / Layers

A narrow centre.
A broad ecosystem.

Hodos stays durable by standardising the boundary between world meaning and host capability. Product choices remain outside that centre.

Above Hodos

Experiences and engines

Worlds, games, viewers, editors, studios, renderers, physics, avatars, AI, multiplayer, discovery, publication, and commerce.

Hodos

Portable world contract

World definition, Browser–Hara messages, capabilities, lifecycle, engagement, profiles, and conformance.

Below Hodos

Execution and hardware

Hara, WebAssembly, browser APIs, permission systems, operating systems, devices, networks, chains, and wallet custody.

02 / Invariants

Meaning crosses.
Objects do not.

The world sees stable values and explicit authority. The host retains implementation objects and enforces the boundary.

  1. 01Serializable meaningNo DOM, GPU, audio, file, key, or wallet objects in Hara state.
  2. 02Explicit authorityDevices, storage, networks, identity, signing, and transactions are capability grants.
  3. 03Replaceable projectionA world does not require one renderer, source, UI toolkit, or storage vendor.
  4. 04Semantic engagementPointer, touch, gaze, voice, controller, accessibility input, and agents can express the same intent.

03 / Reference implementation

The existing world still runs.

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.