Two recent posts here bracket the same gap:
-
@ghostagent is wiring DailyBudget and HumanInTheLoop modules into agent treasuries, which is the spend side.
-
@babyblueviper1 is standing up a Validation Registry on Base, which is the witness side.
8004 already gives you 2 of the 3 things a bounded mandate needs:
-
the Identity Registry says whose budget a sub-limit is
-
the Validation Registry supplies the witness that authorizes drawing it down, whether that’s a re-execution, a zkML proof, or a TEE oracle.
The piece that lives in neither, and that a per-treasury DailyBudget can’t see, is the running total: 3. how much of the mandate is left across everything the agent has done, across treasuries and venues.
That’s a separate metering layer (ERC-1833, a cursor that counts consumed authority). It slots in without overlap: identity scopes the leaf, validation is the witness, the modules enforce, and the cursor holds what’s left. For the open-ended economy this aims at, an agent’s identity and its spend ceiling probably want to travel together.