Macro-real Playbook court with an ivory AI agent marker at a mapped operating junction, an amber route, and a proof-green terminal.

CREATE SOMETHING Map

Plan the task before you automate it.

Map shows how work moves between people and tools. Use it to decide where AI can help and where a person needs to approve. Start with the $0 browser-local starter without touching production. A short summary can travel to a mapping session.

Open private draft Book a mapping session

Input Prospect map
Boundary No production tools
Handoff Build or Control

Mapping protocol

Decide who does what.

Record the person responsible, what AI may do, when it should stop, and how you will check the result.

01 / Input Prospect map only

The public canvas receives workflow context, never credentials or private records.

02 / Boundary No production tools

The agent can edit the prospect map and nothing beyond it.

03 / Handoff Summary + context

A named map and readiness state travel into the booking path.

Private workflow draft

Map one real workflow before you connect AI to it.

Start with a blank canvas or an industry example. Add the steps, tools, and people involved. The draft stays in this browser and never connects to live systems. You can choose to bring a summary to a mapping session.

Top-down Playbook operating map with ivory owner and source markers, a smoked-metal decision gate, an amber route, and a proof-green terminal.

Mapping warmup

Turn one workflow into a map before booking.

Chat with the constrained mapping agent, shape the canvas, then carry the summary into the mapping session. This public agent can only edit this prospect map.

Map readiness Ready to map

Actor 1Human task 1AI task —System operation —Data artifact 1Constraint —Touchpoint —

45 /100

Workflow map Editable workflow

Run Wait Stop

Actor Wait

Workflow owner system Who owns the workflow and can make the next decision.

Data Unknown

Workflow to map system The operating path that should stop relying on manual rescue.

Human Wait

Approval boundary system What waits for a person before an agent or system acts.

Handoffs 2

Workflow owner → Workflow to map owns
Workflow to map → Approval boundary needs boundary

Mapping agent Shape the workflow map

0/10 messages

45/100 Ready to map 0/20 mutations Anonymous map public map only

Work email (optional) Extends the public mapping allowance. It does not save the map.

Agent

Name the workflow, owner, and first decision. I will turn it into a bounded map with run, wait, stop, and proof points.

Starter maps Choose an industry

Selected node data

Label Owner

Status Connect to

Notes

Booking context Browser draft

Saved only in this browser. Use the authenticated Map workspace for durable versions, review, sharing, and export.

Map workflow summary
Map reference: map_dc5d1ca4f9b5447f
Readiness: Ready to map (45/100)
Recommended next step: Request a workflow map or bring this into a mapping session.
Actor: Workflow owner (wait)
Human task: Approval boundary (wait)
AI task: Not mapped yet
System operation: Not mapped yet
Data artifact: Workflow to map
Constraint: Not mapped yet
Touchpoint: Not mapped yet
Handoffs: Workflow owner -> Workflow to map (owns); Workflow to map -> Approval boundary (needs boundary)
Mapping agent turns: 0
Map edits: 0

Use this in booking

Continue the definition

Save the plan or talk it through.

The browser draft is a starting point. It is separate from a saved Map workspace. The separate workspace is Account workspace · pricing at launch. The workspace adds version history, review, sharing, export, and a handover for Build. You can also bring your draft summary to a mapping session first.

Open CREATE SOMETHING Map Book a mapping session

Owner: Workflow owner
Authority: Human approval
Proof: Map + versions + review record
State: review