What it is
A team sets up monitoring when a system launches, when attention is highest. Months later the people who set it up have moved to other work, and the monthly review has become an occasional one. The screens still show numbers, so everyone assumes that someone is watching.
What it pushes on in the Lab
In the Lab, this pressure lowers the engagement of deployment authority, which is whether someone with real power to change or halt the deployment watches it on a regular schedule. It also amplifies the failure regime, pushing the network toward failures that cascade rather than correct themselves.
Who feels it
Nobody feels it at first, and that is what makes it dangerous. The clients feel it when a worker acts on an error that a working review would have caught.
What answers it
An answer has to restore a real review schedule, stop the system when its alarms fire, or correct drift before it compounds. Each lever below does at least one of these.
Levers in the Lab that push the other way on something this pressure pushes on:
- Pattern:Deployment circuit-breaker
- Pattern:Vendor quality gate
The list leaves out levers the Lab has retired, levers it keeps as counter-examples, and any lever no network offers.
Where it starts switched on
Networks in the Lab that start with this pressure switched on:6
The evidence behind its effects
The Lab cites no claim from the evidence registry for this pressure's effects. The Lab's authors set the direction and size of each effect.