Mandate Desk

Built with Brickken

An agent requests.
The owner decides.

Review an agent's exact transfer plan, approve it within fixed limits and revoke the mandate when its work is done.

Mandate Desk separates the owner's approval from the agent's execution. Start with the recorded simulation, then inspect the completed Sepolia run.

01 / Recorded walkthrough

See the approval boundary in use.

Local simulation

The recording uses synthetic MDT with no monetary value. It shows the original local app. This page plays the recording and sends no blockchain transactions.

Choose a moment

Each button pauses the video at that step.

What the simulation demonstrates

The local app checks recipient policy, the approved plan and mandate limits before changing its ledger. Its recipient checks are local policy. They are not evidence that the RAMS contract restricts recipients. The Sepolia observations below have their own evidence and scope.

02 / Completed testnet run

Follow the Sepolia transaction trail.

15 September 2026

The saved run contains four Brickken RAMS writes and two ERC-20 approvals through Sepolia RPC. Open each transaction on Etherscan or read the original evidence files.

Six transactions from the completed run
StepSignerRouteTransaction
Enable transfer actionOwnerBrickken RAMS0x4030808d
Approve token allowanceOwnerSepolia RPC0x4f41eab8
Grant mandateOwnerBrickken RAMS0xde8b7680
Execute approved transferAgentBrickken RAMS0x546917db
Revoke mandateOwnerBrickken RAMS0x37fc3394
Reset allowance to zeroOwnerSepolia RPC0x0de6edf8

Limits and revocation

Four saved control observations include cap checks and calls before and after revocation. These are eth_call observations at recorded blocks. They are not failed transactions.

Read the after-revocation observation

Replay handling

The saved replay observation reports no new agent transaction. The agent nonce stayed unchanged during that observation.

Read the replay observation

Finality

The saved finality check reports all run blocks finalized on both read sources at 12:12 UTC on 15 September 2026. This page does not recheck the chain.

Read the finality record
Run scope and disclosed deviation

The final cleanup step used a fetch throttle preload in the owner server process that was outside the run's recorded code identity. One read source recovered from stale finality reporting before the complete export was produced. Later source fixes are a separate revision and do not change this run's approval or code identity.

These records describe one Ethereum Sepolia testnet run. They do not establish production security or general guarantees for every request.

Read the repository disclosure