Chiron documentation
Everything Chiron and the Ontology Layer can do, grounded in the real system.
Chiron turns your repositories, documents, decisions, and databases into one graph your team and your agents share. These docs explain how that graph is built, how you query it, and how the surfaces on top of it — Manager, Engineers, Memory, and chat — put it to work.
They are written for two readers at once: the person deciding whether Chiron fits, and the engineer who has to integrate it. Nothing here is marketing shorthand — every API shape, source, and behavior is the one the system actually ships.
Where to start
If you are new, read What is Chiron? then follow Getting started. If you are evaluating the platform technically, jump to The Ontology Layer and the Knowledge API.
How these docs are organized
- The Chiron Model — the mental model: projects, Work Orders, and why we model an ontology rather than an index.
- The Ontology Layer — the one contract every source flows through: discover, search, fetch, activity.
- Surfaces — Manager, Engineers, Memory, and project chat, one page each.
- Knowledge API & MCP — the exhaustive reference a technical reader can predict real responses from.
- Recipes — goal-shaped walkthroughs that cross the surfaces.
Use the search button at the top of the sidebar to jump straight to any page by title or heading.