# Fail closed

Failing closed means that when a component cannot do its job, the system refuses to proceed. Nicholas Hopper applies it at every boundary with a language model, so that a model outage or an unparseable response produces a refusal and never a silent pass.

- **Published:** November 17, 2026
- **Updated:** November 17, 2026

## Where Nicholas Hopper applies it

At APX Stream, Hopper made several parts of an LLM pipeline refuse instead of guess:

- **Planner.** A planning step judges which retrieved sources are relevant before any answer is drafted. If its response cannot be parsed, that counts as a refusal.
- **Judge.** An LLM-as-judge check tests whether each drafted answer is entailed by its sources. If the judge is unavailable or its output cannot be parsed, the draft is flagged. It is not passed.
- **Gateway.** The model gateway refuses to start when a provider credential is empty or still a placeholder.

Hopper then wrote fail-fast into the team's technology standard as a principle, so that new services inherit it.

## The cost

A system that fails closed refuses more often, and each refusal needs a person. Hopper accepts that cost where a wrong answer would be read as authoritative.

## Related skills

- LLM-as-judge
- [LiteLLM](https://nicholashopper.com/skills/litellm.md)
- [LLM evaluation](https://nicholashopper.com/skills/evals.md)

---

Canonical page: https://nicholashopper.com/notes/fail-closed  
Last updated: 2026-11-17  
Index of all pages: https://nicholashopper.com/llms.txt
