Shared system base
The shared base of primitives and services that multiple workflows and extensions build on.
Glossary
Stable definitions keep the system legible.
The glossary defines the key nouns explicitly so agents and humans do not have to infer them from context or worldview writing.
Platform terms
Terms about the system itself.
These terms describe how Move Big Rocks is structured.
Shared memory
Durable knowledge, policy, and context that remains available to teams and agents instead of disappearing into local files or private notes.
Bounded extension
An extension that adds focused capability while still depending on shared workspaces, permissions, audit, and work records.
Runtime services
The shared system services that support identity, routing, audit, visible records, and extension behavior.
Work model terms
Terms about the operational work itself.
These terms describe how work moves through the system.
Workspace
The primary operational and security boundary inside an instance.
Queue
A visible bucket for work in motion with ownership and current operational state.
Conversation
A live interaction record that can gather context, resolve directly, or lead into durable follow-through.
Case
A durable operational record for ownership, follow-up, approvals, and auditable closure.
Knowledge
Durable operational context such as runbooks, policies, templates, and shared guidance.
Automation
System behavior that acts on explicit shared records instead of hidden side channels.
Agent and deployment terms
Terms that matter during evaluation and adoption.
These terms describe how humans and agents are expected to use the system.
Agent-visible collaboration
A workflow where agents can inspect and operate against the same records and knowledge people use.
Human approval
A decision that should remain visible to a responsible person rather than being inferred or auto-expanded by an agent.
Self-hosted production model
The long-term deployment posture in which the customer controls runtime, secrets, domains, and production responsibility.
Sandbox
A disposable evaluation environment with the same broad model as production but a lower-trust and time-limited lifecycle.
Authoritative surface
A public page or repository that is explicit about what it is canonical for, such as source, docs, deployment, or machine discovery.
References
Canonical next surfaces.
Each link goes to the next authoritative page, reference, or support surface.
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.