Post-Crash Residual-Load Dashboard¶

Monitoring dashboard — instantiates Overshoot-Crash Load Management

Tracks the delayed secondary load after the visible peak has passed — showing whether the system is truly clearing or only looks quiet while the tail builds.

A Post-Crash Residual-Load Dashboard watches the part of the story everyone else stops watching: the slow, delayed burden that keeps building after the growth stock has peaked and the crisis appears to be over. Its defining premise is that the visible peak and the dangerous peak are different events — the secondary load (cleanup, claims, disposal, oxygen demand, support debt) often crests well after the stock itself has fallen, so a system can look calm while its real load is still rising. Where a pre-peak Saturation Dashboard watches growth approach the threshold, this one watches the tail recede; it makes that delayed burden visible and checks whether the resources absorbing it are themselves nearing saturation, so that "the crash is over" becomes a measured claim rather than a hopeful one.

Example¶

A country's smartphone boom peaks; sales fall, and the story reads as "the market matured." But the handsets sold at the top of the boom are a delayed disposal stock: two or three years on, they arrive as e-waste, and the crash load is the surge of toxic dismantling, recycling backlog, and leachate risk. A residual-load dashboard tracks that tail — tonnes entering the waste stream, recycler queue depth, informal-sector exposure — and runs a secondary-saturation check on the recyclers and landfills receiving it.

It shows the load cresting roughly two to three years after the sales peak, long after headlines moved on. That lag is exactly what a growth-phase dashboard, stood down at the peak, would miss — and it is what tells regulators the clearance system is about to be overwhelmed even though "the boom is over." The dashboard's value is entirely in the months after everyone else looked away.

How it works¶

Meter the tail, not the peak. Its indicators are the delayed secondary stressors — claims, disposal, decomposition demand, support debt — that rise after the stock falls.
Check the absorbers. A secondary-saturation check watches whether the sinks and resources processing the tail are nearing their own limits, not just the headline load.
Separate "quiet" from "cleared." It distinguishes a genuine decline in load from a lull that merely precedes the delayed crest.
Run past the all-clear. Monitoring continues through the slow tail, because the whole point is to catch the load that arrives after attention has moved on.

Tuning parameters¶

Tail horizon — how long after the peak monitoring continues; too short and the dashboard goes dark before the real crest, too long and it costs attention indefinitely.
Leading vs. lagging mix — how much weight sits on early proxies of the coming tail versus confirmed load already arrived.
Absorber thresholds — how close a receiving sink may get to saturation before the check flags it.
Disaggregation — whether load is tracked in aggregate or by cohort and region, which decides whether a concentrated local crest can hide inside a calm average.
All-clear criteria — how much sustained decline counts as genuine clearance versus a temporary lull.

When it helps, and when it misleads¶

Its strength is that it defeats the premature all-clear. The dashboard's entire value is in refusing to declare victory at the visible peak, and in catching the secondary crest while there is still time to add clearance capacity or defend a floor. The absorber check is what stops the tail from quietly overwhelming the cleanup system unnoticed.

Its failure modes are mostly about scope and timing. A horizon set too short goes dark right before the real crest; aggregate-only views let a concentrated local tail vanish into a calm system average; and lagging indicators can confirm the overload only once it has arrived. The classic misuse is reading the stock's decline as proof of safety and standing the dashboard down — mistaking a quieter peak for a cleared one, when recovery paths so often show hysteresis and the tail persists far longer than the boom that produced it.^[1] The discipline is to fix the tail horizon to the load's known lag, disaggregate, and keep watching past the point at which it feels unnecessary.

How it implements the components¶

residual_load_signal — its core output: a live measure of the delayed secondary burden after the peak, showing whether the system is genuinely clearing or only appearing quieter.
secondary_saturation_check — it checks whether the sinks and resources absorbing the tail are themselves approaching saturation, not just whether the headline load level is falling.

It does not monitor the pre-peak growth stock and its approach to the threshold (Saturation Dashboard, Early Warning Indicator), model how much crash load the peak will produce (Growth-and-Crash Stock-Flow Model), or expand the clearance capacity it watches (Clearance Pathway Enhancement). It measures the tail; it does not size, forecast, or clear it.

Instantiates: Overshoot-Crash Load Management — the eyes on the slow tail, the phase the rest of the sequence is most tempted to stop watching.
Consumes: the crash-load forecast that calibrates which tail to expect and for how long (Growth-and-Crash Stock-Flow Model).
Sibling mechanisms: Reentry Gate Review · Saturation Dashboard · Early Warning Indicator · Growth-and-Crash Stock-Flow Model · Clearance Pathway Enhancement · Hotspot Containment and Removal · Sink Capacity Audit · Threshold-Triggered Input Cap · Source Reduction Program · Controlled Drawdown Schedule · Cohort Staggering · Staged Harvesting or Decommissioning · Secondary-Capacity Reserve Activation

Notes¶

This dashboard's readings are the primary evidence a Reentry Gate Review consumes to decide whether recovery is real. Standing it down early does not just lose visibility — it blinds the gate, which is then forced to judge readiness against a system it can no longer see.

References¶

[1] Hysteresis — a system not retracing on the way down the path it took on the way up — is why the residual tail outlasts the crash: the load created at peak clears on a slower, different curve than the stock that produced it, so a decline in the stock does not imply a decline in the burden. ↩