Verification complacency
Verification complacency is the degradation of critical attention that occurs when organizations or individuals treat formal verification — mathematical proof of correctness, model checking, or static analysis — as sufficient assurance of system safety. Like automation complacency, it is not a personal failing but a structural consequence of a feedback topology in which one component has been declared 'provably correct,' reducing the organizational incentive to scrutinize everything else.
The mechanism is straightforward. A verified kernel, a certified compiler, or a model-checked protocol creates an epistemic anchor — a fixed point of certainty around which the rest of the system's assurance arguments are organized. The psychological effect is that scrutiny migrates away from the verified component and, critically, fails to intensify around the unverified components that interact with it. The drivers, the configuration files, the human procedures, the organizational pressures — all of these remain unverified, yet they receive less attention precisely because the verified component has absorbed the assurance budget.
Verification complacency is particularly dangerous because it masks the composition problem: even if every component is individually correct, their composition may be unsafe. The specification that the verified component implements may be wrong. The assumptions that the proof makes about its environment may be violated. The interfaces between verified and unverified components may introduce behaviors that neither team anticipated. Resilience engineering treats these interface failures as primary concerns, but verification complacency treats them as secondary to the 'real' problem of component correctness.
The antidote is not less verification but skeptical verification — an approach that treats proof as a tool for finding bugs rather than a license to stop looking. This requires organizational practices that maintain scrutiny of the system as a whole, including the joint cognitive system of engineers, administrators, and operators who interact with the verified technology.