The operator defines what they want: which protocols, how much capital to deploy, what limits to enforce. This is your strategy — expressed in plain terms, not code.
2. Arx compiles bounded instructions
The mandate is translated into a set of specific, bounded instructions. Each instruction names exactly one protocol, one action, and a maximum amount. Every instruction has an expiration. Nothing is open-ended.
3. The keeper executes within bounds
An automated keeper monitors your vault and executes instructions when conditions are met — deploying idle capital, unwinding positions to fund withdrawals, or rebalancing across protocols. The keeper can only do what the instructions allow. If an instruction expires or conditions change, the keeper does nothing.
Capital never leaves your vault
This is the critical point. Arx is infrastructure, not custody. Your vault holds the assets. Protocols receive capital through your vault's adapters and return it the same way. At no point does Arx, the keeper, or any third party take possession of your funds.
