Caching & quota policy
95% pre-flight quota gates, singleflight coalescing and verified cache integrity.
On this page 3 sections
#Cache integrity and origin bounds
Weather cache entries embed integrity_version: 1 (internal/capability/weather_cache_json.go). Before serving any fresh, Stale-While-Revalidate (SWR), or Stale-If-Error (SIE) hit, UWA re-validates canonical fields, observation age (≤2 hours), portable IANA timezone, coordinate drift tolerance, and live DecisionEngine.PolicyAllows eligibility—so removing a provider key or policy immediately stops delivery of retained cache entries. Explicit upstream no-store, private, or no-cache directives disable storage. Concurrent identical requests are coalesced via singleflight.Group.
#Fail-closed production quotas
UWA enforces a pre-flight quota gate at 95% of configured budgets. In production and staging, reachable Redis and explicit APP_PROVIDER_QUOTAS_JSON budgets for every configured provider are mandatory; unknown provider IDs or missing budgets fail startup closed.
#Geocoding, history and astronomy caching
Geocoding caching is disabled unless specific providers are allowlisted via APP_GEOCODE_CACHE_ALLOWED_PROVIDERS. Historical reanalysis and astronomy caching are disabled in v1 until upstream storage terms are explicitly reviewed.
docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.