Load Shedding Trigger¶

An operational-control rule — instantiates Sustainable Load Envelope Governance

Fires a pre-defined, staged reduction of service, extraction, or commitments the moment a depletion band is crossed — cutting load already being carried, in a set order, before a breach turns into substrate damage.

Prevention sometimes fails: demand already inside the system pushes it past a warning band and toward real substrate damage. Load Shedding Trigger is the last line — the rule that, the moment a depletion band is crossed, fires a pre-defined staged reduction of load already being carried, in an order agreed in advance. It does not deliberate in the crisis; it executes a committed escalation ladder that trades some current demand to keep the substrate from lasting harm. Its defining move is twofold: it acts on load already admitted rather than refusing new demand, and it carries an explicit order of who is cut first, so the hard distributional choice is settled calmly beforehand instead of improvised under stress.

Example¶

A power grid faces sustained demand outrunning what generation and reserves can carry without frequency collapse. When frequency falls through a set band, an underfrequency load-shedding scheme automatically drops pre-designated blocks in stages: non-critical industrial feeders first, then rotating residential blocks, with hospitals and critical infrastructure shed last, if ever. The trigger does not debate; it fires the ladder to protect the grid — the substrate — from a cascading, system-wide blackout that would be far worse than a partial, controlled cut. The order and rotation are a distributional decision made in advance: which sectors and neighborhoods bear the reduction, and how the burden rotates so the same feeders are not sacrificed every single time.

How it works¶

The trigger maps depletion or warning bands to shedding stages: cross a band, shed the increment assigned to it. Firing is automatic or fast-authorized, because the value is speed at the moment of breach. Each stage carries a fixed priority and rotation order for what sheds and in what sequence. What makes it this mechanism is that it is a pre-committed escalation ladder on load already carried, with the burden allocation decided ahead of the event — not a fresh judgment call made while the system is failing.

Tuning parameters¶

Trigger bands — where the shedding thresholds sit relative to the envelope edge. Early bands protect the substrate with more false alarms; late bands cut only when truly necessary but risk firing too late.
Shed increment — how much load each stage drops. Fine increments shed just enough but react in more steps; coarse increments act fast but overshoot.
Priority and rotation order — which loads shed first and how the burden rotates. This sets who bears the cut and whether the same parties are hit every time.
Automation versus authorization — fully automatic firing versus a required human sign-off. Automation is fast and reliable but blunt; authorization adds judgment and delay.
Restoration rule — how far conditions must recover before shed load is restored, so the trigger does not oscillate on and off at the band edge.

When it helps, and when it misleads¶

Its strength is a pre-committed, fast response that protects the substrate at the moment of breach, with the wrenching distributional choices made deliberately in advance rather than improvised in a crisis. It generalizes underfrequency load shedding, the automatic grid scheme that disconnects pre-designated blocks when frequency drops, to any depletable substrate.^[1]

Its failure modes are firing too late — when bands are keyed to lagging indicators, the trigger acts only once damage is under way — and entrenched inequity, when the shedding order repeatedly cuts the same parties until "rotation" is a fiction. The classic misuse is raising or disabling the trigger under pressure ("just this once"), so the protection is absent exactly when it is needed. The discipline that guards against this is bands tied to leading substrate indicators, a rotation that genuinely spreads the burden, and treating frequent shedding as a symptom to fix upstream rather than a tool to lean on.

How it implements the components¶

breach_response_path — it is the defined escalation: the mapping from crossed depletion bands to staged load reductions that fires when the envelope is breached.
distributional_burden_map — its priority-and-rotation order encodes who or what bears each reduction, and in what sequence, decided ahead of the event rather than in it.

It does not sense the depletion it reacts to — Ecosystem or Asset Monitoring Transect and the substrate depletion dashboard produce the indicator it watches — nor define the envelope and its bands (Carrying Capacity Assessment and safe operating envelope chart); and unlike Demand Admission Gate, it removes load already carried rather than refusing new demand.

Instantiates: Sustainable Load Envelope Governance — it is the last-line control that protects the substrate at the moment of breach.
Consumes: Ecosystem or Asset Monitoring Transect and Substrate Depletion Dashboard supply the depletion indicator whose bands the trigger fires on.
Sibling mechanisms: Demand Admission Gate · Substrate Depletion Dashboard · Ecosystem or Asset Monitoring Transect · Carrying Capacity Assessment · Safe Operating Envelope Chart · Capacity Drawdown Ledger · Capacity Envelope Review Board · Sustainable Yield Quota · Recovery Window or Rest Period · Regenerative Budget · Utilization Ceiling and Headroom Rule

Notes¶

The demand admission gate and the load shedding trigger are the two enforcement halves and must not be conflated: the gate refuses new demand at the door; the trigger reduces demand already carried. Because shedding is the last line, standing reliance on it is a symptom, not a solution — if the trigger fires often, the envelope is set too high or the gate is too loose, and the real fix is upstream.

References¶

[1] Underfrequency load shedding (UFLS) — the standard power-system scheme that automatically disconnects pre-designated blocks of load when grid frequency falls through set thresholds, sacrificing some demand to keep the whole system from collapsing. Its defining features — predefined stages and a fixed shed order — are what a load-shedding trigger generalizes to any depletable substrate. ↩