BTC moves 4% in an hour. Felora hedges 30% of the exposure into USDC, stops at $2,500 for the day, and never touches a withdraw function because it was never granted one. That rule is called Volatility Shield, demoed at Wednesday's Rialo Builders Hub before a Discord outage cut the session short. The structure behind it runs in three stages: Signal captures the market condition, Predicate verifies the preset rules hold, Execute acts inside restricted permissions. Nothing moves until all three clear. The design decision worth sitting with is where the rules engine lives. It runs locally in the browser and does not auto sign transactions. The agent does the work. The user keeps the keys. Permissions are scoped tightly enough that the agent can perform restricted swaps and nothing beyond that, no withdrawals, no approving new assets on its own. That's a different answer to agent autonomy than most teams reach for. The common instinct is to make the agent smarter and extend more trust to it. Felora makes the agent narrower and extends less, which is the only version that survives a prompt behaving unexpectedly at 3am. @RialoHQ's architecture supports both approaches equally well. What the builders keep choosing tells you something about which one they would actually run with their own money. An agent that cannot withdraw your funds isn't a limited agent. It's the only kind worth running.