How Complex Systems Fail (1998)
- ID
- 17152
- Status
- summarized
- Published
- 23 Aug 2026, 11:13 PM
- Fetched
- 25 Aug 2026, 12:24 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://how.complexsystems.fail/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 25 Aug 2026, 12:25 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Richard I. Cook's 1998 treatise lays out principles of how complex systems fail, arguing that all interesting systems are intrinsically hazardous, heavily defended, and run in degraded mode with latent flaws. Catastrophe requires multiple small failures to combine — single-point failures are never sufficient on their own. The system continues functioning because of redundancies and human workarounds, not because it is flawless.
Why it matters
If you ship AI agents or multi-service systems, this reframes your incident response: stop hunting for 'the root cause' and instead map the chain of latent failures that lined up. When your agent pipeline breaks, the proximate trigger is rarely the real cause — it's the combination of a degraded state, a missing guardrail, and an edge case nobody tested. Build your postmortems around that combination, not around blaming the last component that touched the request.
Discussion angle
Apply Cook's framework to a recent AI agent or LLM pipeline failure: what were the latent failures that had to combine, and which defensive layer was missing that let them join?