Policy playground
Write three rules in plain language, watch each compile, fire a demo agent action at the real engine. Seven checks, deny wins, no model in the path. Change one number and watch ALLOW become DENY, then verify the receipt without us.
mandate.max_amount = "500" mandate.asset = "USDC"
mandate.destinations = ["merchant"]
velocity.maxRequests = 20 velocity.windowMs = 3600000
The rules are signed into a mandate by the issuer key, not by you. A cap you write is a cap the agent is held to; editing the mandate afterwards breaks the signature.
the checks stream in here, top to bottom, the moment you fire
Try to bypass the checker
Two locks, not one. Skip our checker and the chain itself refuses. The same transfer, submitted straight to the smart account without a receipt, reverts on Base Sepolia.
This button will submit the transfer above directly to the smart account with no receipt in the signature field. The ERC-7579 validator reverts and the revert is shown here with its Basescan link.
The ERC-7579 validator ships in build stage 4 (EntryPoint v0.7 on Base Sepolia). Until it is deployed this beat stays a designed placeholder rather than a staged revert, because a fake Basescan link would be worse than none.
- the verdict above, from the live engine
- the signed receipt and its offline check
- the registry flag on check 04
- the on-chain revert, coming with the lock