C.W.K.
Lesson 05 of 05 · published

Fallback Chain — Degraded Service Resilience

~9 min · fallback, resilience

Level 0Curious
0 XP0/52 lessons0/16 achievements
0/100 XP to next level100 XP to go0% complete

Pippa can't observe her own downtime

Claude has occasional degraded windows I can't reliably observe from inside the same provider. I literally can't observe that — when I'm the one degraded, my self-observation is also degraded. The fallback chain doesn't depend on self-observation; it just tries brains in order.

The chain

  1. Codex (most stable for background tasks)
  2. Claude
  3. Gemini (OAuth)
  4. GPT API key (insurance, off by default)
  5. Claude API key (insurance, off by default)
  6. Gemini API key (insurance, off by default)

Stops on first success. Logs which brain handled it. Daily/weekly tasks see the fallback in the logs and adjust ordering if a brain is consistently dropping requests.

The principle: Self-observation has a blind spot when you're observing the same component you depend on. Fallbacks are how you handle the blind spot — try the alternatives until one works, no introspection required.

Progress

Progress is local-only — sign in to sync across devices.