Skip to content

Slack-Erosion Test

Reserve-floor review — instantiates Internal Capacity Deepening

Checks whether an intensification proposal pushes protected slack — maintenance, recovery, surge, safety, or redundancy reserves — below an explicit floor.

Intensification's real danger is not that a position is too full but that the reserves it quietly relied on are gone. Slack-Erosion Test is a pass/fail check applied to any density proposal, asking one question: does this consume maintenance, recovery, surge, safety, ecological, or innovation slack below a floor set in advance? Its defining discipline is that the floor is declared before the proposal is scored, because slack looks exactly like waste in calm conditions — the argument to cut it is always available and always locally correct, right up until the shock that the slack existed to absorb. The test makes that reserve non-negotiable rather than a variable to be optimised away.

Example

An airline wants to add a fourth daily rotation to an aircraft by trimming ground turnaround from 50 to 35 minutes. On a normal day it works. The Slack-Erosion Test scores it against a pre-set floor: the schedule must retain enough recovery buffer to reabsorb a typical morning delay by end of day without cancelling, and enough maintenance window to keep required checks on cadence. The tighter turn erases the buffer that let a late inbound catch up — one delay now propagates through all four legs and misconnects passengers downline — and it eats into the overnight maintenance slot. The proposal fails not on its average day but on its bad day, and is sent back to find the extra rotation somewhere that doesn't spend the reserve.

How it works

What distinguishes the test from a general load model is that it evaluates against declared floors, not against feasibility. Each reserve — recovery buffer, maintenance window, surge headroom, redundancy margin — has a floor fixed ahead of time, ideally justified by the shock it must survive. The proposal is scored on its stressed state, not its nominal one, because slack only shows its value under load. The output is binary with a reason: pass, or fail-with-the-reserve-it-breaches. Crucially, the floor is set before the proposal is seen, so the test cannot be argued down in the moment.

Tuning parameters

  • Floor levels — how much of each reserve is protected. Higher floors buy resilience but leave more capacity unharvested; the setting encodes how much shock you must survive.
  • Reserve coverage — which slacks are protected (maintenance, recovery, surge, safety, ecological, innovation). A reserve left off the list is one the test will happily let a proposal spend.
  • Stress scenario — the shock the reserve is tested against (a typical delay, a demand spike, a component failure). Set it too mild and the floor protects against nothing real.
  • Waiver policy — whether a floor can ever be breached, by whom, and with what compensating reserve. Loose waivers quietly turn a hard floor back into a soft target.

When it helps, and when it misleads

Its strength is protecting the reserves that never appear in a capacity count and are always the first thing an efficiency drive targets — it converts "we still have headroom" into a checkable claim about a named shock. It is the archetype's brake on intensifying a system into brittleness.

It misleads when the floors are set to be passed rather than to be survived. Slack cannot be felt until it is gone — a system stripped of reserve runs beautifully until the shock arrives, so a test whose floors are quietly lowered to clear a favoured proposal fails silently.[1] It can also over-protect, hoarding reserve against shocks that no longer apply and starving genuine capacity. And a floor defended in isolation misses that removing slack tightens coupling, so failures that used to stay local now cascade. The discipline is to tie each floor to a specific shock, score proposals on their stressed state, and revisit floors as the real shock profile changes — not as the pressure to intensify rises.

How it implements the components

This test fills the reserve-protection slice of the archetype — the floors intensification must not cross:

  • protected_capacity — the explicit floors on maintenance, recovery, surge, safety, ecological, and innovation slack that the test enforces.
  • resilience_and_redundancy_guardrail — the redundancy and recovery margins whose breach the test flags, scored against a named shock rather than an average day.

It does not model how load propagates through support systems — that is the Infrastructure-Load Simulation — nor does it authorize the increment; it hands a pass/fail to the Phased Intensification Gate, which decides.

References

[1] Charles Perrow's normal-accident theory links tight coupling and low slack to cascading failure: the more slack a system sheds, the more tightly its parts are coupled, and the faster a local fault propagates system-wide — which is why removing reserve trades visible efficiency for invisible fragility. ↩