The first question every CFO asks isn't "how accurate is it." It's "what happens when it's wrong."

Fair question. Agents in finance are still new enough that nobody trusts them by default — and they shouldn't. The work matters too much.

What we mean by reversible

Every action Maya takes is logged with the inputs that produced it, the rule or model that decided it, and a one-click way to undo it. If Maya posts a journal entry that turns out to be wrong, you don't restore from a backup. You click "reverse" and the entry is unwound, with its own audit entry explaining what happened.

This sounds basic. It is basic. It also doesn't exist in most agent platforms today, which is why their auditors get nervous.

Why we built it this way

We've spent enough time in finance teams to know how the conversation goes. The controller likes the demo. The CFO is interested. Then the auditor walks in and asks, "How do I prove what happened in March?"

If your answer involves digging through logs across three systems, you've already lost.

The reversible action log gives auditors one place to stand. Every Maya action, every input, every override — chronologically, queryable, exportable. They don't have to trust us. They have to trust the log.

What it changes

Reversibility lowers the cost of saying yes. You don't have to be 100% sure Maya should handle a workflow before you let it. Run it on a slice, watch the log, reverse anything that looks off, and expand from there.

That's how trust gets built in finance. Not from accuracy claims in a sales deck, but from a month of watching the system do exactly what it said it would.

— Elin