Tensions in Practice: An old capacity estimate and a changing support base¶

An illustrative grazed field

A field’s ability to support grazing depends on the condition of its resource base. If earlier use has degraded that base, an old capacity estimate can permit more use than the field now sustains. Continuing the old plan preserves the current allocation; reassessing conditions can lead to less grazing, but takes evidence and may reduce useful activity even before visible output collapses.

Keep a usable operating plan

Avoid changing current allocations without a good reason.

Respect the current support base

Let evidence about resource condition change what use is considered sustainable.

Why these aims pull against each other

The limit is not independent of past use: sustained overload can reduce the base that supports future use. Reusing an old number saves assessment work while potentially planning against capacity that no longer exists.

Compare the arrangements

Reuse the old limit

Set the current grazing allocation from the earlier estimate. If the field has degraded, that unchanged allocation can exceed its present limit.

What it protects: The plan remains predictable and avoids repeated assessment when the support base is actually stable.
What it costs: After degradation, an apparently unchanged plan can prolong overload and further reduce future capacity.
When it fits: Plausible only when there is justified evidence that the old estimate still fits current conditions; a brief successful burst is not that evidence.

Illustration note: The field is a qualitative example. The conditional arrows describe the assumed erosion regime, not a forecast that every grazing plan degrades a field.

Reassess and adjust

Assess the field’s present support base, revise the estimated sustainable limit, and change grazing accordingly. Subsequent condition informs the next assessment.

What it protects: Planning can respond to capacity lost through earlier use instead of repeatedly treating the old limit as valid.
What it costs: Assessment costs effort and can be wrong. Reducing use affects current beneficiaries, and regeneration may still require time.
When it fits: Plausible when relevant condition can be assessed and the allocation can actually change; a monitoring report alone is insufficient.

Illustration note: The feedback is an editorial application of T4. It does not supply a stocking rate, a recovery time, or a promise that reduced use restores every damaged system.

What this illustration does—and does not—establish

Carrying Capacity: Static Threshold versus Endogenous Erosion (coupling) supplies the endogenous erosion mechanism. The field and reassessment loop are editorial applications that show why a past estimate and a current limit need not match.

The example assumes a resource-eroding overload mechanism. It is not a calibrated ecological model or land-management recommendation.
No capacity curve, threshold, carrying number, or recovery rate is inferred from the picture. Local evidence is needed to identify the actual regime.
Holding a reserve below a fixed capacity is a different choice. Here the key change is the capacity itself, not just the amount of unused room.

Source entries

Carrying Capacity

Prime · Source of the tension

Carrying Capacity: Static Threshold versus Endogenous Erosion (coupling) supplies the history-dependent limit. The boundary passage distinguishes a changing capacity from a reserve held below a fixed limit.

T4

T4 — Static Threshold versus Endogenous Erosion (coupling). Carrying-capacity analysis often treats K as a fixed parameter to operate beneath, but the prime's defining feature is that overshoot *lowers K itself* — the threshold is coupled to the history of how it was loaded. The failure mode is planning against yesterday's capacity number after the substrate has already been degraded, so the "safe" operating point is now above the eroded ceiling. Diagnostic: ask whether the system has recently been run hard; if so, re-measure K rather than trusting the design value. Treating capacity as an exogenous constant when it is endogenous to load history is how organizations keep setting targets a depleted team can no longer meet.

Read the source section

The capacity itself can change

- Not a margin of safety. margin_of_safety is the headroom held between rated load and worst-case demand — a buffer. Carrying capacity is the *rated limit itself*, with its defining feature being the substrate-eroding feedback past the threshold. Margin is a policy about where to sit relative to capacity; capacity is the curve.