The public canvas receives workflow context, never credentials or private records.
Map the workflow before the call.
Use the constrained public canvas to name the owner, data, approvals, systems, risks, and inspection points. The agent can only edit this prospect map; production tools and private systems stay outside the public surface.
- Input Prospect map
- Boundary No production tools
- Handoff Summary + context
Map the channel before work enters it.
Atlas makes the boundary, ownership, stops, and proof requirements visible without touching production systems.
The agent can edit the prospect map and nothing beyond it.
A named map and readiness state travel into the booking path.
See the workflow as a story before editing the map.
The static Atlas story uses the same graph contract as the interactive canvas. It explains what can run, what waits for judgment, where execution must stop, and where proof lands.
Shared graph contract
Story before mutation
The explanatory view and interactive canvas render the same operating model.
Atlas story canvas
Atlas story for Submitted asset packet
The same Atlas graph can teach the workflow to a person and preserve the typed contract an agent needs to act safely.
1. Map Submitted asset packet before execution. Marketplace review owner owns the operating path. The canvas makes the workflow, handoffs, and next decision legible before an agent or system acts. 2. Validator and queue sync can run when the rule is clear. Validator and queue sync coordinates with Supplemental reviewer brief; the map keeps AI assistance bounded to the work it can safely support. 3. Reviewer approval decision stays with a person. Human decides approve, reject, request changes, or escalate policy ambiguity. 4. No ungrounded approval is the stop condition. Stop before approval, rejection, security claims, or timeline promises without evidence. 5. Reviewer dashboard receipt shows the receipt. Shows validation evidence, reviewer state, creator-facing notes, and policy flags. 6. Use the map as booking context for a workflow pilot. The map has enough owner, assistive work, system behavior, and decision context for a first run.
Workflow map 7 nodes / 7 edges
Run Wait Stop
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Public mapping surface
The canvas turns curiosity into booking context.
Cold readers can test the method without exposing credentials. Warm teams leave with a summary, readiness signal, and booking metadata that make the first session sharper.
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
Handoffs 2
- Workflow owner → Workflow to map owns
- Workflow to map → Approval boundary needs boundary