Donor Coupled Capacity Governance

When a recipient appears viable because a donor/source continuously sustains it across a boundary, make the subsidy explicit, test real capacity, and choose continuation, formalization, transition, or withdrawal safeguards.

Essence

When a recipient appears viable because a donor/source continuously sustains it across a boundary, make the subsidy explicit, test real capacity, and choose continuation, formalization, transition, or withdrawal safeguards.

Donor-Coupled Capacity Governance treats subsidy as a structural relation, not simply as generosity or dependency. The practical question is whether a recipient's observed capacity is truly endogenous, openly and legitimately supported, or dangerously dependent on an ungoverned donor/source.

Compression statement

Donor-Coupled Capacity Governance applies when a system, population, service, organization, or region is held above its endogenous capacity by an asymmetric resource flow from another bounded system. The intervention distinguishes genuine autonomy from donor-coupled viability, accounts for donor burden and recipient dependence, and designs support rules that either legitimize the subsidy as a durable obligation or transition the recipient toward safer capacity, diversified support, or managed downsizing.

Canonical formula: Observed recipient capacity C_obs = endogenous capacity C_endogenous + donor subsidy S - dependency friction D. Intervene when S is material, hidden, donor-stressing, or withdrawal-sensitive: expose S, bound donor load L, test C_endogenous, and select durable support, transition, diversification, or taper.

Key components

Component	Description
Donor Resource Flow Map ↗	and a
Recipient Capacity Baseline ↗	Together they show what crosses the boundary and what would remain if it did not.
Subsidy Visibility Ledger ↗	prevents the support from disappearing into performance reports, while an
Autonomy Claim Test ↗	prevents externally sustained capacity from being mislabeled as independent success.
Donor Resilience Guardrail ↗	,
Support Load Limit ↗	, and
Withdrawal Rebound Buffer ↗	keep the intervention from harming either side.
Transition or Formalization Path ↗	is the central design choice: the support may continue as an explicit obligation, taper under safeguards, diversify, become reciprocal, or become a capacity-building bridge.

Common mechanisms

A Subsidy Dependency Assessment is useful when the support relation is suspected but not quantified. A Subsidy Ledger and Source-Sink Monitoring Dashboard are useful when support continues and must be reviewed. A Taper and Handoff Plan, Capacity Milestone Agreement, and Withdrawal Rebound Drill are useful when support may change. A Donor Stress Test and Support Load Quota protect the source. A Cross-Boundary Support Agreement formalizes legitimate support rather than hiding it.

Parameter dimensions

Important parameters include support share, donor load, recipient baseline capacity, duration of support, reversibility of withdrawal, source substitutability, moral or legal obligation, recipient agency, donor resilience, and expected rebound severity. The same pattern can be financial, ecological, logistical, social, informational, or political.

Invariants to preserve

The key invariants are visible support, honest capacity claims, donor/source viability, recipient safety, legitimate obligation, and reviewability. The archetype should not presume that independence is always better than support. It should presume that hidden support creates bad decisions.

Target outcomes

A good implementation makes three states distinguishable: self-sustaining capacity, transparently subsidized capacity, and dangerously hidden dependency. Once those states are visible, the system can choose durable support, transition, capacity building, diversification, or guarded withdrawal with fewer surprises.

Tradeoffs and failure modes

The most serious failure mode is abandonment disguised as capacity building. The second is permanent hidden dependency that allows both donor and recipient risks to accumulate. Donor collapse, false autonomy certification, stigmatizing support visibility, and politically convenient austerity are also major risks. The archetype needs ethical review because some subsidies are legitimate obligations rather than problems to eliminate.

Neighbor distinctions

This is not only dependency_exposure; exposure is necessary but not sufficient. It is not symbiotic_alignment, because the support can be asymmetric. It is not satiation_aware_allocation, because marginal allocation does not decide whether recipient capacity is donor-coupled. It is not externality_internalization, because the main pattern is a sustaining inflow rather than an externalized cost. It is not ordinary capacity building unless the donor flow and withdrawal risk are part of the design.

Examples

In conservation, a sink population should not be counted as locally successful if it persists only because a source habitat continually supplies immigrants. In humanitarian aid, a clinic network can be lifesaving and still require transparent localization or formal continuation terms. In an organization, a branch or product line may look viable because central services silently absorb its real costs. In care networks, one caregiver may be the hidden donor keeping a household above its baseline capacity.

Non-examples

A one-time grant is not this archetype if no sustained dependence forms. A balanced mutual exchange is better handled as symbiotic or contractual alignment. A dependency map alone is not enough unless it leads to subsidy governance, donor load limits, support formalization, or transition decisions.

Review note

The draft intentionally keeps ecological source-sink management and aid-localization transition as variants. They may deserve later promotion if future queue items require more specialized components and mechanisms.

Common Mechanisms

• Capacity Milestone Agreement
• Cross-Boundary Support Agreement
• Donor Stress Test
• Source-Sink Monitoring Dashboard
• Subsidy Dependency Assessment
• Subsidy Ledger
• Support Load Quota
• Taper and Handoff Plan
• Withdrawal Rebound Drill

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (13)

• Accountability: Responsibility for actions.
• Adaptive Capacity: Ability to change.
• Autonomy: A unit's behavior is governed by its own internal rules or chosen reasons rather than external direction, defined by the inner-versus-outer authority asymmetry over a scoped domain.
• Boundary: Defines system limits.
• Coupling: Interdependence among subsystems.
• Cross-Boundary Subsidy: An asymmetric, sustained flow of a sustaining resource across a boundary holds a recipient above its endogenous capacity, creating donor-coupling vulnerability mistaken for autonomy.
• Dependency: Directed relation in which one element relies on another being present, prior, compatible, or supplied, with a specifiable failure mode if the condition is unmet.
• Feedback: Outputs influence inputs.
• Flow: Structured movement of energy, matter, or information.
• Observability: Infer internal state externally.
• Resilience: Absorb shocks and adapt.
• Resource Management: Allocation of finite assets.
• Threshold: Safe vs harmful levels.

Also references 16 related abstractions

• Bottleneck: The single limiting stage that caps an entire system's throughput.
• Equilibrium: Balanced state.
• Externality: Spillover effects.
• Fairness: Judging whether an allocation or procedure treats comparable parties impartially according to a defensible standard, given that multiple such standards can conflict.
• Homeostasis: Maintain internal stability.
• Latent Service Bundle: A sustaining system silently renders a multi-category bundle of benefits to diffuse, unbilled beneficiaries, and because no single category sits on a price ledger the bundle is invisible to decision-makers who consult only the invoice and so systematically under-value it.
• Logistics Overreach: An operating front advances faster than the trailing supply line that sustains it, and because the lengthening line itself consumes delivery, beyond a crossover point further advance strands what has already advanced rather than extending reach.
• Moral Hazard: Risk-taking under protection.
• Reciprocity: Mutual exchange.
• Resource Curse

▸ Show 6 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Humanitarian Aid Transition Governance · domain variant · recognized

Manage emergency or development aid so external support preserves life while avoiding hidden long-term dependency or destructive withdrawal.

• Distinct from parent: The parent applies to any donor-coupled capacity system; this variant specializes it for aid, relief, development, and public-service transition contexts.
• Use when: Aid or outside support is keeping a community, institution, or service above its locally sustainable capacity; The support may need to continue, taper, localize, or convert into durable capacity; Abrupt withdrawal would create rebound failure or legitimacy damage.
• Typical domains: humanitarian aid, development programs, public health, education support
• Common mechanisms: subsidy dependency assessment, taper and handoff plan, capacity milestone agreement

Source-Sink Habitat Support Governance · domain variant · candidate

Govern ecological source-sink flows so sink populations supported by immigration are not mistaken for self-sustaining habitats.

• Distinct from parent: The parent covers any recipient capacity held above baseline by donor flow; this variant focuses on ecological demography and landscape/resource flows.
• Use when: A population or local system persists because immigrants, nutrients, subsidies, or inputs arrive from elsewhere; Local reproduction, maintenance, or resource regeneration is insufficient without the cross-boundary flow; Conservation or management decisions depend on knowing whether the recipient area is source, sink, or externally subsidized.
• Typical domains: ecology, conservation, agroecology
• Common mechanisms: source sink monitoring dashboard, withdrawal rebound drill

Cross-Subsidized Service Autonomy Calibration · governance variant · recognized

Make cross-subsidies among units, customers, regions, or services visible so recipients are not treated as autonomous profit or capacity centers.

• Distinct from parent: The parent covers broader donor-coupled capacity; this variant emphasizes financial, service, and organizational cross-subsidy reporting.
• Use when: A region, product, service, department, or customer segment appears viable only because another boundary-crossing flow pays part of its cost; Performance reports, autonomy claims, or accountability rules ignore the subsidy; Leaders must decide whether to keep, redesign, price, or sunset the cross-subsidy.
• Typical domains: platform pricing, public utilities, shared services, regional services
• Common mechanisms: subsidy ledger, cross boundary support agreement

Donor Overextension Guardrail · risk or failure variant · recognized

Constrain sustaining support so the donor does not degrade its own resilience or create cascading failure while propping up the recipient.

• Distinct from parent: The parent balances recipient capacity, donor stress, and transition; this variant foregrounds donor-side capacity limits.
• Use when: The donor is carrying multiple recipients or a recipient whose support demand is growing; Support obligations are invisible to donor capacity planning; Failure of the donor would harm both donor and recipient.
• Typical domains: military logistics, shared services, caregiving networks, supply chains
• Common mechanisms: donor stress test, support load quota, cross boundary support agreement

Near names: Cross-Boundary Subsidy Management, Subsidy Dependence Transition Design, Source-Sink Support Governance, External Support Autonomy Calibration, Donor Dependency Governance.