Failure¶

Version: v2 · 2026-09-28 · History
Prime #: 1566
Domain group: Applied Sciences & Engineering
Origin domain: Engineering & Design (beyond software)
Subdomains: Reliability Engineering, Failure Analysis → Engineering & Design (beyond software)
Also from: Organizational & Management Science
Aliases: Nonattainment, Loss of required function

Core Idea¶

Failure is non-satisfaction of an applicable criterion. A carrier—a component, action, process, system, prediction, institution, or attempted outcome—is expected or required to meet an objective, function, threshold, or acceptance condition. Failure occurs when, under the conditions in which that criterion governs, the carrier does not meet it. The criterion can concern attaining a goal, maintaining function, avoiding a forbidden state, meeting a deadline, preserving integrity, or producing a warranted result. Because criteria differ, the same event can be failure under one frame and acceptable performance under another.

Failure can be a state, event, episode, or verdict. A bearing may enter a failed state when it can no longer carry required load; a launch fails when it does not reach its mission condition; a proof attempt fails when a step is invalid; an organization fails when a binding obligation is not met. The term does not by itself specify cause, mechanism, severity, blame, permanence, or total collapse. Partial, intermittent, graceful, latent, and catastrophic failures differ along those dimensions while sharing criterion non-satisfaction.

The Prime separates outcome classification from explanation. A fault is a defect or abnormal condition that may cause failure. An error is an incorrect state or result that may be detected and corrected before a requirement is lost. A failure mode describes how failure appears; a failure mechanism describes the process producing it; damage is adverse change; risk concerns possible future loss. Keeping these relations distinct makes failure portable across engineering, medicine, computation, action, institutions, and ecology without turning every undesirable event into the same thing.

How would you explain it like I'm…

Didn't Do Its Job

Failure means something didn't do what it was supposed to do. A cup is supposed to hold juice; if it has a hole and the juice leaks out, the cup failed at holding juice. But the same leaky cup could still be fine as a flower pot—it depends on what job you gave it.

Missing the Goal

Failure is when something doesn't meet the goal or rule it was supposed to meet. That something could be a machine, a plan, a guess, or a team. Whether it counts as failure depends on which goal you're checking: a paper airplane that flies only a little way fails a distance contest but might pass a "make it fly at all" test. Failure doesn't automatically tell you why it happened, how bad it is, or whose fault it is. It can be small and partial, or huge and total.

Not Meeting the Criterion

Failure is not meeting an applicable criterion. Something (a part, an action, a system, a prediction, an organization) is expected to meet a goal, function, threshold, or deadline, and it fails when, under the conditions where that standard applies, it doesn't. Because the standard can change, the same event can be a failure under one frame and acceptable under another. Failure by itself says nothing about cause, severity, blame, or permanence; failures can be partial, intermittent, graceful, hidden, or catastrophic. It also helps to keep related words separate: a fault is a defect that might cause failure, an error is a wrong state or result that could still be caught before a requirement is missed, a failure mode is how failure shows up, and a failure mechanism is the process that produces it.

Failure is the non-satisfaction of an applicable criterion. A carrier, whether a component, action, process, system, prediction, institution, or attempted outcome, is required or expected to meet an objective, function, threshold, or acceptance condition, and failure occurs when, under the conditions in which that criterion governs, the carrier does not meet it. The criterion may concern reaching a goal, maintaining function, avoiding a forbidden state, meeting a deadline, preserving integrity, or producing a warranted result, so the same event can be failure in one frame and acceptable performance in another. Failure can be modeled as a state (a bearing that can no longer carry its rated load), an event (a launch that misses its mission condition), an episode, or a verdict (a proof attempt with an invalid step). The term alone does not specify cause, mechanism, severity, blame, permanence, or total collapse, which is why partial, intermittent, graceful, latent, and catastrophic failures can all share the same core. It is useful to separate failure as an outcome classification from its explanation: a fault is a defect or abnormal condition that may cause failure, an error is an incorrect state that might be detected and corrected before a requirement is lost, a failure mode is how failure manifests, a failure mechanism is the process producing it, damage is adverse change, and risk concerns possible future loss. Keeping these distinct lets the concept travel across engineering, medicine, computing, institutions, and ecology without lumping every bad event together.

Structural Signature¶

Recurring features:

carrier. the system, component, action, process, prediction, institution, or outcome being assessed
applicable criterion. the required objective, function, threshold, prohibition, acceptance rule, or service condition
operating circumstances. the load, environment, time, user, mission phase, or jurisdiction under which the criterion applies
observed performance. the state, behavior, output, or outcome compared with the criterion
non-satisfaction relation. the relevant mismatch, omission, interruption, invalidity, or prohibited transition
detection boundary. the evidence and sensitivity by which failure is recognized rather than merely suspected
extent. partial or total, local or systemic, intermittent or persistent
time profile. incipient, active, arrested, recovered, repeated, or terminal
consequence. effects that follow from failure but are not constitutive unless included in the criterion
causal explanation. fault, mechanism, human action, environment, or interaction that explains but is not identical to the failure
recovery boundary. restoration, workaround, compensation, or reclassification can end or mitigate failure without changing that it occurred

What It Is Not¶

Fault. A fault is a defect or abnormal condition capable of producing failure; redundant systems can contain faults without losing required function.
Error. An error is an incorrect internal state, judgment, or result; correction can prevent it from crossing the failure boundary.
Damage. Damage is adverse change to integrity or performance and may be tolerated within requirements.
Risk. Risk concerns the possibility and consequence of future failure, not criterion non-satisfaction that has occurred.
Failure cause or mechanism. Cause explains why failure occurred and mechanism describes how it progressed; neither is the criterion-relative outcome itself.
Dissatisfaction. An observer's dislike is not failure unless a governing objective or acceptance condition is identified.
Blame. Failure can occur without negligence, agency, or moral responsibility, and blame can be assigned even when a technical criterion was met.

Broad Use¶

Failure applies wherever its complete role structure is present; the source domain is historical provenance, not a boundary on the Prime.

Engineering. a component or system loses required function under specified load and environment
Computing. a service violates correctness, availability, latency, durability, or security requirements
Projects. a delivery misses binding scope, time, cost, quality, or benefit criteria
Medicine. an intervention fails relative to a declared clinical endpoint while other outcomes may still improve
Biology. an organism or regulatory process does not maintain a function under the relevant condition
Institutions. a body does not discharge a legal, fiduciary, procedural, or public-service obligation
Science. a model, prediction, or replication fails a stated evidential or methodological test
Individual action. an attempt does not attain its objective despite or because of the chosen action
Communication. a message or protocol fails when required information is not conveyed or acted upon
Safety. a protective barrier fails when a hazardous process crosses the condition it was required to prevent
Applicability boundary. A case must identify the carrier, criterion or shared objective, operative relation, and collapse condition defined above; verbal resemblance alone does not instantiate Failure.

Clarity¶

Use Failure only after naming the carrier and the relation that makes the case one. The minimal definition is: Failure is the criterion-relative state or event in which a system, action, component, process, or attempted outcome does not satisfy a required objective, function, or acceptance condition under the circumstances where that condition applies. The most common ambiguity is to substitute a neighbor, an enabling condition, or a consequence for the identity itself. A precise claim therefore fills at least these roles: carrier, applicable criterion, operating circumstances, and recovery boundary. It also states the level of analysis and the evidence that would make a competent observer reject the classification. This prevents a familiar word from doing explanatory work that belongs to a testable relation.

Manages Complexity¶

Failure manages complexity by compressing many implementations into a stable role structure without erasing the variables that control validity. Analysts can compare cases by filling the same slots, locate disagreement in a missing role, and separate the constitutive relation from causes, instruments, representations, and consequences. The compression is intentionally reversible: the short label expands into carrier, applicable criterion, operating circumstances, observed performance, non-satisfaction relation, detection boundary, with explicit boundaries for variation and collapse. This makes heterogeneous cases comparable while keeping local mechanisms, authority, uncertainty, and evidence visible.

Abstract Reasoning¶

Carrier move. Identify the system, component, action, process, prediction, institution, or outcome being assessed and record what observation supports the assignment.
Applicable Criterion move. Identify the required objective, function, threshold, prohibition, acceptance rule, or service condition and record what observation supports the assignment.
Operating Circumstances move. Identify the load, environment, time, user, mission phase, or jurisdiction under which the criterion applies and record what observation supports the assignment.
Observed Performance move. Identify the state, behavior, output, or outcome compared with the criterion and record what observation supports the assignment.
Non-Satisfaction Relation move. Identify the relevant mismatch, omission, interruption, invalidity, or prohibited transition and record what observation supports the assignment.
Detection Boundary move. Identify the evidence and sensitivity by which failure is recognized rather than merely suspected and record what observation supports the assignment.
Extent move. Identify partial or total, local or systemic, intermittent or persistent and record what observation supports the assignment.
Time Profile move. Identify incipient, active, arrested, recovered, repeated, or terminal and record what observation supports the assignment.
Counterexample move. Remove one constitutive role while holding the surrounding topic fixed; if the label still appears equally applicable, the definition has become too loose.
Neighbor move. Compare the filled roles with the distinctions below and route the case to the narrower or broader entry whose collapse test it actually satisfies.

Knowledge Transfer¶

Cross-domain transfer. Carrier, applicable criterion, operating condition, observed performance, and non-satisfaction travel across technical, biological, institutional, and action substrates; the choice of criterion remains explicitly framed. The invariant is not the source-domain vocabulary but the typed relation expressed by the one-line definition. Transfer is literal when a receiving domain can fill the same roles and expose the same failure boundary; it is analogical when only a visual, verbal, or narrative resemblance survives.

Local warrants for Failure. Different domains establish those roles differently. Formal domains may use proof, specifications, or executable traces; empirical domains use observation and measurement; institutions use authority, records, and rules; practical settings use performance and counterfactual tests. This Prime coordinates the questions without replacing those standards.

Transfer procedure. First identify the source case without metaphor. Then abstract carrier, applicable criterion, operating circumstances, observed performance, non-satisfaction relation. Map each role to the receiving case, test the collapse condition, and explicitly carry any domain qualification that affects validity. If a role has no literal occupant, transfer only a neighboring abstraction or label the comparison as analogy.

Examples¶

Formal/abstract¶

A storage service promises that an acknowledged write will remain retrievable after any single-disk loss. One disk develops a fault, but redundancy preserves the data; there is a fault without service failure. Later, a correlated controller defect causes acknowledged data to disappear after a disk loss. The observed performance violates the durability criterion under a covered operating condition, so failure has occurred. The controller defect is a cause, data disappearance is the failure mode, customer loss is a consequence, and the probability of recurrence contributes to risk.

Mapped back: carrier → the carrier in the example; applicable criterion → its stated counterpart; operating circumstances → the defining condition; recovery boundary → the described counterfactual boundary.

Applied/industry¶

A clinical trial defines treatment success as a prespecified improvement at twelve weeks. A participant improves on pain but not by the required amount on the primary endpoint. Relative to that endpoint, the treatment has failed for that participant; relative to a secondary sleep outcome, it may have succeeded. The classification does not establish that the drug mechanism was inactive, that clinicians were negligent, or that no benefit occurred. It establishes only non-satisfaction of an applicable criterion under the trial's measurement conditions.

Mapped back: the applied carrier fills carrier, its governing relation fills operating circumstances, the evidence fills detection boundary, and removal of recovery boundary marks the point at which the example would cease to instantiate Failure.

Structural Tensions¶

T1 — Objective fact versus criterion choice. Once a criterion and evidence are fixed, non-satisfaction can be factual, yet selecting the criterion may be institutional or normative. Diagnostic: Who set the criterion, under what authority, and would another legitimate frame classify the same event differently?

T2 — Local versus systemic failure. A component can fail while the system succeeds through redundancy, or every component can meet local targets while the system fails. Diagnostic: At which carrier level is the requirement defined?

T3 — Detection versus occurrence. Failure can exist before observation, while noisy indicators can announce failure that has not occurred. Diagnostic: What evidence connects the measured signal to the actual criterion breach?

T4 — Partial degradation versus binary verdict. Performance often degrades continuously although contracts and safety rules impose discrete boundaries. Diagnostic: Is the threshold constitutive, conventional, or a reporting convenience?

T5 — Cause versus outcome. The same failure mode can arise from different mechanisms, and the same fault can be absorbed without failure. Diagnostic: Is the statement naming the criterion breach, its appearance, or its cause?

T6 — Learning versus normalization. Failures can reveal weak assumptions and improve systems, yet repeated near-failures can instead be normalized. Diagnostic: What changes in the model, design, or operating boundary after the event?

Structural–Framed Character¶

Failure is structural on the structural–framed spectrum. Carrier, applicable criterion, operating condition, observed performance, and non-satisfaction travel across technical, biological, institutional, and action substrates; the choice of criterion remains explicitly framed. Its structural skeleton is expressed by the roles above and can be evaluated without importing one home-domain mechanism.

Framing still matters for Failure. Institutions choose some criteria, communities stabilize terminology, practices determine admissible evidence, and normative consequences can follow from classification. Those facts qualify an instance without making the whole abstraction conventional. The correct test is whether changing the frame removes the constitutive relation or merely changes how it is named, measured, governed, or valued.

Across the spectrum tests, the vocabulary travels with moderate qualification, evaluative weight is separable from the descriptive identity, institutional origin is not universally constitutive, and import must be distinguished from recognition. The entry is therefore portable but not context-free.

Substrate Independence¶

Failure has high substrate independence — composite 5 / 5. Carrier, applicable criterion, operating condition, observed performance, and non-satisfaction travel across technical, biological, institutional, and action substrates; the choice of criterion remains explicitly framed. The carrier can change while the relation and its rejection test remain intact. A cross-domain use does not require one material, notation, institution, species, or implementation.

The Failure rating is not a license for metaphor. Mechanisms and evidence remain local, and a familiar surface does not substitute for the typed roles. This Prime survives transfer only when the same relation is present and the same kind of counterfactual removal would make it fail.

Composite substrate independence — 5 / 5
Domain breadth — 5 / 5
Structural abstraction — 5 / 5
Transfer evidence — 5 / 5
Mechanism neutrality — 5 / 5

Relationships to Other Abstractions¶

Current abstraction Failure Prime

Foundational — no parent edges in the catalog.

Children (1) — more specific cases that build on this

Breach of Contract Domain-specific is a kind of Failure

A breach is observed non-satisfaction of an applicable contractual duty or present no-renunciation criterion under governing law.

Neighborhood in Abstraction Space¶

Failure sits among the more crowded primes in the catalog (35^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Failure, Robustness & Safety Margins (17 primes)

Nearest neighbors

Fail-fast system — 0.75
Rationality — 0.73
Temporal Decay and Degradation — 0.72
Damage — 0.72
Estimation — 0.72

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With¶

Fault. A fault is a defect or abnormal condition capable of producing failure; redundant systems can contain faults without losing required function.
Error. An error is an incorrect internal state, judgment, or result; correction can prevent it from crossing the failure boundary.
Damage. Damage is adverse change to integrity or performance and may be tolerated within requirements.
Risk. Risk concerns the possibility and consequence of future failure, not criterion non-satisfaction that has occurred.
Failure cause or mechanism. Cause explains why failure occurred and mechanism describes how it progressed; neither is the criterion-relative outcome itself.
Dissatisfaction. An observer's dislike is not failure unless a governing objective or acceptance condition is identified.
Blame. Failure can occur without negligence, agency, or moral responsibility, and blame can be assigned even when a technical criterion was met.

Solution Archetypes¶

No catalogued solution archetypes reference this prime yet.

Notes¶

No current live node supplies a defensible necessary genus for Failure. Neighboring operations participate in some instances but do not entail the complete identity, so the node is admitted without a parent pending later graph densification.

The entry intentionally separates the abstraction from its causes, instruments, outcomes, moral appraisal, and common implementations. Future DAG or solution-archetype work may add non-hierarchical relations, but those links should be adjudicated independently rather than inferred from shared vocabulary.

References¶

Frozen Wikipedia revision: https://en.wikipedia.org/wiki/Failure (revision 1362645985).
DOI: https://doi.org/10.1177/002224379903600305
DOI: https://doi.org/10.1187/cbe.CBE-14-03-0054
DOI: https://doi.org/10.1093/acprof:oso/9780199347520.001.0001
DOI: https://doi.org/10.1177/20539517221131290
DOI: https://doi.org/10.1177/20539517211069891
DOI: https://doi.org/10.1177/2053951720977882
DOI: https://doi.org/10.1007/BF00368204
Supporting reference preserved in the packet: http://www.merriam-webster.com/dictionary/failure
Supporting reference preserved in the packet: https://web.archive.org/web/20150716191304/http://www.merriam-webster.com/dictionary/failure
Supporting reference preserved in the packet: https://books.google.com/books?id=2H6hDAAAQBAJ&q=%22commercial+failure%22
Supporting reference preserved in the packet: https://books.google.com/books?id=rNi_DwAAQBAJ
Supporting reference preserved in the packet: https://www.bu.edu/bhr/2019/03/20/failure-is-not-fatal-actionable-insights-on-service-failure-and-recovery-for-the-hospitality-industry/
Supporting reference preserved in the packet: https://books.google.com/books?id=aog3AwAAQBAJ
Supporting reference preserved in the packet: https://books.google.com/books?id=nFRG2UizET0C&pg=PA98
Supporting reference preserved in the packet: http://www.edge.org/q2011/q11_6.html
Supporting reference preserved in the packet: https://web.archive.org/web/20131205173145/http://www.edge.org/q2011/q11_6.html
Supporting reference preserved in the packet: https://vbn.aau.dk/files/482741218/20539517211069891.pdf
Supporting reference preserved in the packet: http://www.snopes.com/politics/bush/google.asp
Supporting reference preserved in the packet: https://www.nytimes.com/2009/08/09/magazine/09FOB-onlanguage-t.html?_r=3&ref=magazine&pagewanted=all

The frozen Wikipedia revision is discovery provenance. The retained source set was reviewed for identity, formal or operational relation, and scope. The encyclopedia's structural synthesis is bounded to those claims; a thin authority surface is recorded as a nonblocking source-strengthening repair rather than concealed.