Evaluator
Start with `/docs/get-started`, then `/sandbox` and `/docs/agent-quickstart`.
Documentation
Use the right documentation surface for the job.
The site overview explains the product. The docs should make the next operational step obvious for humans and agents: spin up a sandbox, install the CLI, work with knowledge and queues, build extensions, or move into self-hosted production.
Docs lanes
Pick the lane that matches what you are trying to do.
The docs should be organised by intent, not by repo folders or internal architecture alone.
Operator
Use `/docs/self-host`, `/docs/security`, `/docs/cli`, and the instance-template docs when production matters.
Agent user
Use `/docs/agent-quickstart`, `/docs/cli`, `/site.md`, `/llms.txt`, and the public bootstrap endpoint.
Builder
Use `/docs/extensions` and `/docs/build-extensions` for pack lifecycle and private-extension work.
Move Big Rocks
Use the same deliberate system in evaluation, delivery, and real operations.
The point of the site is to make the next step obvious. The point of the product is to keep your work, knowledge, and agent operating model coherent after the site is out of the picture.