Knowledge model

Keep durable shared knowledge close to the work.

Move Big Rocks knowledge is durable shared memory for teams and agents. It keeps policy, runbooks, templates, and other context connected to the same system that owns work and approvals, so private Markdown and concept instances can become shared context without exposing every source file by default.

Read the core model Read the glossary

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

Shared knowledge and memory

Knowledge is durable context that survives tool boundaries and agent sessions.

Structured Markdown

The site positions knowledge as explicit, machine-legible context rather than an orphaned wiki or a folder that must be shared wholesale.

Connected to work

Knowledge matters because it can guide active operational work, not just sit beside it.

Move Big Rocks

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