Maintenance Funded by Use¶

Policy — instantiates Autopoietic Self-Maintenance

Ring-fences a fixed share of a system's operating revenue or usage and routes it straight to the maintenance capacities that produce the value, so upkeep is funded automatically instead of begged for.

Systems that produce value tend to spend it all on producing more, starving the very upkeep that keeps them able to produce — until the neglected foundation fails. Maintenance Funded by Use is the funding rule that breaks this trap: a defined portion of revenue, usage fees, or surplus is ring-fenced at the source and channeled to maintenance — the people, infrastructure, and reserves that renewal depends on — before the rest is spent. Its defining move is coupling the funding of maintenance to the level of use, so that the more the system is drawn on, the more is automatically set aside to renew it, rather than leaving upkeep to compete for discretionary budget it always loses.

Example¶

A city water utility has been running its pipes to failure. Each year the operating budget covers staff, chemicals, and pumping, and pipe replacement is "next year's problem" — until a decades-old main bursts under a downtown street. The utility adopts a funded-by-use rule: a fixed fraction of every water bill — call it ≈15% of the volumetric rate — is ring-fenced into a renewal fund that may only be spent on replacing and rehabilitating mains, and a small asset-management team is chartered to own that fund and report on it. Because the levy scales with water sold, heavy-use years automatically generate more renewal money. Within a few budget cycles the replacement rate rises from "whatever's left over" (near zero) to a steady schedule, and the council can see, in a single reported number, whether the system is being renewed as fast as it wears out.

How it works¶

Fund at the source, not from the surplus. The maintenance share is taken off the top and locked to its purpose, so it never enters the pool that gets raided for more visible priorities.
Couple funding to use. The allocation scales with revenue or usage, so the load that wears the system down is the same load that pays to renew it.
Charter an owner and report the balance. A named steward controls the fund and publishes whether renewal spending is keeping pace, turning maintenance from an invisible cost into a tracked, defended line.

Tuning parameters¶

Allocation share — what fraction of revenue or use is diverted to maintenance. Higher share renews faster but raises price or cuts into growth; too low and the rule is theater.
Ring-fence rigidity — how hard it is to divert the fund elsewhere. A strict lockbox protects upkeep from raids but removes flexibility in a genuine crisis; a soft fence flexes but leaks.
Coupling basis — whether the levy scales with revenue, physical usage, or a flat charge. Usage-coupling ties wear to funding most tightly; revenue-coupling is simpler but can decouple from actual load.
Reporting cadence — how often the renewal-vs-decay balance is published. Frequent, visible reporting keeps the fund defended; rare reporting lets it quietly erode.

When it helps, and when it misleads¶

Its strength is that it makes maintenance structural rather than discretionary: by routing money automatically and coupling it to use, it defeats the chronic tendency to under-fund the unglamorous upkeep on which everything rests. It converts "we'll get to it" into a standing, sized, tracked commitment — the antidote to accumulating deferred maintenance.^[1]

Its failure modes cluster around the ring-fence and the number. The share can be set too low to actually keep pace — a token levy that looks like stewardship while decay outruns it — and a soft fence invites the fund to be raided the first time a shinier priority appears, which is exactly the behavior the rule exists to prevent. Funded-by-use also only replenishes what money can buy; it does not by itself renew tacit skill, norms, or trust. The classic misuse is running it backwards — declaring a maintenance fund to satisfy an auditor while quietly spending it on operations. The discipline that guards against this is to size the share against the real decay rate (not political comfort), report the renewal-vs-wear balance openly, and keep the fence genuinely binding.

How it implements the components¶

resource_replenishment_path — it is the explicit channel that routes operating value back into maintenance capacity, closing the loop between producing value and funding the foundations of future value.
renewal_stewardship_role — chartering a named owner for the fund keeps renewal visible, budgeted, and defended rather than diffused into general operations.
viability_metric — the reported renewal-vs-decay balance provides evidence of whether funding is sufficient to keep the system viable.

It supplies the money for maintenance but does not perform the physical replenishment of a consumed resource — that is Regenerative Resource Cycle; it funds a steward role but does not rotate the human load across people — that is Stewardship Rotation; and it does not detect early decay signals directly — that sensing lives in other mechanisms it should be paired with.

Instantiates: Autopoietic Self-Maintenance — this policy secures the resources that every other renewal loop depends on.
Sibling mechanisms: Regenerative Resource Cycle · Stewardship Rotation · Apprenticeship Pipeline · Succession System · Knowledge Base Refresh · Community Renewal Ritual · Norm Maintenance Ritual · Onboarding and Socialization · Open-Source Maintainer Renewal · Retrospective-to-Training Loop · Ecological Regeneration Practice

References¶

[1] Deferred maintenance — upkeep postponed to save money now, which accumulates as a growing, often hidden liability and tends to fail suddenly and expensively. Funded-by-use is a standing corrective: it converts maintenance from a deferrable expense into a first-claim on revenue. ↩