Your move
Route uncertainty to a human
The safest automation knows when to stop and ask instead of inventing certainty.
Stop on missing sources, conflicting records, failed checks, sensitive cases, or work outside the approved boundary. The escalation must include the evidence and the exact decision a person needs to make.
Do this now
Three moves, in order.
- List uncertainty conditions the workflow can observe.
- Name the human owner and the decision they are being asked to make.
- Package the input, sources, draft, failed checks, and open question together.
Build the artifact
Escalation rule
Copy these fields into a note, document, or sheet you already use.
Stop when
Observable uncertainty or risk condition
Send
Input, sources, draft, and failed checks
Ask
The exact human decision
Resume when
Recorded approval or corrected source
Give AI the bounded job
Prompt from your artifact—not from vibes.
Create an escalation packet from this case. Separate known facts, source conflicts, failed checks, and the decision required. Do not solve the uncertainty or conceal it with a smoother draft.
Before you use it
The work leaves your hands only when:
- The owner receives the evidence needed to decide.
- The workflow cannot continue without a recorded resolution.
- The resolution updates the source, check, or boundary where appropriate.