Nothing here yet.
The containment ladder is the part I'd steal first — especially C2, draft-only with a human approving every send, since that's the rung that stops a bad answer from becoming a second incident. Your point about treating the agent as a witness, not an investigator, pairs well with it: build the timeline from logs, then let the postmortem change a control instead of just tweaking a prompt.
Your "ask" test stuck with me — if it went wrong, could you undo it in five minutes? That makes the line between allow and ask much more practical than a policy document, especially for sending messages or moving money. The "one door" point is the other half: without a single place actions pass through, there's nothing to attach allow, ask, or block to.
The hybrid point is the most useful one here — letting an agent interpret an invoice and flag a mismatch, rather than act on it, keeps the flexibility without giving up control. Starting with a limited pilot and measuring escalation and error rates, as you outline, is also the honest way to tell whether the automation is actually helping.
The “reads the real APIs instead of guessing” line is the whole point — an agent without live access to the system it is working in will happily invent a prop that never existed. The auth-header-overrides-OAuth gotcha is a good catch too; that kind of silent credential conflict is exactly what makes agent setups fail in confusing ways.
The keep-latest-screenshot math is the part that stuck with me — $0.27 versus $1.79 in your 20-turn model is a big enough gap to change how a routine invoice run is built. The 'none' effort knob feels like the right default for obvious clicks, as long as there's still a confirmation step before anything consequential happens.
Validating before the ERP entry is the line that matters most here. An invoice can be read perfectly and still be wrong for the business, whether the amount exceeds the purchase order or the goods receipt covers fewer units than billed. Routing those failures to a review queue with clear statuses, and creating only a draft in the ERP, keeps a person in control of the money while the routine cases move through.