Latent Condition¶

Name the dormant, pre-staged weakness in a system's defence layers — laid down by upstream decisions far from the sharp end — that produces no harm until an operational circumstance aligns it with an active failure to complete a path to an accident.

Core Idea¶

A latent condition is a pre-staged weakness — in design, procedures, staffing, or management decisions — that resides dormant inside a sociotechnical system for months or years without producing harm, until an operational circumstance activates it by aligning it with an active failure to complete a path to an accident. In Reason's organisational-accident model it names the upstream, blunt-end stratum of causation: holes pre-positioned in the system's defence layers.

Scope of Application¶

Latent condition (with its complement active failure) lives across the accident-investigation subfields of safety engineering and human factors — defence-in-depth sociotechnical systems whose blunt-end actors lay down weaknesses far from the sharp end.

Aviation safety — procedural ambiguities, badly designed alerting, and training gaps dormant until a weather/traffic/crew combination activates them.
Healthcare and patient safety — look-alike packaging, ward-stock decisions, and double-check policy gaps sitting silent until a sharp-end action would otherwise be caught.
Nuclear and process safety — the term's domain of origin: instrumentation gaps and maintenance backlogs holed into the defence layers.
Financial operations risk — control gaps and segregation-of-duties weaknesses dormant until a trader's action converts them into loss.
Proactive safety audit and resilience engineering — the signature context: audits and FMEA that remove resident pathogens before any incident.

Clarity¶

Naming the latent stratum dissolves the investigator's temptation to stop the analysis at the proximate operator act, making the blunt end an obligatory part of the causal account. It sharpens two distinctions: condition versus act (the dormant hole against the operator motion that aligns with it), and audit versus incident (the condition is inspectable before anything activates it).

Manages Complexity¶

An accident presents an open-ended tangle of heterogeneous factors with no stopping rule for the "root cause" search. The concept imposes a binary partition — each factor is either a latent pre-positioned weakness or an active operator action — routing the two bins to two settled toolkits and reducing each latent factor to a few tracked parameters: lag, organisational distance, defence layer, and activation flag.

Abstract Reasoning¶

The concept licenses a diagnostic-retrospective move (reason backward from a harmful act to the pathogens it merely completed), an interventionist move with a class-wide predicted effect (removing a hole forecloses every accident that would recruit it), and boundary-drawing on when the inference applies, including the audit window and the activation-required limit.

Knowledge Transfer¶

Within safety engineering the concept transfers as mechanism across aviation, medicine, nuclear, and financial operations, with the proactive-audit posture as its signature. The abstract pattern of pre-staged vulnerability is carried by parents critical_juncture, the single-point-of-failure / cascade family, and hidden_path_and_barrier_crossing. Forced into non-operator domains (codebases, constitutions, ecosystems) it becomes metaphor, better named directly.

Relationships to Other Abstractions¶

Current abstraction Latent Condition Domain-specific

Parents (1) — more general patterns this builds on

Latent Condition presupposes Swiss Cheese Model (Layered Defense with Aligning Holes) Prime

Latent condition presupposes the Swiss-cheese model's serial imperfect defenses, standing holes, and alignment mechanism; outside that framework it collapses to generic dormant vulnerability.

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

Active Failure Domain-specific presupposes Latent Condition

Active failure presupposes latent condition because a sharp-end act earns this label only when it completes a hazard path through weaknesses already staged in the layered defenses.

Hierarchy paths (25) — routes to 9 parentless roots

Latent Condition → Swiss Cheese Model (Layered Defense with Aligning Holes) → Conjunctive Path Activation → Causality → Dependency

Show alternative paths (24)

Neighborhood in Abstraction Space¶

Latent Condition sits in a crowded region of the domain-specific corpus (23^rd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12