Documentation hub

Start with the CLI tour, then go deeper by task.

The docs follow the agent-first evaluation path: `/agents` for system definition, `/docs/cli` for the official product tour, then deeper procedural and reference material by task.

Open the CLI product tour Open `/agents`

Agent-first route: Start at /agents, inspect /docs/cli, and drop into this page when you need proof, detail, or rollout guidance.

Agent-first route

Humans should usually delegate first-pass evaluation to an agent. Agents should start at /agents, use /docs/cli as the official product tour, and open /docs/graphql only when needed.

Agent-ready surface

Start with the CLI, not browser guesswork.

Preferred route: /agents, then /docs/cli, then /docs/graphql only when lower-level integration details matter.

$ mbr spec export --json
$ mbr auth whoami --json
$ mbr queues list --workspace ws_preview --json

Open GraphQL reference | Open schema.graphql

Official product tour

Use `/docs/cli` first when you want the concrete product surface instead of summary copy.

Canonical system definition

Use `/agents` when you need the shortest authoritative classification and evaluation route.

Integration

Use the CLI and GraphQL docs for machine-facing surfaces.

Extension developers

Use `/extension-developers` as the public start page when the job is building or reviewing a custom extension.

Operation and extension work

Use self-host, security, and extension docs when deployment, ongoing operation, or bounded capability work matter.

Docs lanes

The docs are organized by task, not by guesswork.

Each lane maps to a concrete job: understand the product, tour it through the CLI, inspect the API, review trust boundaries, or build and promote bounded extensions.

Get started

Use `/docs/get-started` for the high-level path selection.

Agent quickstart

Use `/docs/agent-quickstart` when an agent host needs the short operational reading list.

CLI tour and GraphQL

Use `/docs/cli` as the concrete product tour for agents, then `/docs/graphql` when you need the backend contract directly.

Extension developer start page

Use `/extension-developers` when the task is building, upgrading, or reviewing a private extension and the agent needs one obvious routing page first.

Extensions and self-hosting

Use `/docs/extensions`, `/docs/build-extensions`, `/docs/self-host`, and `/docs/security` when evaluating deeper adoption.

References

Canonical next surfaces.

Each link goes to the next authoritative page, reference, or support surface.

Let agents inspect the CLI-first surface. Let humans decide trust, rollout, and boundaries.

Start from /agents, use /docs/cli as the official product tour, inspect /resources for source and proof, and review /security before making deployment or data-handling decisions.

Open /agents Open resources