1. Query the bootstrap
Start from the public bootstrap endpoint instead of scraping the whole site.
Agent-first operations
Give agents one explicit operating contract instead of a mess of side channels.
Move Big Rocks is designed so capable agent hosts can install the CLI, discover the bootstrap contract, create sandboxes, work knowledge, and operate queues and cases without scraping random pages or reconstructing context from scattered tools.
Agent flow
The intended workflow should feel obvious.
A good agent flow starts with discovery, moves into one installed CLI, and then stays inside the same contract for setup and operation. If the agent wants a simpler public documentation surface first, it should also be able to use /site.md and /llms.txt.
2. Install mbr
Use machine-readable install metadata and signed release information.
3. Create or target a runtime
Spin up a sandbox or point the CLI at an existing instance.
4. Operate with proof
Work from milestone context, knowledge, queues, conversations, cases, and extension surfaces through one contract.
Why it matters
The point is not agent novelty. The point is better operations.
When agents can understand the same strategic context, milestone artefact, knowledge, forms, queues, and work records as humans, they become much more useful and much less dangerous.
Fewer hidden assumptions
The context is in the system, not just in one engineer's head.
Less ticket theatre
Agents can work from milestone goals and workstreams instead of being spoon-fed shallow tickets.
Better proof loops
Agents can reconcile what is proven, open, and blocked against the milestone artefact.
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.