Skip to content

Source Sink Viability Management¶

Manage asymmetric support networks by protecting sources, diagnosing sink dependency, and deciding when to sustain, restore, transform, or exit sinks.

Version: v1 · 2026-08-24 · History
Solution archetype #: 999
Problem family: Accumulation, Depletion & Degradation
Problem subfamily: Stock-Flow & Conservation Imbalance

Essence¶

Source–Sink Viability Management handles systems where some sites or units produce surplus and others persist only by receiving that surplus. The archetype asks whether support is wise, fair, sustainable, restorative, temporary, permanent, or disguising failure.

The target prime is not merely “a source and a sink.” It is asymmetric net balance across coupled sites. A source exports more than it needs to persist. A sink consumes or loses more than it produces and would decline in isolation. The design problem is to govern the relation rather than letting aggregate survival hide local nonviability.

Compression statement¶

A source-sink system persists because some sites, units, markets, habitats, teams, or reservoirs produce surplus while others consume more than they produce and would decline alone. The intervention is to map net balance roles, measure source surplus and sink dependency, protect source viability, set support rules, maintain or redesign connectivity, and choose whether each sink should be sustained, restored, converted, or exited. The archetype prevents aggregate persistence from hiding local nonviability, source depletion, or permanent dependency.

Canonical formula: net_balance(site) = local_production_or_recruitment - local_consumption_or_loss; source if net_balance > export_threshold, sink if net_balance < viability_requirement and persistence depends on imported surplus.

When This Archetype Applies¶

Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.

Diagnostic problem

A coupled system is treated as if every site or unit is locally viable, while some sinks persist only because surplus from sources compensates for their deficit, masking source depletion, sink fragility, or maladaptive dependency.

Applicability expression5 distinct conditions

Surplus-deficit unitsandSupport-dependent deficit unitsandHidden uneven viabilityandConnectivity-dependent supportandExport-depleted sources

Algebraic1∧2∧3∧4∧5

groundedpartly groundedopen

5 conditions, all required.

5Required in every casenumbered 1–5

These hold no matter which pattern applies.

1

Surplus-deficit units · grounded

Some sites, teams, habitats, accounts, markets, services, or units generate surplus while others consume, lose, or require more than they produce.

primeSource-Sink Dynamics— A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.

and — also required

2

Support-dependent deficit units · grounded

Deficit units would decline, fail, collapse, exit, or become unacceptable without incoming support.

primeSource-Sink Dynamics— A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.

and — also required

3

Hidden uneven viability · grounded

Aggregate system performance hides the fact that persistence is unevenly produced and unevenly consumed.

primeSource-Sink Dynamics— A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.

and — also required

4

Connectivity-dependent support · grounded

Connectivity matters: a sink can persist only if the surplus path from a source remains open, reliable, and not too delayed.

primeSource-Sink Dynamics— A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.

and — also required

5

Export-depleted sources · grounded

Sources can be depleted, exploited, or weakened by repeated exports.

primeSource-Sink Dynamics— A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.

Other requirements and context (2)

Why these sit outside the expression

Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

Solution feasibilitySupport flows can be protected, increased, redirected, tapered, conditioned, or withdrawn by design choices.
Supporting contextSinks may deserve support for equity, coverage, mission, option value, ecological function, or strategic future potential, but not all dependency should be permanent.

Coverage

5 of 5 conditions grounded.

Read the methodology Download the trigger-logic data

Problem Pattern¶

A source-sink system can look stable in aggregate while hiding two different dangers. First, sources may be overdrawn: their surplus is treated as free even though it depends on renewal, resilience, and local obligations. Second, sinks may be falsely treated as viable because support keeps them alive. Removing support then causes collapse, while continuing support without review may lock in dependency.

This pattern appears in ecosystems, public services, platform marketplaces, regional development, organizational portfolios, infrastructure, health systems, and supply networks. In each case, the relevant question is not only “where should resources go?” It is “which units produce surplus, which units depend on surplus, why is the dependency justified, and what would show that the relation is becoming healthier or more dangerous?”

Intervention Pattern¶

The intervention is a governance layer around source-sink roles. It classifies sites by net balance, protects sources with viability guardrails, profiles sink dependency, maps support pathways, and makes explicit decisions about sustaining, restoring, converting, tapering, or exiting sinks.

The archetype should not stigmatize sinks. A sink can be valuable, necessary, beautiful, strategically important, or morally required. The failure is not dependency itself; the failure is unmanaged dependency, hidden source depletion, unexamined support inertia, or unsafe abandonment.

Key Components¶

Component	Description
Unit of Persistence ↗	Before classifying source or sink status, define what must persist: a population, habitat, service site, market, team, account, or infrastructure node. Without a clear unit, the classification becomes rhetorical.
Source–Sink Role Map ↗	The role map classifies each unit as source, sink, neutral, role-switching, unknown, or contested. It should include confidence and time horizon, because source/sink roles can change after shocks, restoration, seasonality, or growth.
Net Balance Measurement ↗	Net balance compares local production or replenishment against local consumption or loss. A source has exportable surplus only after its own renewal and obligations are protected. A sink requires imports to remain above its viability threshold.
Source Viability Guardrail ↗	A source should not be drained simply because it currently produces surplus. Guardrails protect renewal, resilience, local obligations, and future source capacity. They prevent stewardship from becoming extraction.
Sink Dependency Profile ↗	A sink dependency profile identifies the amount, reliability, duration, pathway, and interruption risk of required support. It distinguishes rescue from recovery and permanent chosen support from accidental lock-in.
Support Rationale and Horizon ↗	Support should have a reason and a review date. The reason might be equity, coverage, ecological function, option value, mission, strategic growth, transition, safety, or legal obligation. The horizon can be permanent, conditional, staged, or time-limited, but it should be explicit.

Common Mechanisms¶

Useful mechanisms include source-sink patch maps, metapopulation models, cross-subsidy budgets, source depletion dashboards, sink dependency dashboards, support flow agreements, restoration priority matrices, connectivity corridor plans, minimum support schedules, support taper plans, rescue-effect audits, role reclassification reviews, and transfer tracers.

Mechanisms should fit the decision. Use metapopulation models when dispersal and recruitment matter. Use cross-subsidy budgets when financial support is institutional. Use rescue-effect audits when persistence might be confused with recovery. Use support taper plans when exit is possible but abrupt withdrawal would be harmful.

13 documented mechanisms across 6 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 2 mechanisms

Cross-Subsidy Budget — Makes the transfer from source to sink an explicit line item — how much surplus each source can spare after protecting itself, where it goes, and whether the resulting subsidy is fair — so support is a decision, not a leak.
Metapopulation Model — Runs a network of coupled patches forward from their per-patch birth–death and dispersal rates to forecast whether the whole persists — and which patches are true sources versus occupied-but-doomed sinks.

Assessment, Review & Assurance · 2 mechanisms

Rescue-Effect Audit — Periodically tests whether a sink's apparent health is genuine local recovery or merely a rescue effect — persistence borrowed from a source — by asking what it would do if the support were removed.
Role Reclassification Review — A standing review that watches for role-change triggers and, on a set cadence, formally re-labels any unit whose source or sink status has shifted — so the classification the whole system trusts never silently goes stale.

Decision, Gate & Allocation · 1 mechanism

Restoration Priority Matrix — Ranks dependent sinks by how recoverable they are against how much they are worth keeping, sorting each into restore, convert, sustain, or exit — so scarce surplus goes where it can actually change a unit's fate.

Monitoring, Sensing & Alerting · 3 mechanisms

Dispersal or Transfer Tracer — Tags and follows the individuals or units that actually move between patches, turning assumed support flows into a measured map of who really feeds whom and what each patch's true net balance is.
Sink Dependency Dashboard — Tracks each sink's dependency in real time — how much support it draws, how close it sits to its viability threshold, and which flows it relies on — so hidden fragility and lock-in surface before an interruption exposes them.
Source Depletion Dashboard — Continuously watches each source's health — how much exportable surplus is left, whether its viability guardrails are being breached, and how it holds up under stress — so stewardship never quietly slides into extraction.

Representation, Specification & Plan · 3 mechanisms

Connectivity or Corridor Plan — Designs and protects the actual pathways along which a source's surplus can reach a sink, and deliberately keeps more than one route open, so rescue can happen without leaving the sink hostage to a single link.
Source–Sink Patch Map — Lays out every unit as a labelled patch — source, sink, neutral, or contested — coloured by measured net balance, so the asymmetric structure of who is quietly carrying whom becomes visible at a glance.
Support Taper Plan — A staged glide-path for reducing or ending support, paced to the sink's response and bounded by a do-no-harm guardrail, so withdrawal is a controlled landing rather than a cliff.

Rule, Policy & Commitment · 2 mechanisms

Minimum Support Schedule — Sets the smallest reliable support a sink needs to stay just above its viability threshold, delivered on a fixed cadence and adjusted by rule as conditions change — sparing the source without letting the sink slip under.
Support Flow Agreement — Turns an informal support flow into an explicit compact — stating why the support exists, until when it is promised, and on what fair terms — so a subsidy is a governed decision rather than an accreted habit.

Parameter Dimensions¶

Important parameters include local production, local consumption, net balance, exportable surplus, support amount, support reliability, dependency duration, source renewal rate, sink viability threshold, connectivity reliability, transfer delay, role-switch frequency, withdrawal harm, restoration cost, and support rationale.

Invariants to Preserve¶

The main invariants are source viability, explicit sink dependency, visible support flows, monitored connectivity, fair support rationale, and safe transition rules. Aggregate viability should never be allowed to hide local depletion or collapse risk.

Target Outcomes¶

A good implementation makes source depletion visible before it becomes collapse. It prevents rescued sinks from being mistaken for self-sustaining units. It clarifies when support is justified and when restoration, conversion, taper, or exit is needed. It also helps preserve ethical support where permanent dependency is legitimate and openly chosen.

Variants¶

Ecological Source–Sink Habitat Management is the marine-science and conservation form. Cross-Subsidy Viability Design covers public services, platforms, and organizational portfolios. Rescue-Effect Stabilization focuses on cases where repeated support prevents collapse but may hide non-recovery. Sink Conversion or Exit Management covers persistent sinks that need transition decisions. Role-Switching Source–Sink Adaptation covers systems where sources and sinks change roles over time.

Neighbor Distinctions¶

Conserved Reservoir-Flux Balancing is the parent stock-flow neighbor, but it does not by itself answer source viability, sink dependency, support rationale, or exit decisions. Buffering smooths temporary mismatch. Mutual Dependency Stabilization is reciprocal. Dependency Exposure reveals hidden reliance. Commons Governance governs shared-resource use. Public Goods Provision funds shared benefits. Network Flow Optimization routes flow. Source–Sink Viability Management is the asymmetric-persistence pattern: sources export surplus, sinks persist through imports, and the system must govern the consequences.

Examples¶

A protected reef exporting larvae to degraded reefs is an ecological source-sink system. A profitable urban route subsidizing rural transit is a public-service source-sink system. A dense marketplace funding incentives for a thin region is a platform source-sink system. A profitable product line funding exploratory research is an organizational source-sink system. A central hospital supporting rural clinics is a healthcare source-sink system.

Non-Examples¶

A one-time transfer is not necessarily source-sink management. A dependency map without support decisions is Dependency Exposure. A buffer stock that smooths short-term mismatch is Buffering. A route optimization problem is Network Flow Optimization. A project ranking model is allocation unless persistent source/sink viability is the central structure.

Failure Modes¶

The major failure modes are rescue mistaken for recovery, source depletion by invisible obligation, aggregate persistence illusion, connectivity neglect, stale role classification, maladaptive subsidy lock-in, abandonment shock, and sink stigmatization. The practical test is whether the system can say what each sink needs, why it is supported, what protects the source, and what would justify changing the support relation.

Review Notes¶

This draft should be reviewed as a full archetype rather than a simple variant because the target prime includes distinct semantics: asymmetric net balance, source export, sink nonviability in isolation, and persistence through coupling. It should be cross-checked against the previous reservoir-flux draft and against the next target, turnover, because turnover may require a separate identity-preserving renewal archetype.

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

Built directly on (12)

Balance: Even distribution of elements.
Boundary: Defines system limits.
Buffering: A maintained intermediate capacity that absorbs excess and releases it during shortfall, smoothing variation and decoupling a source from a consumer whose rates do not match.
Coupling: Interdependence among subsystems.
Feedback: Outputs influence inputs.
Flow: Structured movement of energy, matter, or information.
Observability: Infer internal state externally.
Reservoir-Flux Network: Named stocks linked by conserved flows.
Resilience: Absorb shocks and adapt.
Resource Management: Allocation of finite assets.
Source-Sink Dynamics: A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation.
Turnover: Continuous replacement of components while the system's structure persists.

Also references 16 related abstractions

Adaptive Capacity: Ability to change.
Asymmetric Flux: A direction- or channel-selective boundary drives accumulation even under symmetric forcing.
Backpressure: A return signal from a downstream stage throttles upstream production to its own capacity, converting a one-way push into a two-way conversation that holds the system at the bottleneck's throughput instead of accumulating hidden queue debt.
Boundedness: Values remain within limits.
Carrying Capacity: The sustainable load envelope of a system: the maximum demand it can carry indefinitely before sustained operation begins consuming its own substrate and lowering future capacity.
Conservation Laws: Quantities remain constant.
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.
Equilibrium: Balanced state.
Externality: Spillover effects.
Homeostasis: Maintain internal stability.

▸ Show 6 more

Variants¶

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

Ecological Source–Sink Habitat Management · domain variant · recognized

Manage habitat patches so surplus-producing sources can sustain sinks without masking sink degradation or exhausting the source.

Distinct from parent: Domain-specific ecological form of the general source-sink viability pattern.
Use when: Population persistence depends on dispersal from productive patches to deficit patches; A sink would decline in isolation but receives enough immigrants, larvae, seeds, workers, or resources to persist; Managers can protect sources, restore sinks, alter connectivity, or change pressure on either side.
Typical domains: marine science, conservation biology, landscape ecology
Common mechanisms: patch viability map, metapopulation model, dispersal corridor plan, sink restoration priority matrix

Cross-Subsidy Viability Design · governance variant · recognized

Use surplus from viable units to sustain deficit units while making dependency, fairness, and source depletion explicit.

Distinct from parent: A policy and governance subtype focused on subsidy and support rather than ecological dispersal.
Use when: Profitable, high-capacity, or high-yield units support low-yield units that would not persist alone; The sink is maintained for equity, coverage, strategy, resilience, mission, or option value; The design must prevent permanent hidden dependency and source exhaustion.
Typical domains: public services, platform marketplaces, organizational management, regional planning
Common mechanisms: cross subsidy budget, service coverage subsidy, mission support transfer, dependency dashboard

Rescue-Effect Stabilization · risk or failure variant · candidate

Maintain enough incoming support to keep a sink from collapse while avoiding false belief that the sink has become self-sustaining.

Distinct from parent: Narrower case where rescue prevents collapse but dependency remains unresolved.
Use when: A sink persists because repeated imports prevent local collapse; The support flow is intermittent, delayed, or shock-sensitive; Managers must distinguish true recovery from continuous rescue.
Typical domains: ecology, healthcare operations, social services, infrastructure resilience
Common mechanisms: rescue flow audit, minimum support schedule, dependency exit review, early warning threshold

Sink Conversion or Exit Management · governance variant · recognized

Decide when to restore a sink toward self-sustaining status, convert its role, or exit support without destructive abandonment.

Distinct from parent: The parent includes ordinary maintenance of source-sink networks; this variant handles unresolved sink dependency.
Use when: A sink remains dependent beyond an acceptable support horizon; Source surplus is no longer sufficient to sustain all sinks safely; The system needs a humane, ecological, or strategic transition rather than indefinite subsidy.
Typical domains: conservation, public services, portfolio management, infrastructure planning
Common mechanisms: graduated support taper, restoration plan, managed retreat plan, service consolidation review

Role-Switching Source–Sink Adaptation · temporal variant · candidate

Monitor and adapt when sources become sinks or sinks become sources under seasonality, shocks, growth, depletion, or regime change.

Distinct from parent: Narrower temporal case where role change is expected and central.
Use when: Net production and consumption roles change over time or across regimes; A formerly reliable source can become a dependent sink after shock or overuse; Support policy must adapt without locking old roles into the map.
Typical domains: ecology, energy systems, regional economics, organizational portfolios
Common mechanisms: seasonal role map, shock reclassification review, adaptive transfer rule, moving window net balance test

Near names: Source–Sink Governance, Source–Sink Support Design, Source–Sink Network Governance, Source–Sink Metapopulation Management, Surplus-Subsidy Viability, Sink Rescue Management.

Editorial Notes¶

Problem Classification¶

Classification: Accumulation, Depletion & Degradation → Stock-Flow & Conservation Imbalance

Problem kernel: aggregate viability hides surplus flows from sources into deficit sinks

Rationale: Local surpluses flow from source units to sustain deficit sinks, so aggregate persistence hides unequal net balances, source depletion risk, and sink nonviability. Support-substrate depletion would require current activity to consume a finite regenerative base faster than it recovers; that can occur, but the necessary structural center is the unaccounted conservation and transfer balance between sources and sinks.

Boundary considered: Accumulation, Depletion & Degradation → Support-Substrate Depletion

Why this classification prevailed: Stock-flow imbalance governs transfers and net balances among sources and sinks; support-substrate depletion governs consumption of a finite regenerative base faster than recovery.

Review outcome: Adjudicated after independent review; high confidence.