It gets slow before it breaks
2026-08-22 · Fragility, Resilience & Early Warning
A system about to fail looks exactly the way it always looks. The quantity that is actually changing is how long it takes to come back after a nudge — and almost nobody records that one.
Think of a door with a spring closer. When it was new you pushed it open, let go, and it snapped shut. A few years on, the same push, the same release, and it drifts — swinging, hesitating, easing slowly closed. Note that the door's position has not changed: left alone it sits shut, exactly as it did when new. Only the speed of return has changed. And one day it stops closing at all.
This is the fifth time this site has taken up criticality, but the first four were about how a system flips. This one asks something else: can you see the flip coming? The counterintuitive part is that if there is a signal, it is usually not in the number you are watching. Water clarity, share price, mood, error rate — these tend to be suspiciously calm right up to the transition. The signal hides in the way those numbers wobble, and wobble is the first thing a monthly average destroys.
The five criticality topics look at the same cliff from different angles: Topic 10 is bifurcation and tipping (the system jumps to another steady state), Topic 16 is phase transitions and universality (why details stop mattering at the critical point), Topic 17 is percolation (connectivity going through in one step), Topic 18 is self-organized criticality (the system climbs to the critical point by itself). This one asks only two things: is there a measurable precursor, and when is there none at all.
Saying a system is "stable" means something quite specific: nudge it and it comes back by itself. Draw that and you get a ball sitting in a bowl. The nudge pushes the ball up the wall; coming back is the ball rolling to the bottom.
The shape of the bowl sets how fast it returns. Steeper walls mean the same push lifts the ball less and it rolls back quickly; a flatter bowl means the same push sends it further and it takes ages to settle. Physics calls that speed the recovery rate; its inverse is the recovery time — how long it takes to get home. → ref · Phase space & attractors
Now connect Topic 10. When external conditions creep on — phosphorus accumulating in a lake, a metal part flexed over and over, someone short of sleep for months — the system inches toward a bifurcation point: the point past which it jumps to another state and does not come back. Mathematically, approaching that point is the flattening of the bowl. At the bifurcation the bottom is completely flat and the recovery rate has fallen to zero.
The phenomenon has a name: critical slowing down. Its prediction is admirably concrete: the closer to the tipping point, the slower the recovery from a disturbance.
This is not just blackboard work. In 2012 a group of Dutch researchers drove a population of cyanobacteria — bacteria that live by photosynthesis — toward a real tipping point in the lab: above a critical light level, photo-inhibition collapses the whole population, and it does not come back. Before the collapse they repeatedly applied identical small disturbances and timed the return. The closer to that critical light level, the slower the recovery. It remains one of the cleanest demonstrations that slowing down really happens in a living system.
For every system you actually care about, define a bounce-back measure: after a small disturbance of comparable size, how long does it take to return to baseline? Then track the trend of that time rather than the state value itself. The test is not "how long this time" but "is the same disturbance taking longer this month than last".
Section 1 leaves a practical problem: you cannot nudge a lake every week, nor take a company and shove it to see how fast it steadies. Fortunately you don't have to. Wind, rain, temperature, random buy and sell orders, the small mess of daily life — something is pushing all the time. The system is never actually at rest; it is constantly being knocked off and sliding back.
So the slowdown writes itself into that wobble, in two quantities you can compute directly.
First, consecutive moments start to resemble each other. If the bounce-back is fast, the deviation created now is gone by the next reading, so consecutive readings have almost nothing to do with each other. If the bounce-back is slow, most of this moment's deviation survives into the next — and the readings start to look alike. There is a standard way to measure that: lag-1 autocorrelation (pair every reading with the one after it and see how tidily those pairs line up). Slowing down drives it toward 1.
Second, the swings get wider. Deviations that decay slowly stack on top of each other, so the same size of push produces a bigger excursion. How wide the swings are is the variance — the average squared distance from the mean; bigger means more spread out.
These are two faces of one thing, and they fit in a single line of near-trivial arithmetic. Write the system's behaviour near baseline as "next moment = α × this moment + a bit of random push". That α is the surviving fraction: α near 0 means the system forgets instantly (fast recovery), α near 1 means it remembers almost everything (slow recovery). Statisticians call this line a first-order autoregression, written AR(1); its continuous-time twin is the Ornstein-Uhlenbeck process. α is a direct translation of the recovery rate, and the width of the swings scales as 1 ⁄ √(1−α²) — take α from 0.2 to 0.95 and the same push produces swings three times as wide. → ref · AR(1) & the OU process
The approach has been tested for real, on a whole lake. Over three years, researchers gradually stocked largemouth bass into Peter Lake in Wisconsin, deliberately pushing its food web toward a flip, while monitoring a neighbouring untouched lake as a control. The result: variance and autocorrelation in the manipulated lake began rising more than a year before the food web actually shifted.
There is a striking human counterpart. A 2014 study using high-frequency mood diaries — several prompts a day — reported that autocorrelation and variance in emotions rise before both the onset and the lifting of depression. That result drew a published objection at the time: critics argued the data showed a difference between groups rather than individuals demonstrably approaching a tipping point. It is best treated as a direction worth pursuing, not a settled finding.
If you are going to monitor something, keep the raw high-frequency data; don't store only aggregates. Variance and autocorrelation are both quantities about adjacent readings, and taking a monthly mean destroys them by definition — ten years of monthly reports contain none of this signal at all. There is a computable floor for sampling: sample several times faster than the system's recovery time. If recovery takes three days, monthly is useless.
Reading the recovery rate out of ambient noise is free, and also the dirtiest option: you need a long stretch of series and you have to hope nothing else changed during it. There is a faster, cleaner way — disturb it yourself and start the clock.
You have seen this done. A cardiac stress test is exactly a deliberate perturbation: the doctor does not wait for the day you happen to go running, they put you on a treadmill, apply a controlled and comparable push, and watch how fast you come back. Engineering calls the same idea a tap test — strike the structure, see how quickly the vibration dies away. Software calls it chaos engineering or a game day — kill a machine on purpose and time how long the system takes to return to normal.
The load-bearing word is comparable. The size, location and timing of each perturbation must be as alike as you can make them, or what you measure is the difference between the pushes rather than the difference in the system.
One class of system gets a bonus for free: systems spread out in space. Dryland vegetation, coral reefs, forests — a single satellite image holds thousands of readings. So instead of waiting for time to pass you can compute variance and neighbour-similarity across space: patches getting coarser and neighbouring cells becoming more alike is the same phenomenon as rising variance and autocorrelation in time, cut a different way. One snapshot can occasionally stand in for years of waiting.
Change the output of a drill from "pass / fail" to a number: recovery time. And require the perturbation to be comparable (same injection, same load band), or the number cannot be compared across runs. The value of a drill is not proving you can survive it — it is giving you a curve with a readable trend. Surviving but taking twice as long as last quarter is the single most important thing the drill produced.
Suppose you did all of the above right: high-frequency data, comparable probes, indicators climbing. Turning that into an alarm that actually rings runs into a very plain piece of arithmetic.
First, three easy traps.
Trap one: the wrong variable. Slowing down shows up only in quantities coupled to the direction that is about to lose stability. A system has dozens of metrics and most of them are unrelated; watching those, you will wait forever. Choosing the variable requires a guess about the mechanism — so this method does not free you from understanding the system, only from having an exact model of it.
Trap two: window length and detrending are free parameters. Computing variance means choosing how long the sliding window is, and usually removing a slow trend first — and how long, and how removed, are up to you. That is enough freedom that trying a few settings will often produce whichever conclusion you were hoping for. The only honest procedure is to fix and write down the parameters before you look at the result.
Trap three: the test should be a trend, not a threshold. "Alarm if autocorrelation exceeds 0.8" is meaningless — baseline values differ wildly between systems. What is meaningful is whether the indicator is persistently rising over a stretch (usually quantified with a rank correlation test).
And then the arithmetic. Transitions are rare events, and rare events dilute even a good detector:
So the only actions an early warning signal can drive are the cheap, reversible ones: raise the monitoring frequency, thicken a buffer, take leverage down a notch, postpone an irreversible decision by a few weeks. It cannot drive "shut the plant down" — not because the signal is bad, but because an 87% false-alarm rate multiplied by the cost of a shutdown is unpayable, and after the second one somebody quietly switches the detector off.
Before building a detector, do the multiplication: expected base rate × sensitivity (how many real ones you catch) against false-positive rate × the cost of each false alarm. If the product doesn't work, the fix is not a more sensitive detector — it is the other road: raise reversibility, so that a transition, when it comes, costs little enough that you didn't need to know in advance. Warning and reversibility are substitutes; on a tight budget the second is usually the sounder buy.
Now the other side, and this section matters more than the four before it. Early warning signals — EWS for short — are among the most oversold ideas in complexity science of the past fifteen years. There is something real in them, and there are a great many ways for them to fail.
First, only one kind of transition gives you a window. The entire argument rests on a premise: that the system is being carried toward a bifurcation gradually by slowly creeping external conditions. At least two kinds of transition violate it. One is pushed over by noise: the bowl never got shallower, one shove was simply large enough to kick the ball over the ridge. The other is conditions changing too fast: the bowl really is flattening, but no slower than the transition itself, so the slowdown never accumulates into a measurable signal.
This is not a theoretical worry. The Dansgaard-Oeschger events of the last ice age — abrupt warmings of a dozen degrees within decades — were checked for slowing down and it is not there; the best reading is that they were noise-triggered, hence unforecastable in principle. Ecology has its own version: a 2010 analysis showed that a whole family of perfectly standard ecological models produces no leading indicators before a regime shift.
Second, a signal is not proof that a tipping point is ahead. Rising variance and autocorrelation establish that recovery has slowed — that resilience has fallen. But falling resilience need not mean there is a cliff in front of you; the system may simply be degrading smoothly toward a worse but continuous state. A 2025 review in climate science put it bluntly: reading rising EWS as "a tipping point lies ahead" packs into the signal something the signal does not contain.
Third, the statistical power is far worse than people assume. Reliably detecting a rising trend inside noise takes a long, high-frequency series over a period in which nothing else moved — real data routinely satisfies none of those. A 2012 study devoted to this question concluded that at realistic data volumes the reliability of these tests is too low to carry a decision.
Fourth, retrospective success is not success. This affliction is universal in forecasting and EWS did not escape it. Seizure prediction has been studied for over thirty years, retrospective "successes" have been abundant, and prospective blinded validation stayed out of reach for decades — only recently have long-term implanted recordings produced limited genuine forecasting. The well-known 2023 paper warning of a collapse of the Atlantic meridional overturning circulation (AMOC) supplied a fresh example: in 2025 its authors issued a correction acknowledging coding errors in the estimation procedure. None of this voids the research programme, but it is a reminder: between a model that "would have warned of" a past collapse and a usable alarm lies an entire regime of prospective validation.
Fifth, a monitored system reacts. This is the Topic 26 mechanism showing up here: once variance and autocorrelation become targets, the cheapest way to hit them is not to become more resilient but to flatten the indicator — lengthen the reporting interval, smooth what gets submitted, absorb small fluctuations internally. Same system, better numbers.
Sixth, self-organized critical systems have no "distance to the tipping point" at all. The systems of Topic 18 — sandpiles, earthquakes, faults — are not approaching a critical point; they sit on one, throwing off events of every size continuously. Asking how far such a system is from its transition is the wrong question, because there is no bifurcation being approached. → ref · The sandpile model
When reporting any early warning indicator, report three things with it: the failure conditions (what makes you think this system is the slow-bifurcation kind rather than the noise-triggered kind), the base rate (how often this class of transition has occurred in your history), and when the window and detrending parameters were fixed (before the result, or after). Missing any of the three, the signal should not enter a decision. And the safer stance throughout: treat EWS as an input to vigilance, and reversibility as the actual defence.
Strictly, you can't know for certain. Two usable approximations: has the system ever shown hysteresis (the same parameter value supporting two different states, which implies bistability and therefore a bifurcation)? And is the driver changing far more slowly than the system's own recovery time? When both hold, the premise of EWS roughly stands; when one fails, downweight it. Note that both tests rely on history — and a kind of transition that has never occurred in your history is invisible to them.
This is Goodhart's law from Topic 26, and there is no clean solution. One partial answer is two layers: indicators used to raise the alarm must be public (or nobody responds), while indicators used to audit the detector itself should be held back and sampled. Another is to prefer indicators where flattening them requires actually improving — recovery time, for instance, is hard to shorten without genuinely adding slack. Unfortunately there are not many like that.
Some people argue exactly that ("the edge of chaos"), on the grounds that response to small inputs is maximal near the critical point. But the cost is symmetric: large response also means poor rejection of disturbance, and slowing down means recovery takes longer — the sensitivity is bought with recoverability. Doing it deliberately requires continuously measuring how far from criticality you are, and Section 5 explains why that is often impossible.
Because it is a binary judgement while the mechanism emits a continuous signal. Before the transition, the system returns to baseline every single time — until the last time, when it doesn't. A binary test outputs "normal" across the entire window in which warning was possible, and its first alarm coincides with the event. Every monitor that binarises a continuous quantity has this problem, not just this one.