Hazard-Control Decay

Track the widening gap between what a safety control's paperwork says it does and what it actually does under hazard, so that a control certified sound by audit can be found silently unprotective before it fails.

Core Idea

The pattern in which a protective control — a procedure, interlock, checklist, or maintenance ritual — stays documented and formally in force while its actual protective effect has eroded past reliability. The defining mark is the divergence between nominal and enacted control: the audit ticks, but the protection the system believes it has is not what it delivers. Decay accumulates from locally reasonable adaptations — a skipped checklist item, a normalized workaround, an untested valve (Vaughan's "normalization of deviance").

Scope of Application

Lives across safety-critical operations — one substrate (layered safeguards tracked by an assurance apparatus) at many sectoral specializations.

• Aviation — a checklist item routinely skipped against tempo while the QRH still requires it.
• Healthcare — hand-hygiene compliance at 95% on observed days, 40% on unobserved ones.
• Nuclear operations — a lock-out procedure with floor-known workaround keys.
• Process industries — a relief valve at design pressure but seized after years without a flow test.
• IT security — an MFA policy in force while grandfathered accounts open a standing gap.

Clarity

Naming the decay makes the divergence itself, not the control, the unit of analysis, dissolving the puzzle "we passed every audit and had the incident anyway." It also sharpens decay against three lookalikes it is routinely lumped with: control absence, design error, and failure under stress — each calling for a different fix.

Manages Complexity

An open-ended forensic problem over a whole inventory of green-ticked controls reduces to tracking one scalar per control — the gap between enacted and nominal protection — and routing each through a four-way branch (absence, design error, failure-under-stress, decay). Only the decay branch points to enacted-test verification, and the hazard's location is read off the divergence rather than reconstructed incident by incident.

Abstract Reasoning

The pattern licenses discounting assurance evidence by construction (a green tick proves only the artifact exists), a four-way classifying branch that selects the remedy, and mechanism-tracing from a present gap back to accumulated adaptations. That supports a predictive reading of where gaps widen and an interventionist move: measure the enacted effect, not the nominal artifact.

Knowledge Transfer

Within safety-critical operations the pattern transfers as mechanism — the whole apparatus (divergence unit, blind-assurance diagnostic, four-way classification, enacted-test instruments) carries intact across aviation, healthcare, nuclear, and IT, which are one substrate at many sectors. Beyond it, invoking the name where there is no hazard is analogy. The portable content is the parent nominal_vs_actual_control — a documented apparatus diverging from the enacted one while assurance stays blind — which travels to policy-on-the-books versus enforced and espoused-versus-enacted theory.

Relationships to Other Abstractions

Current abstraction Hazard-Control Decay Domain-specific

Parents (2) — more general patterns this builds on

• Hazard-Control Decay is a kind of Nominal vs. Actual Control Prime

  Hazard-Control Decay is Nominal vs. Actual Control specialized to a protective safeguard whose documented presence conceals eroded enacted protection.

• Hazard-Control Decay is a kind of Temporal Decay and Degradation Prime

  Hazard-Control Decay is temporal degradation specialized to the protective effectiveness of a safeguard diminishing while its nominal artifact remains in force.

Hierarchy paths (5) — routes to 5 parentless roots

• Hazard-Control Decay → Nominal vs. Actual Control → Formal vs. Informal Structures → Formalization → Representation → Abstraction

Show alternative paths (4)

Neighborhood in Abstraction Space

Hazard-Control Decay sits in a sparse region of the domain-specific corpus (64^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

• Evacuation — 0.84
• Active Failure — 0.84
• Operator-Vigilance Dependency — 0.83
• Internal validity — 0.83
• Situational-Awareness Collapse — 0.83

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