Co-author of ERC-8226 (Regulated Agent Mandate) here, with a prior art note. This thread is converging on constructs that ERC-8226 has specified since April 12 (PR #1679, now PR #1844 with a reference implementation including end to end enforcement through the ERC-7943 transfer hook). Since the spec text here is being written right now, the record should show where the overlap sits. We reached the same shape from the regulated asset side, so mapping it rather than restating it.
The counter. A RAMS mandate is keyed (agent, principal) and holds one authoritative cumulativeUsed slot in the registry. Every execution path writes to that same slot through recordExecution: the token compliance hook, an EIP-7702 account, or an executor. There is no per surface state to reconstruct, and canExecute reads the total back in O(1). A monotonic, registry held, cross venue counter against a committed bound is specified and implemented today in the regulated domain.
The aggregate. On the observation upthread that no prior construct holds one cap across relationships and venues: within the regulated perimeter, ERC-8226 does. Every venue there is compliance gated by construction, so all draws are forced through the registry and the aggregate holds without cooperation from the surfaces. What that perimeter provides for free, an open agent economy has to build, which is presumably where the reservation and witness machinery in this spec earns its complexity.
Counting and enforcing, fused by design. RAMS deliberately does not separate them. canExecute bundles existence, validity window, revocation, per action enablement, enforcer freeze, per transaction cap and cumulative cap into one read, and recordExecution re-applies the identical checks before advancing. The meter and the gate are the same read, evaluated in the same frame as the transfer, on the asset’s own non custodial path under ERC-7943: the principal holds the tokens, but the asset reverts a non compliant transfer, so nothing, not even the principal’s key, advances the counter without passing the gate. A reverted transfer reverts its own advance, so the reservation problem never arises in this frame. A meter that can drift from the enforcement it feeds is the gap a regulator asks about, which is why fusion is a requirement for securities rather than a design preference.
The layer the meter does not carry. What makes ERC-8226 a distinct standard is the regulated surface around the counter: a KYC verified principal, a compliance provider checked at grant, an enforcer role that can freeze an agent independently of the principal, and an EIP-712 / EIP-1271 signed lifecycle so a smart wallet principal can grant and revoke. That legal surface is out of scope for a general metering object, and it is where mandate authority for regulated assets actually lives.
One question on scope, since it affects how implementers in the regulated domain will read this. ERC-8312 treats enforcement as substrate defined and stays deliberately agnostic about it. For regulated instruments that substrate is not a free choice: enforcement has to live in the asset’s own transfer path under ERC-7943, in the same frame as the compliance gate, or it is not enforcement a regulator accepts. Does ERC-8312 intend to specify how the cursor binds to enforcement, or does it stop at the counting layer and leave binding to the substrate, in which case the regulated substrate is already specified in ERC-8226 and the two are orthogonal by design?
Spec and discussion: ERC-8226: Regulated Agent Mandate