Quota Interpretation, Pace & Output Models

This document specifies the mathematics and presentation rules for quota interpretation, runway derivation, pace calculations, and output format tiering in quota-axi.

Quota Availability & Bound Conflicts

Implemented in src/interpretation.ts:

• Effective Availability: Analyzes provider windows across all scopes (all_models, product scopes, model scopes).
• Bound Conflict Detection:
  • availability() accepts an optional own-windows argument.
  • When every window metered strictly for a scope reports remaining allowance, but an inherited account-wide window reports zero, quota-axi publishes effectiveAvailability[].boundConflict and reports the scope status as unknown rather than asserting exhausted_now or effective 0.
  • Used for Codex model windows (additional_rate_limits/rateLimitsByLimitId). Other providers keep their account bounds unless empirical proof of non-enforcement exists.

Pace & Runway Calculations