Map the work before you automate it.

Name one repeated job and put its steps in the order they happen. You get one grounded repair, one human gate, one honest unknown, and one receipt to collect.

Built locally. Nothing connected, sent, or stored.

The job

Keep it to one repeated job.

What repeated job are we mapping?500 character limit. Do not paste private details.

Where does it begin?Where does it end?

Start and people

Name the trigger and the handoffs.

What starts it?What must be ready?

OwnerOther peopleWho receives the result?

The path

Add each use in order. Repeat a tool when the work returns to it.

0 / 10 stepsThese are labels only. No tool is connected.

Other tool or step

Add the first step to draw the path.

Load and friction

Use your own estimate. The map does not invent savings.

How often?Items per runHands-on timeWait time

Source of truth

Where does information get handled again? Copy or retype Download or upload Wait for a person Find the current record

Worst wait, break, return, or exception

Result and proof

Define what comes out and what proves it worked.

Expected outputSuccess measureReceipt to keep

Name a job and add a step to build the map.

Finder questions

How does the workflow finder build my map?

It matches your ordered steps and one repeated job against a reviewed local pattern library. The map is built by fixed rules in your browser, with no model call.

Is anything I type sent or saved?

No. Slice 1 does not send, store, or connect anything. Raw credentials, private URLs, health details, financial-account details, and identifying contact information are refused.

Does a line between tools mean they integrate?

No. A line only records the order you entered. Every tool remains a label until a later diagnostic verifies permissions and connector behavior.

What should I do with the receipt?

Collect it on the next real run. It gives you evidence to confirm the map, revise the repair, or stop before building the wrong automation.