Funding Dependency Register¶

Register — instantiates Revenue–Accountability Coupling Design

Keeps a standing, disclosable record of every revenue stream and how much of the agent's survival rides on each — flagging the streams that let it keep operating without the people it is meant to serve.

An organization answers, in practice, to whoever it depends on to keep the lights on — and it rarely admits, even to itself, who that is. Funding Dependency Register is the standing record that makes it explicit: one entry per revenue stream, each carrying its share of total survival, its renewal basis (who has to say yes for the money to continue), and — the field that makes this an accountability instrument rather than a finance report — a bypass flag marking whether the stream depends on the served constituency or routes around them. Its distinguishing move is being a living register, kept current and disclosable, rather than a one-off audit or a live alarm: it is the diagnostic backbone that answers "who could switch off our money, and do they overlap with the people we exist to serve?" — the operational form of the fact that resource control is control.^[1]

Example¶

A university research center lists its funding streams in the register: recurring university base funding (~25%, renewed internally), three multi-year federal grants (~40%, renewed by program officers), an industry consortium (~25%, whose member companies fund studies that touch their own products), and philanthropic gifts (~10%). The bypass flags tell the story a funding pie chart hides: base funding is coupled — the university sustains it as a matter of mission — while the industry consortium, ~25% of survival, depends on parties whose interests the center's findings are not supposed to serve. Seeing that concentration named, and published in the register for faculty and the oversight board to inspect, the center treats research independence as a measurable exposure to be reduced, not a virtue to be asserted — and the register becomes the shared input an audit verifies and a drift dashboard watches.

How it works¶

What distinguishes it from ordinary financial reporting is the three fields that matter for accountability, kept current on every stream:

Dependency share, not just amount. Each stream is scored by how much of the agent's survival rides on it, so a small but irreplaceable source ranks as high risk.
Renewal basis. Who has to keep saying yes — readers, a program officer, a statute — because that is who the agent actually answers to.
Bypass flag. Whether the stream depends on the served constituency or routes around them, which is the exact field that names the accountability gap.

Tuning parameters¶

Concentration metric — how dependence is measured (share of total budget, share of discretionary budget, a concentration index). Guards against an org that looks diversified but really lives on one donor.
Bypass test — how strictly "routes around the constituency" is defined; a loose test lets influence-laden money pass as clean.
Disclosure level — internal, board-only, or a public ledger. More disclosure buys more discipline but exposes sensitive funder relationships.
Refresh cadence — how often streams are re-scored, trading maintenance effort against staleness.

When it helps, and when it misleads¶

Its strength is converting "we're independent" from an assertion into a measured, disclosable claim: a concentration jump becomes an early warning, and the bypass flags name the exact streams eroding accountability so a remedy can target them.

Its limit is that it records dependence without fixing it, and a tidy published register can breed complacency — "we disclosed it, so it's handled." It is also run backwards: curated to look diversified by splitting one dominant funder into several sub-grants, or by scoring dependence in whatever units flatter the org. The discipline is to score by ultimate source, publish the register, and pair it with an independent audit that checks the numbers rather than trusting the self-report.

How it implements the components¶

Funding Dependency Register fills the revenue-diagnostic slots of the archetype — what a standing record of the money can hold:

revenue_dependency_map — its core content: every stream and the share of survival riding on it.
bypass_channel_identifier — the bypass flag names the streams that let the agent survive without the served constituency.
public_revenue_ledger — the register is maintained as a disclosable ledger of sources, not a private spreadsheet.

It does not periodically verify its own entries — independent checking is Revenue Source Audit; and it does not watch the streams for real-time movement or fire alerts — that live monitoring is Rent-Stream Drift Dashboard.

Instantiates: Revenue–Accountability Coupling Design — it makes visible the resource channel that accountability has to be re-coupled to.
Sibling mechanisms: Budget-to-Mandate Crosswalk · Revenue Source Audit · Rent-Stream Drift Dashboard · Sponsor Influence Firewall · Sunset Reauthorization Vote · Beneficiary Feedback Gate · Constituency Board Seat · Participatory Budget Review · Clawback or Reversion Clause · Performance-Linked Renewal · Public Accountability Hearing

Notes¶

The register is a diagnostic, not a remedy — it names the dependence that other mechanisms then act on (an Alternative Revenue Path to reduce a concentration, a Sponsor Influence Firewall to neutralize an influence-laden stream). It is also the revenue-side complement of the Budget-to-Mandate Crosswalk: one shows who funds the agent, the other shows whom the agent's spending serves.

References¶

[1] Resource dependence theory (Pfeffer & Salancik) — organizations are constrained by whoever controls the resources they cannot do without. The register is a direct operationalization: it inventories exactly those dependencies so they can be governed instead of quietly governing the agent. ↩