What should an AI agent stop and ask you about?

Which moves cannot be taken back?

Drafts are cheap. Delivery is not. A message sitting in a composer can be rewritten. The same text, once sent, sits in someone else's inbox. A post can be edited later, but the first version is already in feeds and screenshots. A form submitted to a registry, a file deleted from shared storage, or a permission granted to a colleague all leave a trail that a later apology does not erase.

Money has the same shape. A payment, a transfer, a trade, or an advertising spend is not a draft. Access is similar: once a person or a service can read a mailbox or a repository, you are relying on their later behaviour, not on a cancel button. The agent should treat these as a different class of work from research, outlines, and previews. It can assemble the packet. It should not press send on your behalf unless you have been shown the packet and have said yes.

Why pause right before the click rather than earlier?

Stopping too early wastes the agent's usefulness. You already know you wanted a reply drafted, a listing written, or a transfer prepared. The value is in the filled fields, the attached files, the chosen audience, and the exact amount. The pause belongs at the last reversible moment: the composed email, the staged post, the order ticket with limits visible, the delete list with names you can still uncheck.

A late pause also keeps the human decision small. You are not asked to approve a vague plan. You are asked to approve this recipient, this caption, this size, this stop, this daily loss cap. If the agent asks in the middle of drafting, you are guessing. If it asks when the click is the only remaining step, you are checking.

How does GROX decide when to stop and show you a card?

When GROX is about to send, post, pay, call or change something on your behalf, it puts up a card saying what will happen and acts only when you press Approve. You can change the card's words before you approve. Reading, searching and drafting run straight away without a card. Without a card, GROX acts only inside an allowance you set ahead of time or a routine you have switched to autopilot.

For trading, GROX turns a described idea into a strategy you can read, tests it on past prices before any real money moves, and runs it inside limits you set in advance — size per trade, a stop, a daily loss cap — so it asks before it spends. Copying another wallet's buys still requires a confirmation per buy unless you have pre-approved that exact size. A practice mode runs the same strategy with no money at risk. For social publishing, a post to a network reached through a scheduling service is staged for your approval first. Pause, change or stop a running strategy with a sentence.

• GROX puts up a card saying what will happen before it sends, posts, pays, calls or changes something.
• You read the card, edit the wording if you wish, then press Approve.
• Without a card, GROX acts only inside an allowance you set ahead of time or a routine you have switched to autopilot.
• Pause, change or stop a running strategy with a sentence.

When is “just this once” the right default, and when is “always on this site”?

Standing permission is a convenience for reversible chores: filing a note, refreshing a spreadsheet, fetching a calendar. It is a poor fit for anything that leaves your money, your name, or someone else's data in a new place. “Just this once” should be the default for send, post, pay, submit, delete, and grant. “Always on this site” is only sane where a mistake is cheap and easy to reverse, and even then it should be easy to withdraw in a sentence.

Paying should never be pre-approved as a blank cheque. A size you have already named for a single trade is not the same as an open wallet. Copying another wallet's buys still needs a confirmation unless you have allowed that exact size in advance. Practice without money at risk is the place to learn a strategy. Live spend waits. Unusual claims against hardware earnings are held for review for the same reason: irreversible cash should not flow on a quiet assumption.

Just this once

Approve this packet, this recipient, this amount. The next similar action asks again.

Always on this site

Reuse a narrow habit on a cheap, reversible task. Withdraw it in plain words.

Named size, not an open till

A limit you set in advance is a fence, not a signature on every future payment.

Practice first

Run the same rules with no money at risk before anything settles.

Why does a record of every decision matter?

Memory without a decision log is only a diary of outcomes. You need the ask, the yes or no, the limits that were in force, and whether the agent paused. That record is how you correct a habit the system has learnt from your orders and stated preferences. It is also how you stop a follow, a strategy, or a robot job with a sentence and know that the stop did not wait in a queue.

Shared strategies should keep rules public while keeping exact parameters private, and pay a creator only from realised gains. Alpha claims should be scored against real prices at a fixed horizon rather than asserted. Robot work should leave a recording of the path taken next to the machine's own claim. Hire of another agent should be escrowed, paid on completion, and refunded if it fails, with a dispute window. None of that replaces the pause before the click. It makes the pause auditable. GROX is built so trading asks before it spends, staged social posts wait for approval, and a stop never waits — but a simpler drafts-only editor is the better choice if you never want an agent near send, pay, or access at all.