Sink Capacity Audit¶

Audit — instantiates Overshoot-Crash Load Management

Verifies that every receiving system — treatment plant, court, landfill, labor market, balance sheet — can actually absorb the planned drawdown without hidden overload, unfair burden-dumping, or delayed failure.

A drawdown protects the focal system only if the load it sheds lands somewhere that can take it. Sink Capacity Audit is the check that tests exactly that: for every sink the unwind routes into, it asks whether that sink can absorb the planned volume without hidden overload, inequitable burden transfer, or delayed failure — and it converts the answer into a hard ceiling per sink plus an explicit list of the downstream functions and parties that must be protected. Its defining posture is that it sets limits and can say no: where the clearance mechanism builds more capacity, the audit measures the capacity that truly exists and caps the load accordingly. That gatekeeping role — protecting the receiving end from being quietly sacrificed to save the focal system — is what distinguishes it from every capacity-building sibling.

Example¶

A utility plans to retire several aging plants over three years, releasing a large workforce. The "sinks" absorbing that drawdown are the regional labor markets, unemployment services, retraining programs, and local housing. The audit examines each. It finds that two small plant-towns would absorb three-to-four times their normal unemployment caseload if the retirements land together (hidden overload), and that older workers disproportionately fall into long-term unemployment the local market never re-absorbs (inequitable transfer, and a delayed failure that surfaces long after the plants close).

The audit's output is not encouragement but constraints: a per-town intake ceiling, a protected-cohort provision for older workers, and a flag that the plan is infeasible unless retraining and hiring capacity grow first. Framed as a just transition obligation, the audit is what turns that principle into checkable limits^[1] rather than a slogan — and what stops the utility from balancing its own books by dumping a solvable problem onto the least-resilient towns.

How it works¶

Enumerate every sink. List each disposal, settlement, treatment, absorption, or recovery system the drawdown routes load into — including the informal ones no one planned for.
Measure real spare capacity. Assess each sink's realistic headroom under stress, not its nameplate rating; a sink at 90% baseline utilization has little to give.
Test distribution, not just totals. Check who bears the load, because a system-average that looks fine can hide a few sinks or communities carrying all of it.
Set the ceiling. Output a maximum load per sink and a protected-function list, so the drawdown and clearance mechanisms have a hard limit to plan within.

Tuning parameters¶

Audit scope — which sinks are counted. Too narrow and the audit blesses a plan that overloads an unexamined downstream system; wider scope costs effort but closes blind spots.
Capacity definition — nameplate, realistic spare, or stressed spare. The more conservative the definition, the lower and safer the ceiling.
Distributional granularity — system-average versus per-community / per-cohort. Finer granularity is what surfaces inequitable burden transfer.
Margin / haircut — how much headroom to reserve against correlated timing and estimate error. A thin margin re-imports the overshoot risk into the sink.
Refresh cadence — one-shot sign-off or re-audit as the drawdown proceeds and real absorption data arrives.

When it helps, and when it misleads¶

Its strength is preventing the intervention from protecting the focal system by overloading a downstream ecosystem, institution, workforce, or community — the failure mode where the "fix" simply relocates the crash.

Its central misuse is being run backwards: convened after the drawdown is already decided, the audit rubber-stamps it by setting the ceiling to whatever the plan needs rather than to what the sinks can bear. Nameplate-capacity optimism inflates the headroom, and system-average thinking hides the communities actually carrying the load. The discipline that keeps it honest is independence from the drawdown owner, capacity measured under stress rather than on paper, and a mandatory distributional cut so the ceiling protects the vulnerable and not just the aggregate.

How it implements the components¶

Sink Capacity Audit realizes the archetype's limit-and-protection layer — the checks that bound where load may go:

sink_capacity_threshold — its primary output: the verified maximum load that may be routed into each sink during the unwind.
critical_function_map — the audit's distributional check identifies the downstream functions, communities, and vulnerable parties that emergency measures must not sacrifice.

It does not build or accelerate the channel — raising throughput is Clearance Pathway Enhancement (clearance_path, downstream_absorption_capacity) — nor pace the unwind, which is Controlled Drawdown Schedule. Note the boundary: it caps load into a downstream sink; the minimum reserve the focal system must keep for itself is secondary_resource_floor, held by Secondary-Capacity Reserve Activation.

Instantiates: Overshoot-Crash Load Management — this audit supplies the ceilings the drawdown and clearance mechanisms must plan within.
Consumes: Growth-and-Crash Stock-Flow Model supplies the crash-load forecast the audit tests each sink against.
Sibling mechanisms: Clearance Pathway Enhancement · Controlled Drawdown Schedule · Cohort Staggering · Secondary-Capacity Reserve Activation · Hotspot Containment and Removal · Growth-and-Crash Stock-Flow Model · Source Reduction Program · Saturation Dashboard · Early Warning Indicator · Threshold-Triggered Input Cap · Staged Harvesting or Decommissioning · Post-Crash Residual-Load Dashboard · Reentry Gate Review

Notes¶

Keep the two ceilings distinct. The sink capacity threshold limits how much load a downstream system may receive; the secondary resource floor (Secondary-Capacity Reserve Activation) sets how much of its own critical resource the focal system must retain. Conflating them tends to protect the aggregate while silently overloading whichever party is least able to object.

References¶

[1] Just transition — the principle that winding down an activity should not concentrate its costs on the workers and communities least able to bear them. The audit operationalizes it by turning distributional protection into explicit per-sink ceilings and protected-cohort provisions rather than leaving it aspirational. ↩