First successful run
Serve the repository on port 9001, verify the adapter, and launch the stack over HTTP.
Platform downloads →Understand the system. Then make it move.
Start with one verified frame, follow the GPU and ECS data paths, and surface the same work through the Playground, Editor, and WebGPU OS. The full Markdown remains directly readable even when the interactive viewer is unavailable.
Engine foundations
Trace the shared GPU device, frame lifecycle, ECS world, and rendering boundaries.
Engine getting started →Architecture map
See how Engine, Editor, Plauna, AGI, and WebGPU OS compose without hiding subsystem ownership.
Read the architecture →Machine navigation
Give an agent the curated discovery index and enriched source-backed ES-module catalog.
Open API catalog →Optional network service
Deploy the separate discovery, admission, encrypted-signaling, TURN, and trusted-node service. It is never gameplay authority.
Master server repository →The documentation is readable before the navigator loads.
This interface reads the canonical Markdown and generated search data directly. If JavaScript is unavailable, use these source routes without losing the setup or architecture path.
Crawler routes: documentation home · llms.txt · llms-full.txt · documentation chunks JSONL · API symbols JSONL · API catalog JSON · XML sitemap. The Companion is optional OS integration; it is not WebGPU compatibility mode and cannot add browser GPU support.