Funding Firewall Rule¶
Funding rule — instantiates Capture-Resistant Institutional Design
Structures the institution's money so it doesn't depend on the actors it governs — routing fees through a buffer, capping any single source, or funding from a broad levy — so the budget can't be used as a leash.
An institution that must not offend the actors who pay its bills is already half-captured. Funding Firewall Rule removes that leash by construction: it structures the flow of money so the institution is not financially dependent on — and is not paid directly by — the specific actors whose behavior it decides. That is achieved by interposing a buffer (fees pooled and reallocated rather than paid to the regulator for its own service), by capping any single source's share, or by funding from a broad levy or independent appropriation. Its defining move is structural, not procedural: it does not disclose the money or screen the people — it re-routes the budget so that no regulated actor's payment tracks its own scrutiny, and no single actor is pivotal to whether the institution can operate. The budget simply stops being a lever the regulated class can pull.
Example¶
An accounting-oversight board inspects the audit firms that sign off on public companies. If each firm paid the board directly for its own inspection, the board would flinch from failing its largest, most lucrative customers — the dependency would sit right on the decision. The funding firewall re-plumbs the money. All firms pay a broad, formula-based levy into a pool whose size is set by an independent authority; the board draws its budget from that pool, and no firm's payment is tied to its own inspection, with no single firm contributing more than a small share of the total.
Now the board can fail its biggest inspectee and feel no direct budget consequence. The sector still funds the system in aggregate — which is fair, since it creates the need for oversight — but the link between a specific actor's money and that actor's scrutiny has been severed. The leash is gone even though the sector still pays.
How it works¶
What distinguishes the firewall is that it operates on the structure of the money flow:
- Decouple payer from decision. The regulated actor may fund the system in aggregate but never pay for its own scrutiny; the two are deliberately unlinked.
- Diversify and cap sources. No single actor or narrow group supplies enough of the budget to make its withdrawal a threat.
- Interpose an independent budget-setter. A body the regulated class cannot lean on sets the funding level, so the sector cannot retaliate by starving the institution.
- Buffer against the moment. Multi-year commitments and a reserve keep a sudden funding threat from bearing on a live decision.
Tuning parameters¶
- Buffer depth — direct fees, a pooled levy, or general appropriation. A deeper buffer means more independence but less user-pays efficiency and more exposure to political budgeting.
- Source cap — the maximum share any single actor or sector may supply. A lower cap reduces each actor's leverage but makes the institution harder to fund.
- Budget-setter independence — whether the funding level is set by the regulated sector, the institution, an independent authority, or a legislature. An independent setter resists retaliation but introduces a new dependency of its own.
- Funding horizon — annual versus locked multi-year commitments. Longer horizons blunt year-to-year budget pressure on decisions.
- Reserve buffer — the size of a contingency fund, so that a funding threat cannot force the institution's hand mid-decision.
When it helps, and when it misleads¶
Its strength is that it cuts the most material leash — money — and does so structurally, so independence does not depend on anyone's restraint in the moment; it survives turnover and bad days.
Its characteristic failure is that it can move the dependency rather than remove it: shift funding from the industry to a legislature that the industry lobbies, and capture simply relocates upstream.[1] Divorcing funding entirely from the sector can also cost the efficiency and domain knowledge that user-pays funding carries, and a firewall on paper can be quietly breached by discretionary "top-ups" that restore the very link it severed. The classic misuse is declaring funding "independent" while a single dominant payer or a captured appropriator still holds the purse. The discipline that keeps it honest is to check where the dependency moved to, cap concentration hard, lock funding multi-year, and treat any discretionary supplement as a hole in the wall.
How it implements the components¶
Funding Firewall Rule fills the financial-independence slice of the archetype:
funding_independence_buffer— the pooled, capped, or independently-appropriated structure that stops the institution depending on the regulated actor's money.institutional_independence_boundary— the firewall is the financial dimension of the institution's independence boundary, the wall that keeps the budget from being a lever.
It does not govern people crossing between the institution and the industry — that is the Revolving-Door Cooling-Off Period — nor close the informational back channel (the Ex Parte Contact Disclosure Rule), nor screen individual conflicts (Conflict-of-Interest Disclosure and Recusal).
Related¶
- Instantiates: Capture-Resistant Institutional Design — the firewall removes the budget dependency that would otherwise let the regulated class steer the institution.
- Sibling mechanisms: Revolving-Door Cooling-Off Period · Ex Parte Contact Disclosure Rule · Conflict-of-Interest Disclosure and Recusal · Privileged Access Log · Capture Risk Audit · Countervailing Stakeholder Panel
Notes¶
Independence has several dimensions, and the firewall owns only one of them: the financial. The informational dimension belongs to the Ex Parte Contact Disclosure Rule and the personnel dimension to the Revolving-Door Cooling-Off Period; the three share the same independence boundary from different sides. The non-obvious caution is that a firewall's job is only half done when the dependency is severed — one must also check where the new dependency lands, because "independent funding" that rests on a captured appropriator has merely lengthened the leash.
References¶
[1] The budget-dependence channel is a standard variant of regulatory capture in the sense of George Stigler's economic theory of regulation — the institution serving the interests of the group it is meant to regulate. A firewall closes the direct financial channel but must be checked for whether the dependency has simply reappeared one step upstream. ↩