Source–Sink Network Mapping¶
Diagnostic mapping method — instantiates Sanctuary-Aware Source Control
Maps the target as a network of sources and sinks so the low-contestation node that keeps reseeding the rest can be found and named — not just the biggest visible infestation.
Before you can control a recurring population, you have to know which part of it is the engine and which part is merely the symptom. Source–Sink Network Mapping models the target as a directed network of nodes and classifies each by its net reproductive flux: sources produce a surplus that disperses outward and sustains other nodes, while sinks would decline on their own and only persist because they keep being reseeded. Its defining move is to rank nodes by who reseeds whom rather than by abundance — because the node that looks like the problem (a dense, obvious sink) is often the one being fed by a sparse, inconvenient source somewhere upstream. The output is a map with the low-contestation regeneration node flagged, so the campaign can aim at the factory instead of repeatedly mopping the floor.
Example¶
A reservoir system is choking on an invasive floating weed — water hyacinth — and every season the crews clear the main channel, only to watch it fill back in. Source–Sink Network Mapping is the step that asks where is it coming from? The system is divided into nodes: the open main channel, a marina, several sheltered coves, and a shallow upstream backwater behind a causeway. Abundance says the main channel is the disaster. But tracing dispersal — flow direction, fragment drift, and where regrowth appears first after a clearance — tells a different story: the backwater is a low-flow, hard-to-reach node that quietly exports fragments downstream every high-water event. It is sparse compared to the channel, yet it is the source; the channel is a sink.
The map that comes out of this isn't a heat-map of density but a flux diagram: arrows from the backwater and one cove into the channel and marina, with the backwater circled as the regeneration node and tagged "hard to reach — upstream of a protected wetland." That single reclassification changes the whole campaign. Clearing the channel again is now visibly treating a sink; the durable move is to reach the backwater — which is exactly the node the next diagnostic has to figure out how to get to.
How it works¶
- Node the system. Partition the target's range into candidate nodes at a resolution fine enough to separate a source from the sinks it feeds.
- Estimate net flux, not standing stock. For each node, characterize whether it is a net exporter or importer of the target, using dispersal direction, timing of reappearance after suppression, genetic assignment, or mark–recapture — whatever evidence is affordable and direct enough to trust.
- Draw the edges. Connect nodes by who-reseeds-whom, keeping the connections strong enough to matter and honest about which are measured versus inferred.
- Flag the regeneration node(s). Name the low-contestation source that persists and exports, and mark its reachability as an open question for the reach diagnostic to answer.
Tuning parameters¶
- Node granularity — patch-level versus region-level partitioning. Finer resolution separates a small source from the sinks it feeds but multiplies survey effort and noise.
- Flux-estimation method — how you infer direction of reseeding (hydrology and timing, genetic assignment, tagging). Direct methods resolve true sources; cheap proxies risk mistaking abundance for source status.
- Connectivity threshold — how strong a flow counts as an edge. Set it too low and the map is clutter; too high and a slow-but-decisive reseeding path disappears.
- Temporal window — a single snapshot versus multi-season. Sources and sinks can swap roles after a flood, drought, or season change; too short a window freezes a transient picture.
- Confidence tagging — how sharply confirmed source status is distinguished from inferred. Under-tagging lets a guess harden into a target.
When it helps, and when it misleads¶
Its strength is that it converts "the target is everywhere" into "these one or two nodes are the engine," which is the difference between managing a steady state and ending it. It is the diagnostic that stops a campaign from pouring its whole budget into the biggest visible sink while the real source keeps reseeding it — the archetype's central failure.
Its failure mode is that a network map is only as good as its flux data, and the seductive shortcut is to read abundance as source status — to circle the densest node because it is easiest to see and to reach.[1] Dynamic role-swaps (a sink that becomes a source after a disturbance) slip past a too-short window, and edges that are merely inferred can be drawn with false confidence. The classic misuse is to assemble the map after the operational plan, to rationalize where the crews already wanted to work. The discipline that guards against this is to validate at least the decisive edges with one direct method, carry the measured-versus-inferred tags all the way through, and re-map after any major disturbance rather than trusting last season's arrows.
How it implements the components¶
Source–Sink Network Mapping realizes the modeling-and-diagnosis side of the archetype — the components that describe where the target lives and how it moves, before anyone acts:
source_sink_reseeding_model— its primary output: the directed model of which nodes export the target and which merely receive it.regeneration_point— the mapping locates and flags the low-contestation node that keeps reproducing and exporting.adversary_or_hazard_population_model— it characterizes the target's abundance and vital rates per node that feed the flux estimate.propagation_map— it charts the dispersal pathways along which the target spreads from source to sink.
It does not judge whether those sources can be reached or lawfully acted on — that is the [Sanctuary Reachability Audit] — nor does it watch for recurrence (the [Sentinel Surveillance Dashboard]) or schedule and carry out the intervention (the Synchronized Campaign Calendar and Source Reduction Program).
Related¶
- Instantiates: Sanctuary-Aware Source Control — this method supplies the source–sink model the whole campaign is aimed by.
- Sibling mechanisms: Sanctuary Reachability Audit · Rebound and Reseeding Stress Test · Sentinel Surveillance Dashboard · Synchronized Campaign Calendar · Source Reduction Program · Containment Barrier · Below-Replacement Confirmation Test · Coordinated Access Protocol · Cross-Boundary After-Action Review · Protected-Zone Exception Review
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Source–Sink Network Mapping operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it maps the target as a network of sources and sinks so the low-contestation node that keeps reseeding the rest can be found and named — not just the biggest visible infestation.
Independent corroboration: The frozen evidence defines Source–Sink Network Mapping as 'Maps the target as a network of sources and sinks so the low-contestation node that keeps reseeding the rest can be found and named — not just the biggest visible infestation', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Representation, Specification & Plan — Source–Sink Network Mapping includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Biology & Ecology
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Classifying habitat patches as sources and sinks to locate reseeding nodes is canonical population and landscape ecology.
Related originating lineages:
- Earth Sciences — Spatial analysis identifies connected low-contestation patches.
- Environmental Science & Climate Studies — Management of invasive species and hazards applies source-sink maps.
- Systems Thinking & Cybernetics — Directed flow networks reveal leverage nodes maintaining recurrence.
Review resolution: The blind reviewers agree that biology_ecology is the primary origin and differ only on alternate origin 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 multi_domain records portability separately from historical provenance; encyclopedia_synthesis=false preserves the affirmative synthesis judgment where either reviewer identified one.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
"Source" here is a property of net flux, not of size — the smallest node on the map can be the one that has to be reached. Keeping that distinction explicit is what stops the campaign from re-aiming at whichever node is currently largest. The map names the source; it deliberately says nothing about whether the controller can get to it, which is why it hands that question straight to the Sanctuary Reachability Audit.
References¶
[1] In population ecology a source produces a net surplus of individuals that disperse to and prop up sinks, which would otherwise decline; suppressing sinks while a source survives yields recovery rather than elimination. The source–sink framework was formalized by H. Ronald Pulliam (1988), and it is the reason abundance is a poor guide to which node actually drives recurrence. registry ↩