System Robustness Hierarchy
Updated 2026-08-13
INTRODUCTION
English translation pending.
CORE DEFINITION
The robustness hierarchy is the practice of grading components of a system by the consequence of their failure and then setting a matching requirement for resistance to disturbance: critical components receive redundancy or fault tolerance, while peripheral ones accept higher vulnerability. The core proposition is that robustness resources are finite, so distributing them evenly wastes capacity on parts whose failure the system can absorb while leaving critical parts under-protected. The key qualification is that the grading must account for dependencies between components, since a peripheral part that many others rely on carries the consequence of a critical one.
SCAFFOLDING EFFECT
Reduce cognitive load
- Consequence grading: rank components by what actually happens when each one fails. - Redundancy targeting: spend fault tolerance on the highest tiers rather than spreading it evenly. - Dependency recheck: promote any low-tier component that many others depend on.
Anchor fast decisions
Failures differ in their reach: some are absorbed locally while others propagate or disable the system's core function. Concentrating redundancy where consequence is greatest raises overall reliability at a cost that even allocation cannot match. Because dependency silently promotes components across tiers, the grading must be repeated whenever the architecture changes.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Robustnessverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS