What counts as proof?

Proof means delivery records, tools, connectors, and client builds that show which signal arrived, who decided, what evidence was used, what changed, what stayed private, and what still needs an owner.

Why are Ground and Loom MCP included?

Ground shows the verify-before-claiming discipline, while Loom MCP shows why long-running agent work needs ownership, checkpoints, and handoff evidence.

How does proof become a client workflow?

The paid work turns proof primitives into scoped actions, approval states, blocked-state receipts, and an operating path the client can inspect.

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

Product system

One workflow map. Three places to operate.

Atlas maps the workflow. Signal watches changes. Decision routes judgment. Proof keeps the record. The map defines the boundary; the three operating surfaces keep responsibility visible.

Map one workflow Talk through one workflow

Atlas Map
Signal Watch
Decision Route
Proof Record

System anatomy

One map coordinates three operating surfaces.

Atlas holds the map. Signal watches, Decision routes, and Proof records. Substrate is the Foundation underneath; Map / Pilot / Operate is the delivery method.

Product system

Atlas → Signal / Decision / Proof

Map the work once, then watch the change, route the judgment, and preserve the record.

Product overview

The product line follows the workflow.

This page is the index: each product surface has one job, a clear owner, and a visible relationship to the others.

Atlas Map the workflow

Atlas shows where signals enter, where decisions pause, and where proof records the outcome.

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.

Supporting proof

Framework and tool proof sit under the product system.

Ground and Loom MCP are evidence of the same operating rule in public: watch the signal, verify before deciding, 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.

Historical proof for agent continuity
@createsomething/loom-mcp
Linear-first coordination

Free & Open Source

Ground

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

Code analysis that checks before it claims
@createsomething/ground-mcp
Instant setup

Apply the proof

Apply the proof to the workflow your team still protects by hand.

I’ll map the first workflow, identify the safest signal source, define who decides, and name what proof the control layer should leave behind.

Map one workflow Talk through one workflow

Owner: Workflow owner
Authority: Human approval
Proof: Map + state + receipt
State: ready