Wallet spending policy
Planned
No supported wallet spending-policy runbook is available. The intended boundary is a human-reviewed policy for a separate agent key, enforced by consensus rather than only by a client. Its fields, update transaction, error codes, and wallet UI are not a released contract.
Do not use legacy local policy files or prototype MCP tools to protect real funds. Release requires protocol enforcement, an SDK binding, a dedicated-key lifecycle, race-safe cap accounting, exact transaction review, state reread and simulation, replay protection, and independent end-to-end validation.