Skip to content

Absolute Resource-Budget Protocol

Governance protocol — instantiates Rebound-Aware Efficiency Governance

Converts a per-unit efficiency gain into a binding ceiling on total resource use, with a stated rebound tolerance, so a smaller unit cannot quietly become a larger system.

An efficiency project delivers a per-unit number — less water per fixture, less energy per unit output — but the thing the environment actually feels is the total. Absolute Resource-Budget Protocol is the rule that pins the decision to that total: it fixes a binding ceiling on aggregate resource use, expressed in physical quantity rather than as a percentage improvement, plus an explicit tolerance band for how much rebound is allowed before the ceiling is breached. Its defining move is that the cap is absolute and exogenous — anchored to a real limit (an aquifer's recharge, a carbon budget) rather than to the engineering forecast — so that making each unit cheaper cannot license the total to grow. It sets the number and the band; it deliberately holds no levers of its own.

Example

A municipal water utility subsidizes efficient fixtures across the city and watches per-household water intensity fall by roughly a fifth. Left there, the win is illusory — cheaper, "guilt-free" water tends to become longer showers and greener lawns. Instead the utility writes an Absolute Resource-Budget Protocol: total citywide withdrawal is capped at a figure tied to sustainable aquifer recharge (an external physical limit, not last year's demand), with a rebound tolerance that total use may drift up at most ≈2% during the transition before the cap is considered breached. The protocol also states how the budget is apportioned among districts and the process for a drought-year exception. From that point the efficiency program is judged against the absolute budget, not the per-fixture figure — and the day total use approaches the ceiling, the program is a success or a failure on the only axis that matters.

How it works

What distinguishes this protocol from a target or a forecast is where the number comes from and whether it binds. The ceiling is anchored to a physically or ecologically meaningful quantity, so it does not move when efficiency improves. It is written to be enforceable — a cap, not an aspiration — and carries an explicit tolerance band that names how much rebound counts as acceptable versus a breach. It fixes revisit triggers (when the budget is re-examined) but hands the watching, the pricing, and the correction to other mechanisms. The protocol is the constraint; the teeth live elsewhere.

Tuning parameters

  • Budget basis — anchor to a physical/ecological limit or to a negotiated political target. A hard physical anchor resists rebound but is harder to agree.
  • Absolute vs. per-capita framing — a fixed total cap or a per-head cap. Per-capita accommodates population growth but lets the total creep upward.
  • Tolerance width — how much rebound the band permits before it is a breach. Wide bands avoid false alarms but let savings quietly erode.
  • Bindingness — hard cap versus soft target: enforceability traded against political feasibility.
  • Ratchet cadence — a fixed ceiling or one that tightens on schedule. A ratchet locks in gains but needs standing buy-in.

When it helps, and when it misleads

Its strength is re-anchoring "success" on the absolute quantity that actually matters, which is precisely the quantity a unit-efficiency metric can rise while pretending to fall. That guards against the Jevons trap, where more efficient use of a resource increases its total consumption.[1] Its failure modes are all about how the number is set: a cap derived from a forecast that already bakes in expected growth is too loose to bind, and any cap invites activity to slip across its boundary rather than shrink. The classic misuse is to set the budget equal to the engineering forecast so it can never actually constrain anything — a ceiling drawn just above where the ball was always going to land. The discipline that keeps it honest is to anchor the cap to an external physical limit and to let a boundary review test whether use is truly falling or merely leaking past the accounting line.

How it implements the components

Absolute Resource-Budget Protocol fills the archetype's constraint components — the number and the band, not the machinery around them:

  • total_resource_use_target — its core output: the binding, physically anchored ceiling on aggregate use.
  • rebound_budget_or_tolerance — the explicit band naming how much rebound is tolerated around that ceiling before it counts as a breach.

It does not name the accountable owner or sweep the savings — that is the Efficiency-Dividend Lockbox; it does not watch the total or fire corrections when the band is breached — that is Rebound-Triggered Policy Recalibration; and it does not apply the demand-side price or quota levers — those are the pricing and Quota System siblings.

Notes

The protocol is deliberately just the number and the band — it has no enforcement of its own. That is a feature: it lets the ceiling be debated and set on the merits of the physical limit, separately from the political fight over which lever pulls total use back into line. But it also means an Absolute Resource-Budget Protocol adopted without a paired recalibration loop and an accountable owner is a declaration, not a control.

References

[1] The observation that improving the efficiency with which a resource is used can increase, rather than reduce, the total amount consumed — named for William Stanley Jevons, who described it for coal in 1865. It is the reason a unit-efficiency gain has to be governed against an absolute total rather than trusted to shrink the system on its own. ↩