Spending policy as an economic-release gate
Consensus-enforced spending policy is a release gate for autonomous economic execution. It is not live on a supported product path today.
Client-side caps are insufficient: a compromised client, alternate RPC, stale read, or concurrent request can bypass them. The required boundary is protocol rejection of any agent-signed transaction outside a registered policy, combined with race-safe accounting and an exact wallet review.
The public design considers limits such as per-transaction and rolling budgets, counterparty and asset allowlists, expiry, revocation, and time windows. Those fields and behaviors are not yet a released contract. Dispute windows also depend on an escrow system that Stele does not expose.
Economic execution remains unavailable until the protocol, SDK, wallet or dedicated local keystore, simulation, state reread, approval, broadcast, and receipt paths clear review together. Stele keeps economic writes and hosted signing disabled.