Macro 3D Playbook court with an AI agent at a three-path operating junction.
Product system

One playbook. Three operating paths.

Map defines the client-owned Playbook. Build makes its approved Runbooks executable. Control operates and improves the system with visible authority and proof.

Choose the right path
  • Map Define
  • Build Connect
  • Control Operate
Product chooser

Choose where the workflow is now.

Two products and one implementation service. Signal, Decision, and Proof are operator surfaces. They sit inside Control—not as additive licenses.

01 / 03 Define

Make the system legible before implementation.

Map is a standalone subscription for systems, owners, approvals, stops, proof requirements, versions, and handoff.

Standalone subscription CREATE SOMETHING Map

Understand and design one human-agent workflow before implementation.

Request access after workflow scope
  • Living workflow definition
  • Standalone subscription
  • Included with Control
Evidence
  • Living typed definition
  • Useful before or after implementation
  • Included with Control
Receipts
StandaloneRequest access after workflow scope
Explore Map
02 / 03 Connect

Turn the agreed map into an owned implementation.

Build is the scoped service for connecting the approved workflow, its policy boundaries, verification, and handoff.

Implementation service CREATE SOMETHING Build

Turn an approved workflow map into an owned, connected system.

Scoped and quoted separately
  • Scoped implementation
  • Owned system
  • Verified handoff
Evidence
  • Approved definition
  • Connected implementation
  • Operating handoff
Receipts
Scoped serviceScoped and quoted separately
Explore Build
03 / 03 Operate

Watch the signal. Route the decision. Preserve proof.

Control is the governed operating product. It includes Map and keeps delegated work inside explicit authority, approval, evidence, and recovery boundaries.

Standalone subscription CREATE SOMETHING Control

Run Managed AI Operations with explicit authority, approvals, evidence, and recovery.

From $900 per month after launch
  • Inbox / Map / Proof
  • Human approvals
  • Recurring review
Signal Watch the source

Signal captures the incoming change, source, owner, affected system, and reason it matters.

Decision Route the judgment

Decision routes whether the next step can run, must wait, or should stop with a named owner.

Proof Preserve the record

Proof preserves the evidence, decision, outcome, receipt, rollback note, and next owner.

Evidence
  • Signal watches change
  • Decision routes judgment
  • Proof preserves the result
Receipts
Map includedFrom $900 per month after launch
Explore Control
Verified field result

Automation prepared the evidence. Human judgment still decided.

Routine evidence moved before review. Approval, rejection, and consequential action stayed with a named person.

49/ 50
49 of 50 selected cases produced usable evidence packets for human decision.
Workflow
Marketplace template review
Receipt
#FR-2026-01
Verified
May–June 2026
External writes
0
Technical proof

Inspect the discipline beneath the system.

Historical and open tools are evidence, not additional commercial products. Ground and the Loom archive show the discipline beneath Map, Build, and Control.

Historical Proof Loom Archive

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 Ground

Stop hallucinated duplicates. Ground requires verification before claims — no more false positives.

@createsomething/ground-mcp
Apply the system

Start with the workflow your team still protects by hand.

Use Map to define it, Build to connect it, or Control to operate it with approvals and proof. Control includes Map.

Start a private workflow draft Book a mapping session
Owner
Workflow owner
Authority
Human approval
Proof
Map + state + receipt
State
ready