Aerial black-and-white view of one water-control structure dividing flow across three channels
Product system

Map the system. Control the work.

CREATE SOMETHING Map stands alone as the living definition. CREATE SOMETHING Control stands alone as the governed operating product and includes Map. Build connects the approved system.

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.

  • Living workflow definition
  • Standalone subscription
  • Included with Control
Evidence
  • Living typed definition
  • Useful before or after implementation
  • Included with Control
Receipts
StandaloneMonthly / yearly
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 implementation
  • Owned system
  • Verified handoff
Evidence
  • Approved definition
  • Connected implementation
  • Operating handoff
Receipts
Scoped serviceQuoted 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

Operate delegated work with explicit authority, approvals, evidence, and recovery.

  • 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 includedMonthly / yearly
Explore Control
Outcome Routine work moves. Judgment stays with the operator.

Evidence can be prepared before review while approval, rejection, and consequential action remain with a named person.

Worked example Marketplace template review

The system prepared 49 of 50 selected evidence packets before a human reviewed the templates.

Open product proof

Inspect the discipline beneath the system.

Ground and the Loom archive show the same operating discipline beneath the commercial path: verify before claiming, preserve ownership, and keep evidence with the work.

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.

Map one workflow Talk through one workflow
Owner
Workflow owner
Authority
Human approval
Proof
Map + state + receipt
State
ready