Subsidy Ledger¶
Document — instantiates Donor-Coupled Capacity Governance
Maintains a visible record of support flows, costs, beneficiaries, duration, and governance terms.
A Subsidy Ledger is the standing, authoritative record of what actually crosses the boundary: each support flow, what it costs the donor, who receives it, how long it has run, and under what terms. Its single job is to keep the subsidy from disappearing into aggregate performance reports. It is descriptive, not prospective and not normative — it does not say what the recipient must earn, nor what the parties owe each other; it says what is happening, entry by entry, so the support can never again be mistaken for endogenous strength or quietly forgotten. Where the flow branches — one donor feeding several sinks, or a support that passes through an intermediary before reaching the true beneficiary — the ledger traces it to source and destination so the real subsidy geography is visible rather than netted away.
Example¶
A consumer-electronics company runs two product lines under one P&L: a mature, high-margin line of chargers and a young, loss-making line of smart-home devices. On the quarterly deck the division looks healthy, and the smart-home team is praised for "approaching profitability." In truth the charger line is silently absorbing shared costs — the same sales force, the same warehouse, the same support center — that the smart-home line consumes far out of proportion to its revenue. The finance team opens a Subsidy Ledger.
Each entry names a flow and its cost: shared field-sales time, 22% consumed by smart-home vs. 6% of revenue; returns-handling, 3.1x the per-unit rate of chargers; a warehouse footprint the smart-home SKUs would have to rent at $40k/month standalone. The ledger records each flow's donor (the charger line), its recipient (smart-home), how long it has run (nine quarters), and any governance terms (none — which is itself recorded as a finding). Because some costs route through corporate shared services before landing, the ledger includes a source-sink trace showing that a "corporate overhead" allocation is in fact charger-line margin reaching smart-home by a two-hop path. The result is a single artifact that makes the cross-subsidy — roughly $2.4M a year on illustrative figures — impossible to un-see, which is the precondition for anyone deciding whether it is a wise strategic investment or a hidden drag.
How it works¶
The distinguishing discipline is completeness and traceability of the record, not judgment about it:
- One entry per flow, at its true cost. Each support stream is logged at what it costs the donor (including opportunity cost and shared-resource consumption), not at its invoice or its zero sticker price.
- Attribute source and sink explicitly. Every entry names who gives and who receives, so subsidies routed through intermediaries or netted into overhead are pulled back into daylight.
- Trace multi-hop and branching flows. Where support passes through a pool before reaching a beneficiary, the ledger follows it end to end so the pool cannot launder the subsidy's origin.
- Record duration and terms as data. How long a flow has run and whether it carries any agreed terms are fields, so "indefinite and ungoverned" shows up as a visible state, not an absence.
Tuning parameters¶
- Cost basis — cash outlay only vs. fully-loaded (including opportunity and shared-resource cost). Fully-loaded is truer to the archetype's "real cost" invariant but is harder to compute and more contestable.
- Trace depth — how many hops the ledger follows a flow through intermediaries. Deeper tracing exposes laundered subsidies but multiplies effort and allocation arguments.
- Entry granularity — one line per program vs. per transaction. Fine granularity supports audit; coarse granularity keeps the ledger readable.
- Disclosure scope — who may see the ledger. Wide visibility deters hidden subsidy but can stigmatize legitimate recipients — a tension the archetype flags directly.
When it helps, and when it misleads¶
Its strength is that it destroys the specific illusion the archetype exists to fight: it makes subsidized performance and endogenous performance separable, on the record, at a glance. It is the substrate every other mechanism reads from — you cannot stress-test a donor, cap a load, or plan a taper against a flow you have not first written down.
Its failure mode is that a ledger's honesty is exactly as good as its cost allocations, and allocating shared costs is notoriously arbitrary — the choice of allocation base can make the same cross-subsidy look large or trivial.[n1] A ledger can thus be technically complete and still mislead, either by under-loading shared costs (flattering the recipient) or over-loading them (manufacturing a case for withdrawal). The classic misuse is weaponized visibility: surfacing a legitimate, just subsidy in stigmatizing detail to justify cutting it. The guarding discipline is to fix and disclose the allocation methodology before the numbers are read, and to record terms and legitimacy alongside costs so the ledger informs a governance choice rather than pre-loading austerity.
How it implements the components¶
subsidy_visibility_ledger— the document is this ledger: the standing, entry-by-entry record of support flows, costs, beneficiaries, duration, and terms.donor_resource_flow_map— each entry attributes a flow to its donor source, assembling the map of what the donor actually sends across the boundary.source_sink_flow_trace— it follows branching and multi-hop flows end to end so subsidies routed through pools are traced to true source and sink.
It does not set the recipient's readiness gates — local_capacity_milestone and autonomy_claim_test belong to Capacity Milestone Agreement — nor the relationship's mutual terms — reciprocity_or_obligation_rule and donor_exit_exception_rule belong to Cross-Boundary Support Agreement, its nearest document-twins. This ledger records what flows; those decide what must be earned and what is owed.
Related¶
- Instantiates: Donor-Coupled Capacity Governance — supplies the factual record every other mechanism reads from.
- Sibling mechanisms: Capacity Milestone Agreement · Cross-Boundary Support Agreement · Source-Sink Monitoring Dashboard · Subsidy Dependency Assessment
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Subsidy Ledger operates as a persistent ledger, log, register, or case record that preserves history and traceability because it maintains a visible record of support flows, costs, beneficiaries, duration, and governance terms.
Independent corroboration: The frozen evidence defines Subsidy Ledger as 'Maintains a visible record of support flows, costs, beneficiaries, duration, and governance terms', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Accounting & Auditing
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: A ledger of flows, beneficiaries, costs, and terms descends from accounting records and audit trails.
Related originating lineages:
- Economics & Finance — Subsidy incidence concerns who receives and bears transfers.
- Public Administration & Policy — Public grant governance requires transparent program records.
Review resolution: The blind reviewers agree that accounting_auditing is the primary origin and differ only on domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
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 Subsidy Ledger is a record, not a monitor: it is the point-in-time book of what has flowed and on what terms. Its sibling Source-Sink Monitoring Dashboard reads the same underlying flows but renders them as a live, trending, threshold-alerting view — the difference between the accounting book and the instrument panel.
[n1] Cross-subsidization — using surplus from one activity to cover another's shortfall. In cost accounting the apparent size of a cross-subsidy depends heavily on the chosen allocation base, which is why a ledger's methodology must be fixed and disclosed before its numbers are trusted. ↩