Usage limits

Usage limits govern actions using accumulated history, such as a maximum refund total over 24 hours. Policies refer to named historical facts rather than querying external systems during rule evaluation.

For real enforcement, a matching action may reserve capacity atomically. Concurrent requests then observe the reservation instead of all reading the same stale total. A blocked, rejected, or failed action can release its reservation according to the configured lifecycle; a completed action commits it.

Policy tests are side-effect free. They can evaluate a supplied historical total, but they do not reserve capacity and cannot promise that capacity will remain available for a later live request.