Documentation hub
Choose a lane before opening the reference.
The Starlight reference stays deep and searchable. This hub groups the docs by reader intent: get oriented, configure a workspace, understand the engine, integrate the API, operate a deployment, or plan the next implementation step.
Run OAH locally, learn the product boundary, and understand the vocabulary used across the docs.
02 Configure a workspaceReview runtime templates, settings, prompts, agents, models, skills, hooks, MCP servers, and validation rules.
03 Trace the engineFollow lifecycle, context construction, message projection, queue reliability, and worker ownership.
04 Integrate through the APIBrowse OpenAPI resources, streaming events, schemas, actions, storage, and model contracts.
05 Operate deploymentsMove from embedded worker development to split deployment, Kubernetes rollout, readiness checks, and runbooks.
06 Plan the roadmapTrack product maturity, implementation stages, worker scale, and the next maintenance decisions.
Maintenance map
Keep each page close to its owner.
The product pages are intentionally shallow. Durable technical detail still belongs in Starlight, but the sidebar now mirrors ownership: workspace configuration, engine internals, API contract, operations, and roadmap each have their own shelf.
Next paths
Leave the hub with a purpose.
Each product entry leads to a different maintenance question. Use these paths when the current page is too broad.
Use the architecture map when you need to decide which subsystem owns a change.
API Check client contractsUse the API entry when a WebUI, TUI, Desktop, or integration behavior depends on the runtime contract.
Operations Move toward deploymentUse the operations lane when a local behavior needs production, Kubernetes, or runbook treatment.