Skip to content

Reach Limit Gate

Rule / checkpoint — instantiates Sustainment-Reach Alignment

A preset stop-line that halts the front's advance at the reach where added extension would begin subtracting from sustainment.

Most overreach happens one reasonable step at a time; no single advance looks like the one that breaks the line. Reach Limit Gate forecloses that drift by fixing the limit in advance — a hard stop-line, set at the crossover where the next increment of reach would consume more sustainment than it delivers, past which the front may not advance without an explicit, senior override. Its defining move is that the limit is pre-committed and binding: not a gauge to consult (that's the dashboard) or a model to run (that's the capacity model), but a checkpoint that says no further, here and forces the decision to stop into the open rather than letting momentum erode it. It guarantees the stop happens; it does not plan what to do afterward.

Example

A wildland fire crew is building containment line down a ridge. Every hundred metres of new line is another hundred metres to hold, patrol, and re-supply with water and hose. The Reach Limit Gate is the discipline written before the shift: the line may not extend past the point where an engine can still lay water to the working edge and crews keep a viable escape route to a safety zone — the anchor-point and LCES (Lookouts, Communications, Escape routes, Safety zones) rule every wildland firefighter is trained on.

Mid-afternoon the fire runs downhill fast and the edge tempts the crew another quarter-mile. The gate trips: beyond the last water-reachable point, each added metre of line can't be held and turns from an asset into an exposed flank. Rather than chase it, the crew holds at the gate and the advance simply stops there — the extension that would have subtracted from their ability to sustain any line is not taken. What to do next — fall back to a road, or wait for the fire to consolidate — is handed to the rescope and pause playbooks. The gate's one job was to keep the crew from walking past the line they couldn't feed.

How it works

  • Set the line before you need it. Locate the stop at the modeled and measured crossover, decided in the calm before the advance rather than in its heat.
  • Make it binding, not advisory. Crossing requires a named override at a named level, logged — so continuing is a decision someone owns, not a silent default.
  • Trip on a leading signal. Tie the gate to a forward indicator (net-delivery slope, escape-route time, buffer days) so it fires before the crossover, not after.
  • Stop only; hand off the rest. On a trip the gate halts advance and wakes the pause and rescope mechanisms; it does not itself plan the pullback.

Its distinguishing feature is pre-commitment plus a binding override — the opposite of an advisory gauge you are free to talk yourself past.

Tuning parameters

  • Margin below the crossover — flush with the crossover maximizes reach but leaves no buffer; set back from it trades reach for a safety margin.
  • Override height — who may wave the front through (shift lead vs. incident commander vs. board). Higher makes the gate stickier and harder to erode.
  • Trip signal and lead — which forward indicator trips it, and how early. Earlier trips are safer but forfeit reach that might have held.
  • Hard vs. soft gate — an absolute bar versus a "stop-and-justify" checkpoint. Hard gates resist momentum; soft gates keep flexibility at the cost of erodibility.
  • Reset condition — what must improve (sustainment restored, line shortened) before the gate reopens.

When it helps, and when it misleads

Its strength is defeating incrementalism — the way a front creeps past its support in steps none of which alone looked fatal — by moving the stop decision ahead of the momentum and making it binding. It is the operational form of Clausewitz's culminating point: the reach beyond which an advance grows weaker, not stronger.[1]

A gate set on a stale or optimistic crossover stops in the wrong place — too early wastes real reach, too late doesn't bind at all. The classic misuse is the routine override: the gate exists but is waved through every time, becoming theater that launders overreach as due diligence. It also can't distinguish a disciplined hold from paralysis. The discipline is to source the line from a live crossover estimate, keep override friction real and logged, and audit override frequency — a gate that never binds is mis-set.

How it implements the components

Reach Limit Gate realizes the governing side of the archetype — the components a binding rule can fill:

  • crossover_threshold — the gate is a commitment to a specific crossover: the reach at which added extension turns net-negative.
  • front_pace_gate — it governs the advance decision itself, converting that threshold into a binding "advance / hold" checkpoint on the front's pace.

It does not measure the live ratio that locates the crossover (net_delivery_metric, line_health_monitor) — that is Net Supply Ratio Dashboard; and it does not plan the pullback once it trips (retraction_or_rescope_rule) — that is Front Rescope Playbook.

  • Instantiates: Sustainment-Reach Alignment — the gate is its enforced stop-line.
  • Consumes: Net Supply Ratio Dashboard and Line-of-Support Capacity Model — the live and modeled crossover the gate enforces.
  • Sibling mechanisms: Front Rescope Playbook · Net Supply Ratio Dashboard · Advance Pause & Consolidation Window · Priority Supply Ladder · Relay Hub Network · Support Burn-Rate Review · Support Line Postmortem · Forward Staging Cache · Lead-Time Stress Simulation · Line-of-Support Capacity Model · Local Sourcing & Repair Protocol

Notes

The gate stops further advance; it does not shorten a line that is already overextended. If you are already past the crossover, the fix is the Front Rescope Playbook, not the gate. And a gate limits reach, not the pace of consumption — a front that sits still at the limit can still burn out its line over time, which is the Support Burn-Rate Review's beat, not this one's.

References

[1] Clausewitz, in On War, describes the "culminating point of the attack" — the point at which an advancing force's strength stops growing with further advance and begins to decline, as the lengthening line consumes it. A reach limit gate is a pre-commitment to stop there.