Reference

Reference should remain the least narrative and most stable part of the global docs. Its job is to keep product roles, route structure, and documentation boundaries easy to look up.

Product ownershipDocs route modelStable lookup surface

Back To Docs Hub

Page Focus

Reference is the stable map of product responsibilities, route conventions, and core CTK documentation surfaces.

Product ownership

Launcher is authoritative, Reason structures truth, Replay reconstructs outcomes, and Lens projects the scene.

Docs route model

Global docs use shared `/docs` routes organized by Core, Reason, Replay, Lens, Integrations, and Reference.

Stable lookup surface

Reference exists so operators and product teams can quickly confirm where a concept or responsibility belongs.

Questions This Page Answers

Which product owns which responsibility?

How are docs organized globally?

Where should teams look when they need the stable, canonical mapping?

Move across the shared CTK documentation model.

Architecture

/docs/architecture

Getting Started

/docs/getting-started

Integrations

/docs/integrations