Enforcement guarantees

Planned capability

This page describes a proposed management contract, not a setup procedure. Current request behavior is documented in the Gateway API reference.

Proposed shared counters

A hard organization-wide ceiling would require one authoritative counter for each budget scope and window. Admission would need to reserve atomically against every applicable block budget. Eventual device synchronization would not prevent simultaneous requests from spending the same remaining amount.

Proposed reservations and settlement

Before forwarding, admission would need a bound on final cost, including output limits and pricing. Completion would settle actual usage and release unused reservations. The contract would need to define retries, cancellation, incomplete responses, unknown prices and orphaned reservations.

Proposed failure policy

A hard ceiling would require refusal when accounting or the necessary cost bound were unavailable. Fail-open, downgrade and alert-only configurations would permit spending beyond a threshold. Current path-specific behavior, including counting-backend failure, remains governed by Policy and enforcement boundaries.