Flavio Riper

A lot of agent projects spend months improving prompts, models, and workflows, then ship to production without asking a few fairly basic questions. Before trusting an AI agent with real work, I'd want clear answers to these:
1. What actions is the agent allowed to take?

Define the boundaries before deployment, not after.
2. Which tools and systems can it access?
Give access based on necessity, not convenience.
3. Are sensitive actions gated by approval?
Not every step needs review, but some decisions probably should.
4. Is there a record of what the agent did?
If something goes wrong, you should be able to reconstruct the sequence of events.
5. What happens when the agent is uncertain?
Low-confidence outputs need a clear path instead of silently moving forward.
6. Can you roll back mistakes?
Every production workflow should have a recovery plan.
7. Who owns the outcome?
At some point, a person needs responsibility for the workflow, even if an agent is doing most of the work.
None of these questions are particularly complicated. What's surprising is how often they only come up after an agent is already running in production.
What would you add to the list before trusting an agent in production?

Two months ago I asked here how people stay aware of what their agents are doing, and @getosmo replied with something that has been quietly rearranging my roadmap since.

I had been treating "can you undo it" as the line for when an agent should stop and ask. He took that apart. Irreversibility over-fires and under-fires, he said. It over-fires on things that cannot be undone but that nobody cares about, like the agent writing a log line. It under-fires on the ones that really hurt: a mass email to 50k users, or a migration you can only roll back after downtime. "Reversible on paper, ruinous in practice."