The docs can answer you now

Documentation has one job: answer the question you actually have, in less time than it would take to give up and email us. Ours didn’t. The pages were honest and the writing was fine, but finding anything meant scrolling a wall or already knowing which page held the answer. That’s not documentation, it’s a filing cabinet with the drawers glued shut.

So we rebuilt the docs on Starlight. Three things changed for the reader:

• Search. Press the key, type “belief decay”, land on the exact heading. It indexes every page, including the generated references.
• A sidebar that’s always there, so you can see the whole shape of the docs and jump sideways — from Concepts to the API reference to the SDK — without going back to a hub.
• A table of contents on every page, including a jump-to-type rail on the SDK reference so you can go straight to the class or interface you came for.

What we refused to trade away is the part that keeps documentation trustworthy: the references are still generated from the source, every build. The API reference is rendered from the live OpenAPI spec — if an endpoint changes, the page changes or the build fails. The SDK reference is generated from the SDK’s own types by TypeDoc. Neither can quietly drift into describing a product that no longer exists, which is the failure mode that makes most API docs slowly untrue.

The brand didn’t move either. It’s the same monochrome the rest of the site wears — same black, same type, no second look bolted on for the docs. A docs engine that arrives looking like a different website is its own small lie about how connected the thing is.

If you’ve been putting off reading the docs because last time you couldn’t find the answer, that excuse is gone. Start here.