Fallback
A backup path used when the first choice fails, is unavailable or is not confident — such as a different model, a simpler rule or a person. A good fallback is designed and tested, not an afterthought.
A fallback is what happens when the primary path does not work. In AI systems it can mean routing to another model when the first is slow or down, switching to a simpler rule, retrying with different settings, or handing the case to a person.
Fallbacks improve resilience but complicate evaluation. If a fraction of requests silently fall back to a different model, the quality and cost you measured may not describe what customers get. That is why routing metadata, which shows which model actually answered and whether a fallback occurred, is becoming evidence, and why fallback conditions belong in the runtime address and the serving route.
Decision systems
In a decision system, a fallback is not the same as abstention. Deferring an uncertain case to a person is a deliberate design choice, not a failure mode: uncertainty needs somewhere to go. Test fallbacks as part of the unhappy path, and note how they change model routing.
Read more in The benchmark needs a runtime address.
Related terms
Model routing
Directing each AI request to a particular model or route based on cost, quality, latency or availability, so the model that answers can differ from request to request.
Serving route
The actual path a request takes to be answered — which model, hardware, precision, routing and fallback rules handled it — as opposed to the model name a vendor advertises.
Abstention
A deliberate option for an AI decision system to decline to decide and return uncertain or high-consequence cases to a person, rather than forcing every input into yes or no.
Used in these essays
AI agent governance: what executives must decide first
AI agent governance is a short list of leadership decisions about authority, ownership, evidence and supervision that have to be made before an agent acts.
The most expensive AI mistake may happen after the pilot succeeds
A successful pilot rarely fails at the moment of success. The costly error is the chain of hard-to-reverse commitments the announcement sets off before production evidence exists.
AI agents are exposing your org chart as fiction
An org chart tells you who manages whom. An agent can reveal who actually authorizes a decision, rescues an exception, and carries the consequences.
How to tell if an AI pilot deserves to survive
A pilot earns another investment only when its result can survive ordinary work, a credible alternative, and an owner who can carry it without the pilot team.
Five AI metrics I would remove from an executive dashboard
Licenses, prompts, pilots, hours saved and benchmark scores can all rise while the business stands still. The executive dashboard needs a different contract.
Design systems need an interaction policy layer for AI
Components can keep an AI experience visually on-system while the agent is behaviorally off-policy. Design systems now need reusable rules for what AI may present, decide, execute, defer, expose as uncertain, confirm, reverse and escalate.
Your AI agent can follow the objective and still break the company
AI agents can satisfy a local objective while violating the organization’s broader constraints. The control problem is not only model alignment; it is management design.
OpenAI Decisions API turns probability into policy
The provocative part of OpenAI's Decisions API is not that AI can make choices. It is that a model score can quietly become an action — and an action can quietly become policy.
The hidden metric in AI automation is supervision
As AI moves from assisting work to leading it, hours saved stop telling the whole story. The scarce resource shifts to human supervision: approvals, exceptions, context and judgment.
The benchmark needs a runtime address
AI systems are increasingly dynamic at runtime. Enterprise evaluation should qualify the serving route, harness, tools and fallback conditions, not just the model name.