Use cases

The line you don't let an agent cross alone

Every one of these is the same call with different words in it. What changes is who you send it to and how long they have.

Support

Refunds above a threshold

A support agent can answer, apologise and log all day. The moment it wants to move money, it asks the person whose budget it is.

What the human sees

Refund $840 to order 1183? Customer says it arrived broken; photos attached to the ticket.

Approve refundAsk for photosDeny
Growth

Anything that goes out under your name

Cold email, a reply to a customer, a post on the company account. The draft is the agent's; the send is a person's.

What the human sees

Send this 240-contact sequence? First touch drafted below.

Send itHold for edits
Engineering

Deploys and migrations

Let the agent build, test and stage on its own. Gate the one command that reaches production, and record who waved it through.

What the human sees

Promote build 4f21c9 to production? 3 migrations, one of them drops a column.

Ship itNot now
Infrastructure

Destructive operations

Deleting a bucket, rotating a key, tearing down an environment. The kind of action where 'the model was confident' is not an acceptable postmortem line.

What the human sees

Delete staging-db-07 and its snapshots? Last write was 46 days ago.

DeleteKeep itSnapshot first
Finance

Spend a wallet can't argue with

An agent holding a card or a crypto wallet needs a ceiling it cannot reason its way past. Put a person above the ceiling.

What the human sees

Buy 12 months of the $4,800 plan? Cheaper monthly for the first 5 months.

ApproveMonthly insteadDecline
Operations

Escalation with a deadline

On-call gets a Telegram message with two buttons and an hour to use them. No answer means no, and the runbook takes the safe branch.

What the human sees

Auto-scale the cluster 3× for the traffic spike? Est. $190 for the day.

Scale upRide it out

Two credits to find out.

Send one to yourself and watch the whole loop close.