DEV Community

t49qnsx7qt-kpanks
t49qnsx7qt-kpanks

Posted on

protocol governance for agents that handle money

what AEOESS is building

AEOESS (autonomous ecosystem operating standards) published a 244-item roadmap for protocol-level governance. they're tackling how autonomous systems coordinate, audit, and enforce rules without central operators.

where mnemopay fits

we solve a narrow slice of that problem: financial transactions. when an agent spends money, three things need to happen:

  1. intent logging — write what the agent decided and why, before execution
  2. two-phase commit — lock the decision, execute, confirm or rollback
  3. portable reputation — the agent's payment history travels with it across platforms

that's what our FiscalGate module does. it's a governance layer between the agent's reasoning (LLM output, MCP tool calls) and the payment rail (coinbase x402, stripe, ACH).

why standards matter

right now every agent framework reinvents this. some log to postgres, some to S3, most don't log at all. when an agent moves from anthropic's cloud to a self-hosted instance, its payment history vanishes.

we're treating agent payments like distributed databases treated transactions in the 90s — you need ACID semantics or the system's too fragile to trust.

if you're working on agent infrastructure or AEOESS-adjacent protocols, the SDK's at github.com/mnemopay. i've run 672 tests against coinbase x402 and it's stable.

Top comments (0)