Redundancy is a design strategy in which duplicate or backup components are intentionally incorporated into a system so that if any single component fails, the system as a whole continues to operate or transitions to a safe state. It operates through deliberate duplication of critical paths, power supplies, control systems, or safety functions — the parameter being that the backup must be functionally independent enough to survive the failure mode affecting the primary. Redundancy persists through engineering documentation, design standards, and regulatory requirements that mandate its use in safety-critical domains. [formal: redundantia | substrate: behavior | horizon: generations | explicit: yes | epoch: 0.01]
Accepted ontology entry
redundancy
Redundancy is a design strategy in which duplicate or backup components are intentionally incorporated into a system so that if any single component fails, the system as a whole continues to operate or transitions to a safe state. It opera…
Definition
Why it is in scope
Human-made design practice of including backup or duplicate components to maintain function when primary components fail. A foundational reliability strategy used across engineering, computing, and safety systems.
Names and aliases
- redundancyen · CANONICAL
Relations from this entry
- cms8trh56025c73fklxfsothwSERVES →
Redundancy is built and maintained for the sake of safety-management-system: it ensures that safety-critical functions continue to operate even when components fail, which is a core objective of the safety management system. Law 8d: for whose sake? Redundancy serves the management system's reliability requirements.
- cms7wyk72004ph6s8d82lhwqlSERVES →
redundancy is built for the sake of reliability: adding backup capacity exists to sustain reliability when primary components fail. Servant (redundancy) → master (reliability).
Relations to this entry
- cms9fdor4010i7skqnv0ro3o1← INSTANCE_OF
Failover is a specific kind of redundancy mechanism — a system design strategy where components are duplicated so that if one fails, another takes over. A competent speaker would call failover 'a form of redundancy.' Per Law 9, files against the nearest kind (redundancy).
- cmsixcd4601g4nobpm595aipd← DEPENDS_ON
Common-cause failure IS the phenomenon where a single cause triggers failures in what redundancy was supposed to protect. The removal test: remove redundancy (independent backup paths), and common-cause failure loses all meaning — there are no independent paths to fail together. This is constitutive, not incidental: the concept exists precisely to identify the failure of redundancy assurance.
Record identity
- Created
- Jul 31, 2026, 12:19 PM UTC
- Content hash
- 52dbf9db1d73aaa2df14d37b36f2ee294958ad1cf1168207b380c07aaca09eab