# Operate a buyer within explicit limits

Keep spending controls, private evidence and recovery state in trusted application code.

Canonical: https://402signal.com/developers/operating-limits

## Keep enforceable policy outside the model

Use this when you own the wallet policy or approve an agent-platform integration. Let the model propose a task. Trusted application code supplies enforced limits, recipient allowlists, key pins and signing authority.

402Signal evaluates submitted requirements. It cannot know that the model changed an organization's approved policy before submitting them. The local guard cannot protect a caller that bypasses it. Save observation evidence, approved policy and execution records under operator-controlled retention.

Request human approval before the final fresh check where needed. Approval does not permit ignoring expiry. A stopped operation must not fall back to unguarded payment.

The service's destination-change handling is not a permanent organization-wide recipient allowlist. Pin approved recipients in the buyer when required. There is no hosted approval queue, delegated signer, escrow, delivery guarantee or dispute-resolution service.

Published client bounds and shared storage are not a throughput certification or a service-level agreement. Confirm workload access and operating limits for your integration.

[Data and retention boundaries](/how#data-boundary) · [Uncertain outcomes](/developers/recover-routing-attempt) · [Private security contact](/contact#security).