Operator
In one line: It acts on real things, and a human approves before anything irreversible happens.
What it is
An Operator does things on real systems on a person’s behalf: changes a rule, publishes a page, cleans something up. It works out a plan first, and a human approves before anything that is hard to undo.
How one run goes
- Receive a request in plain language.
- Work out a plan: what changes, where, and how to undo it.
- Show the plan and wait for a person to approve it.
- Run the approved steps one at a time, recording each.
- Report what changed and how to roll it back.
An example
A co-worker asks for a stale redirect to be removed. The Operator finds it, shows the exact change and the way back, waits for an approval, makes the change and confirms it is gone.
Where the human comes in
A human approves the plan (what changes, where, how to roll back) before anything irreversible runs.
Use it when
People currently repeat the same actions from a checklist. It is not the right shape when nothing needs approval (that is plain automation) or when the change cannot be undone and the plan cannot be reviewed first.
Watch out for
The tool that changes things is the dangerous part. Keep it narrow and clearly named, and make the approval part of the tool itself, not a polite request in the prompt.
Back to all patterns or the Idea Gallery. A pattern is a shape to borrow when it fits, not a category: the gallery cards do not carry one.