Funding Conditions Register¶
Governance register — instantiates Outside-Authority Influence Channel Mapping
A standing ledger of every funding source's attached conditions — grant terms, gift restrictions, sponsorship clauses — logged with owner, sovereignty risk, and review date so money-borne strings stay governable.
Money almost never arrives clean; it arrives with expectations, and those expectations are easy to sign and easy to forget until the day they touch a decision. Funding Conditions Register is the standing ledger that refuses that amnesia for the money channel specifically. For every source of funds the decision body accepts, it records the conditions attached — grant deliverables, gift restrictions, naming rights, pre-publication review clauses, renewal contingencies — and, beside each, the sovereignty risk it creates, who owns it, and when it is next reviewed. Its one distinguishing idea is that funding conditions are a live governance object, not a one-time entry on a map: the register keeps the strings visible, owned, and re-examined across the whole life of the relationship, so a clause signed years ago is still on the screen the day it would otherwise quietly bend a choice.
Example¶
A university research center runs on three funding streams. The register logs each with its conditions. The corporate sponsor's grant carries a thirty-day pre-publication review clause. The endowed chair comes with a naming condition and a "field of study" restriction written into the gift agreement. The foundation grant renews annually, contingent on hitting "impact metrics" the foundation defines. Each row gets a risk rating — the pre-publication clause is flagged high, because it is a latent publication veto — plus an owner (the associate dean for research) and a review date.
Months later a doctoral study nears publication with findings unwelcome to the sponsor. A researcher checks the register before circulating the draft, sees the pre-publication clause and its high rating, and routes it to the firewall protocol rather than discovering the string mid-crisis. The register did not decide anything; it made sure the condition was seen while there was still time to handle it well.
How it works¶
- Log every funding source and its attached conditions, verbatim from the agreement — the explicit clauses and the documented informal expectations both.
- Rate each condition for sovereignty risk — does it reach what gets decided, published, or studied, and how reversibly?
- Assign the governance fields — an owner, a mitigation, the residual risk, and a next-review date — so each string is a tracked item, not a filed contract.
- Keep it live — new grants, renewals, and expirations update the ledger, and cumulative exposure to a single funder is totted up, not just per-grant clauses.
The distinguishing move is that it is a register, not a map: it carries owners, mitigations, and review cadence for the funding channel, so conditions stay governed over time rather than mapped once.
Tuning parameters¶
- What counts as a condition — explicit written clauses only, or documented informal expectations too. Wider is more honest but harder to substantiate.
- Risk-rating scheme — a simple flag, or a scored rubric on reach, reversibility, and dependence. Finer rating triages better but invites false precision.
- Disclosure — an internal ledger, or a publicly posted register. Publishing deters string-pulling but chills some legitimate giving.
- Review cadence — annual, per-decision, or event-triggered (a renewal, a relevant decision). Faster catches drift but costs staff time.
- Aggregation — per-grant, or totalled per funder. Per-funder totals catch the cumulative dependence that many small clean grants can hide.
When it helps, and when it misleads¶
Its strength is temporal: it keeps money-borne strings from vanishing between the signing and the decision they later touch, and it converts a contract in a drawer into a governed item with an owner and a review date. For the funding channel it is the memory the rest of the design lacks.[n1]
Its central failure mode is mistaking the written condition for the real one. The dangerous string is often unwritten — the implied "we trust you'll remember who funds this program" that no clause captures — and a register of clauses can miss it entirely while looking thorough. Logging also breeds false comfort: a documented condition can feel handled precisely because it is written down, though writing it changes nothing. And cumulative dependence on one funder across many individually-innocent grants can threaten sovereignty more than any single clause. The discipline that keeps it honest is to record informal expectations alongside formal clauses, to aggregate exposure by funder rather than only by grant, and to pair the register with a mechanism that actually acts on the high-rated rows — the ledger records, it does not restrain.
How it implements the components¶
funding_condition_map— the register is this map: every funding source and the conditions, restrictions, and contingencies riding on it.sovereignty_risk_register— for the funding channels it covers, it maintains the risk-register fields: the affected decisions, the channel owner, the mitigation, the residual risk, and the review cadence.
It records what a funder can require but does not test what refusing that funder would actually cost (leverage_and_dependency_assessment) or plan how to reduce the dependence (dependency_diversification_plan) — both belong to the Refusal-Cost Scenario Test, its nearest twin on the money-and-dependence axis, which stress-tests the strings this register merely records. It covers only the funding channel, not the relational one (relationship_and_interlock_map, the Relationship Interlock Diagram).
Related¶
- Instantiates: Outside-Authority Influence Channel Mapping — the register supplies the governed record of the funding channel the rest of the design reasons over.
- Sibling mechanisms: External Influence Channel Matrix · Relationship Interlock Diagram · Refusal-Cost Scenario Test · Conflict-of-Interest Disclosure Review · Recusal and Firewall Protocol · Influence-Response Decision Tree · Dependency Heatmap · Privileged Access Log
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Funding Conditions Register operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a standing ledger of every funding source's attached conditions — grant terms, gift restrictions, sponsorship clauses — logged with owner, sovereignty risk, and review date so money-borne strings stay governable.
Independent corroboration: The frozen evidence defines Funding Conditions Register as 'A standing ledger of every funding source's attached conditions — grant terms, gift restrictions, sponsorship clauses — logged with owner, sovereignty risk, and review date so money-borne strings stay governable', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Accounting & Auditing
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Restricted-fund accounting supplies the ledger logic for recording conditions attached to money.
Related originating lineages:
- Law & Governance — Gift restrictions and contractual grant terms legally define enforceable conditions.
- Public Administration & Policy — Public and nonprofit grant administration materially developed compliance registers and review dates.
Review resolution: Both reviewers agree that accounting_auditing is primary: Restricted-fund accounting supplies the ledger logic for recording conditions attached to money. I retain law_governance, public_administration_policy only where the reviewers identify formative lineage, not every later application. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The register looks like the already-authored Privileged Access Log (a different archetype) — both are standing ledgers — but they hold different objects: the access log records contacts and meetings over time, while this register records funding conditions and their governance status. A funder who never once takes a meeting can still hold a decisive clause; a frequent visitor may attach no strings at all. Kept together, the two answer "who has our ear" and "who has our purse" respectively.
[n1] In nonprofit and grant accounting, restricted funds are monies a donor has earmarked for a specific purpose, distinct from unrestricted funds the body may spend at its own discretion. The register generalizes that idea from how money may be spent to how a decision may be shaped — treating every condition, financial or editorial, as a restriction on sovereignty to be tracked. ↩