Map defines the client-owned Playbook. Build makes its approved Runbooks executable. Control operates and improves the system with visible authority and proof.
Two products and one implementation service. Signal, Decision, and Proof are operator surfaces. They sit inside Control—not as additive licenses.
Map starts with a $0 browser-local starter. Its account-scoped workspace adds versions, review, sharing, export, and Build handoff under a separate account workspace · pricing at launch boundary.
Understand and design one human-agent workflow before implementation.
Account workspace · pricing at launchBuild is the scoped service for connecting the approved workflow, its policy boundaries, verification, and handoff.
Turn an approved workflow map into an owned, connected system.
Scoped and quoted separatelyControl is the governed operating product. It includes Map and keeps delegated work inside explicit authority, approval, evidence, and recovery boundaries.
Run Managed AI Operations with explicit authority, approvals, evidence, and recovery.
From $900 per month after launchSignal captures the incoming change, source, owner, affected system, and reason it matters.
Decision Route the judgmentDecision routes whether the next step can run, must wait, or should stop with a named owner.
Proof Preserve the recordProof preserves the evidence, decision, outcome, receipt, rollback note, and next owner.
Historical and open tools are evidence, not additional commercial products. Ground and the Loom archive show the discipline beneath Map, Build, and Control.
Archived MCP coordination work that proved agents need ownership, checkpoints, routing, and recovery. New repo work now uses Linear as the task source of truth.
@createsomething/loom-mcpFree & Open Source GroundCheck TypeScript, JavaScript, and SvelteKit evidence before an agent reports duplicates, dead code, or orphans.
@createsomething/ground-mcpUse Map to define it, Build to connect it, or Control to operate it with approvals and proof. Control includes Map.