AI Anonymous retry-planning practice / October 24, 2026

Read retry-plan.py and retry-cases.json first. Python standard library only.
From this directory run: python .
etry-plan.py
Compare with retry-observed-results.json. No API key, network request or sleep occurs.
Fixed clock: 2026-10-24 16:00:00 UTC. Each case is an independent snapshot.
Two additional retries, 30-second total deadline, 0.5-second fixed jitter example.
The repeat_safe flag is authored, not proof a real operation may be repeated.
Only 429/503 are candidate statuses in this deliberately narrow teaching policy.
Missing 429 hint goes to review; missing 503 hint uses authored 1/2-second backoff.
The date parser accepts canonical GMT IMF-fixdate only, not every HTTP-date format.
would_wait is a plan, not a completed retry or promise of provider recovery.
Actual runners need current-clock handling, monotonic deadlines including request
time, per-attempt timeouts, cancellation, random jitter, concurrency limits,
provider-specific errors, stream handling and repeat-safety/idempotency design.
This kit does not implement those systems. Do not wrap a production SDK with it.
Full guide: https://jabsystems.io/ai-anonymous/ai-retry-read-the-signal
