Sui Puts Enforced Spending Limits at the Center of Its AI-Agent Design

TL;DR: A Sui design note argues that agents need permissions enforced by the systems they use. Onchain transactions can support those controls, but cannot establish that an agent’s objective is correct. A useful financial agent needs enough authority to complete a task without repeatedly asking for approval. It also needs boundaries that remain effective if it misunderstands an instruction or encounters misleading information. An October 28 Sui Foundation design note addresses that tension by focusing on enforceable permissions and records that participants can verify. The discussion is a framework for building safer workflows, not an announcement that all AI agents on Sui have become reliable. Instructions and permissions perform different jobs The Foundation’s note argues that boundaries should be enforced by the systems an agent uses, rather than existing only as instructions the agent is expected to remember. It also emphasizes shared terms and verifiable records when multiple organizations participate. That distinction is straightforward in a payment example. Telling software to spend less than a limit is one control. Giving it credentials that cannot authorize a payment above...