Skip to API documentation
Source observatory / API

Every module tied back to the code.

Browse signatures for people or consume the same catalog as structured JSON. Every enriched record names its source file, source-server import specifier, SHA-256, detected exports, and signatures; summaries appear only where source JSDoc provides them, without pretending this ES-module stack is a REST API.

CATALOG 01

Engine

GPU runtime, ECS, rendering, simulation, math, audio, gameplay, and tools.

Engine JSON →
CATALOG 02

Editor

Scene, assets, viewport, inspectors, project workflow, extensions, and UI.

Editor JSON →
CATALOG 03

Plauna

Retained UI, state, layout, motion, rendering surfaces, and application services.

Plauna JSON →
CATALOG 04

AGI

Training, tensors, observations, rewards, motion, model loading, and Studio.

AGI JSON →
CATALOG 05

WebGPU OS

Kernel, shell, packages, storage, drivers, browser bridge, and extension contracts.

OS JSON →
WebGPU OS Docs
v0.1.0 API JSON ↗

The API remains inspectable without JavaScript.

The interactive browser reads the canonical Markdown, compressed document bundle, and generated reference indexes directly. These machine routes expose the same source hashes and detected exports when scripting is unavailable.

Crawler routes: API guide Markdown · combined API JSON · API symbols JSONL · documentation chunks JSONL · llms.txt · XML sitemap. `llms.txt` is supplemental discovery metadata; linked Markdown, generated catalogs, and repository source remain canonical.