Operator-Vigilance Dependency¶

Name the safety configuration in which a human operator's unaided sustained attention is the final live barrier against a severe hazard, under exactly the monotony and rarity that the vigilance literature says will degrade that attention — worsened, not helped, by more upstream automation.

Core Idea¶

Operator-vigilance dependency is the safety-critical configuration in which a human operator's sustained, unaided attention is the final — often the only live — barrier against a serious failure, under conditions that systematically degrade that attention. It places a known-weak control in the load-bearing seat: upstream automated layers catch the frequent events, so the residual class reaching the operator is rare, and rarity breeds the monotony that accelerates the vigilance decrement — the "irony of automation."

Scope of Application¶

Operator-vigilance dependency lives across the sociotechnical-safety subfields of safety and human-factors engineering — the settings for which the vigilance literature was developed.

Aviation — pilot monitoring on automated flight decks, where mode confusion and sensor failure are the rare residual class (AF447, Asiana 214).
Healthcare — anesthesia, ICU, and long-shift nursing monitoring under alarm fatigue and shift-duration decay.
Nuclear and process safety — control-room operators on a long quiet watch (Three Mile Island, Davis-Besse).
Financial operations controls — end-of-day reconciliation and four-eye checks reduced to one tired analyst.

Clarity¶

Naming this configuration dislodges the default verdict "the operator failed to monitor," relocating the investigable subject to the design choice that put unaided attention in the last-resort seat. It also sharpens genuine redundancy versus pseudo-redundancy: on the diagram the operator is one layer of several, but for the rare residual class they are the only live barrier — redundancy that exists on the slide but not in the moment that matters.

Manages Complexity¶

A superficially miscellaneous family of incidents, each terminating in the unhelpful "failed to monitor," collapses to one configuration with one diagnostic question. The heterogeneous case details drop out as substitutable instances. The analyst tracks a bounded set of degradation parameters — time on task, monotony, non-actionable-alarm rate, automation-induced workload reduction, annunciation salience, operator state — and reads residual coverage off their product, plus a single severity-of-one-miss scalar and a two-branch redundancy/automation structure.

Abstract Reasoning¶

The configuration licenses a diagnostic inferring the design arrangement from a missed detection and its reflexive verdict, an interventionist move carrying the counterintuitive irony-of-automation prediction (more upstream reliability lowers residual detection) and its constructive reverse, and a boundary-drawing move separating genuine from pseudo-redundancy and unaided from aided attention. Within those bounds it predicts residual coverage as a product of documented decrements before any incident.

Knowledge Transfer¶

Within safety and human-factors engineering the configuration transfers as mechanism across its canonical substrates — pilot, nurse, control-room operator, reconciliation analyst — with little more than a substitution of role, the diagnostic, parameters, redundancy cut, irony-of-automation prediction, and mitigation catalog all carrying intact. Beyond sociotechnical safety it shades into near-vacuity: the generalizable skeleton belongs to the parents single_point_of_failure and defense_in_depth, while the documented human-attention decay and perverse automation coupling stay home.

Relationships to Other Abstractions¶

Current abstraction Operator-Vigilance Dependency Domain-specific

Parents (2) — more general patterns this builds on

Operator-Vigilance Dependency is a kind of Single Point of Failure Prime

Operator-Vigilance Dependency is the sociotechnical-safety species of Single Point of Failure in which one human noticing capacity is the last live barrier.
Operator-Vigilance Dependency presupposes Alertness Prime

Operator-Vigilance Dependency requires a standing, depletable capacity to notice rare low-salience signals before harm occurs.

Hierarchy paths (5) — routes to 4 parentless roots

Operator-Vigilance Dependency → Single Point of Failure → Center Of Gravity → Leverage Points → Feedback

Show alternative paths (4)

Neighborhood in Abstraction Space¶

Operator-Vigilance Dependency sits in a crowded region of the domain-specific corpus (37^th 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