Rate-Limit Response & Retry-After Interpreter

• 01Parses non-negative delay-seconds plus current and legacy HTTP-date wire forms without accepting ambiguous platform date strings.
• 02Uses a valid response Date as the HTTP-date reference when supplied and otherwise labels local-clock provenance explicitly.
• 03Interprets configured rate-limit statuses while requiring a safe method or caller-owned replaySafe evidence before producing a wait outcome.
• 04Supports one provider reset header only when its name and delay or epoch unit are configured explicitly; standard Retry-After takes precedence.
• 05Keeps missing, malformed, expired, excessive, provider, and explicit fallback timing distinct while leaving quota unknown and automaticRetry false.
• 06Returns deterministic deeply frozen value-minimized decisions, policy findings, typed validation errors, and a non-mutating preserve-first integration plan.

• 01Browser and server teams consuming APIs that return 429, 503, Retry-After, or documented provider reset headers
• 02Floot, React, Next.js, Node.js, and plain JavaScript projects that need explicit recovery evidence without replacing transport
• 03AI and automation clients that must stop guessed or immediate retry loops while keeping replay and provider policy host-owned

This listing is a downloadable Genesis code package. The ZIP includes reusable code and START-HERE directions.

1. 01

   Checkpoint and document provider evidence

   Record the exact source and deploy revision, preserve the current request contract, and document only the statuses, standard headers, provider reset semantics, clocks, and replay decisions the host can verify.

2. 02

   Integrate at one response boundary

   Call the interpreter only where the existing client classifies response errors, map its outcome into existing controls, and stop if the change would replace transport, retry a mutation without proof, or alter unrelated behavior.

3. 03

   Test and publish separately

   Run package, missing, malformed, excessive, clock, provider, replay, cancellation, idempotency, UI error-state, regression, production-smoke, monitoring, and rollback checks before deployment.