Policies, approvals and audit
Control Tool execution and retain evidence without confusing permissions, usage and external effects.
Put decisions at the execution boundary
Governance supplies Tool policy decisions, approval records, timelines and post-execution usage tracking. Trusted application code configures these controls; model instructions are not an authority boundary.
- Tool policies: deny, automatically allow or require a human decision.
- Approval requests and decisions: bind a reviewed decision to its pending operation.
- Timeline and usage records: retain history and accounting.
Keep different guarantees separate
An approval is not authentication, a usage record is not a spending limit, and an audit event is not proof that an external system rolled back. Use Authentication for verified identity and inference budget admission for spend control.
Your application owns reviewer permissions, resource policy, retention and recovery. In-memory reference implementations do not establish durable or distributed guarantees.