Workspace and team
A workspace is the logical and security boundary inside an instance. Teams define operational ownership inside that boundary.
The core product
Understand the core before you think about buying another category tool.
Move Big Rocks core is already a real product. It gives teams one shared operational model for service catalog, forms, queues, conversations, cases, Markdown knowledge, concept-aware context, automation, and agent access. Extensions add focused depth later. The core is the substrate that makes the rest coherent.
The model
The core is a connected operating model, not a bag of features.
The point of the core is that the pieces reinforce each other. Service catalog classifies work. Forms make it legible by defining what must be known before work is accepted or acted on. Queues route it. Conversations and cases carry it forward. Knowledge guides it. Automation and agents operate on top of the same shared context.
Topic and queue
Topics classify what work is about. Queues show where it is being worked now.
Conversation and case
Conversations handle live interaction. Cases exist when durable ownership or follow-through is required.
Concept and knowledge
Concept specs define structure. Markdown instances hold the actual knowledge and context.
Service catalog and forms
Service catalog and forms are core because they stop everything else from turning into sludge.
Without a clear service catalog and structured forms, requests arrive as blobs and operators, automations, and agents all have to guess what kind of work they are looking at.
Service catalog
Define services, request types, topics, and ownership so work can be classified deliberately.
Structured forms
Capture what must be known before a request is accepted, escalated, or routed.
Better routing
The right team, queue, knowledge, and automations can attach because the work has been classified properly.
Better agent behaviour
Agents do better when they know exactly what information is required and what the work is actually about.
Queues, conversations, and cases
The work model should be simple enough to understand and rich enough to be useful.
Move Big Rocks does not collapse everything into tickets. Queues hold queue items. Queue items can point to conversations or cases. Conversations can resolve without becoming cases. Cases can exist without an originating conversation. That keeps the model honest.
Queues
The current operational bucket with team ownership and visible work state.
Conversations
Live interactions that can gather context, cite knowledge, and resolve without becoming durable work.
Cases
Durable work items for ownership, SLA, approvals, or follow-through.
Unified operator view
Operators and agents should be able to work mixed queue items without losing model clarity.
Knowledge and The Strategic Context Stack
The core keeps knowledge, strategy, and delivery context in the same system as the work.
Markdown is the canonical authoring format, but it is structured by concept specs. That same system holds operational knowledge, RFCs, templates, milestone goals, workstreams, and The Strategic Context Stack so agents and humans can work from the same context.
Private and shared knowledge
Teams can keep drafts private, share with named peer teams, or publish workspace-visible standards.
Versioned concepts
Concept specs define RFCs, templates, constraints, goals, strategies, milestone goals, and workstreams.
Typed references
Markdown can use references like @goal/... and @queue/... while structured metadata holds the canonical graph.
Filesystem workflows
Humans and agents can check knowledge out locally when useful, then sync changes back through the same contract.
Automation and agents
The core should work naturally with agents because it already has a coherent operating model.
A stable mbr CLI and shared GraphQL surface let agents create sandboxes, import knowledge, work queues, reply to conversations, operate cases, and manage extensions without resorting to brittle browser automation or hidden side channels.
CLI-first
The CLI is the main machine contract and should feel predictable to both humans and agents.
GraphQL-backed
The same shared services back the CLI, admin workflows, and extension runtime.
Automation
Event-driven automation sits on top of explicit work and knowledge primitives instead of shadowing them.
Safe leverage
Agents get leverage without bypassing approvals, trust boundaries, or audit.
What core replaces
The core is strong enough to replace a lot before you buy anything else.
Even without extensions, the core can replace a surprising amount of operational sprawl by giving teams one coherent model instead of a docs tool, a form builder, a support inbox, a lightweight backlog, and custom glue all living separately.
Beyond a wiki
Knowledge has access control, concept structure, review state, and links to work.
Beyond a form tool
Forms are tied to catalog, routing, and follow-through — not orphaned submissions.
Beyond a helpdesk shell
Queues, conversations, and cases stay connected to knowledge and forms.
Beyond ticket churn
Milestone goals and workstreams give delivery teams richer coordination units than shallow backlog items.
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.