Substrate Depletion Dashboard¶

A substrate monitor — instantiates Sustainable Load Envelope Governance

Puts the substrate's condition — stock level and depletion rate — on one screen beside throughput and sustained demand, so the hidden cost of today's output is visible next to the output.

Substrate Depletion Dashboard instruments the thing that usually goes unwatched — the renewing substrate on which future capacity depends — and shows it beside the throughput everyone already tracks. Its defining move is juxtaposition: by putting depletion and demand on one screen, it makes visible the trade the archetype warns about, that a system can post healthy output while quietly spending down the stock that produces it. It favours leading signs of exhaustion over the lagging evidence of collapse, and it reports rate and direction, not just level — a stock that is adequate today but falling fast is exactly the signal a raw output number hides.

Example¶

A consulting firm watches one number above all others: billable utilization. It looks excellent — in the low nineties — right up until three senior engagement leads resign in a single quarter and two deliveries slip. The Substrate Depletion Dashboard is built to catch that a year earlier by showing the people substrate next to the throughput. Beside utilization it displays unused-leave backlog and consecutive high-intensity weeks (recovery debt), the trend in voluntary-attrition and internal-transfer requests (early exit signals), and the ratio of experienced to junior staff on live work (the stock of tacit capacity). Read together, the picture inverts: the same low-nineties utilization that read as efficiency now reads as a substrate being drawn down — high output funded by rest and expertise that are not being replaced. The dashboard sets no limit and fixes nothing; it makes the depletion legible while there is still time to act.

How it works¶

Instrument the substrate, not just the output. Add indicators for stock level and depletion rate to the throughput metrics already in view.
Prefer leading indicators. Track the early, reversible signs — rising recovery debt, thinning reserves — rather than the terminal ones like attrition or breakdown.
Juxtapose deliberately. Place substrate and demand on one view so the cost side sits next to the benefit side and cannot be read in isolation.
Show rate and direction, not only level — the slope of the decline is the part a snapshot misses.

What makes it this mechanism and not a chart is that it measures and displays live indicators; it does not interpret them into zones or pass a verdict.

Tuning parameters¶

Indicator set — which signals to trust as proxies for a stock that is often hard to measure directly. The choice determines what the dashboard can even see.
Leading-versus-lagging balance — how far upstream to reach; earlier signals give more lead time but are noisier and easier to dismiss.
Granularity — system-wide totals versus per-unit breakdown (which team, which asset), trading legibility for the ability to catch local depletion hidden in a healthy average.
Sampling cadence — how often indicators refresh; a slowly-renewing substrate can be sampled coarsely, a fast one needs a tighter loop.
Baseline & normalization — what counts as "full" versus "depleted," and whether indicators are shown raw or against a healthy reference band.

When it helps, and when it misleads¶

Its strength is that it defeats the archetype's core trap — output that flatters while the substrate drains — by refusing to show throughput alone. Because it favours leading indicators, it buys lead time that a lagging metric such as attrition or equipment failure never gives.^[1]

A dashboard measures proxies, and the substrate is usually the hard-to-measure side, so a confident green readout can reflect a convenient indicator rather than the true stock. Dashboards also breed "watermelon" reporting — green on the surface, red underneath — when indicators are chosen or aggregated to reassure. And measurement is not management: a beautifully instrumented decline that no rule acts on is just a well-documented one. The discipline is to choose indicators for fidelity to the real substrate rather than convenience, show rate alongside level, and wire the dashboard to the limits and reviews that actually respond.

How it implements the components¶

depletion_stock_indicator — its core readout: how much of the capacity substrate remains and how fast it is being drawn down.
sustained_demand_metric — the throughput it places beside the substrate, framed as sustained load rather than a momentary peak, so the two can be read against each other.

It does not partition the readings into safe zones (Safe Operating Envelope Chart), take the ground-truth field measurements that feed it (Ecosystem or Asset Monitoring Transect), or log discrete over-envelope events as an audit trail (Capacity Drawdown Ledger).

Instantiates: Sustainable Load Envelope Governance — it is the sensory layer of the envelope, making the substrate's condition observable so the rest of the governance acts on evidence.
Sibling mechanisms: Safe Operating Envelope Chart · Capacity Drawdown Ledger · Ecosystem or Asset Monitoring Transect · Carrying Capacity Assessment · Regenerative Budget · Recovery Window or Rest Period · Sustainable Yield Quota · Utilization Ceiling and Headroom Rule · Demand Admission Gate · Load Shedding Trigger · Capacity Envelope Review Board

Notes¶

The dashboard, Capacity Drawdown Ledger, and Ecosystem or Asset Monitoring Transect all watch the substrate, differently: the dashboard shows continuous live indicators, the ledger records discrete drawdown events and exceptions as an audit trail, and the transect takes ground-truth field measurements on a sampling schedule. The dashboard is the real-time face; the other two feed and corroborate it.

References¶

[1] Leading versus lagging indicators — leading indicators move before the outcome and give time to act (recovery debt, reserve drawdown); lagging ones confirm it after the fact (attrition, outage, collapse). A depletion dashboard earns its keep by surfacing the leading signals a throughput-only view omits. ↩