Reservoir Mapping Review¶
Diagnostic mapping method — instantiates Bioaccumulation Prevention
Maps where a system's retained load enters, settles, concentrates, and eventually surfaces — turning a diffuse buildup into a named set of reservoirs, sources, and interactions you can act on.
You cannot stop a buildup you have not located. Reservoir Mapping Review is the diagnostic that draws the map: for a given kind of retained load, it traces the whole topology — the sources that feed it, the reservoirs where it settles and concentrates, the pathways along which it leaks or remobilizes, and the vulnerable points where it finally surfaces as delayed harm. Its defining move is that it is reservoir-centered rather than event-centered: instead of counting inputs as they flow past, it asks where those inputs come to rest and pool. That single shift is what separates it from every downstream sibling — the map is the thing that tells a source-reduction program which tap to close, a dashboard which stock to watch, and a cleanup campaign where to dig.
Example¶
A regional water authority suspects PFAS "forever chemicals" are accumulating somewhere in its watershed, but its monitoring only reports what flows past the intake each week — a stream of transient readings that never adds up to a picture. A Reservoir Mapping Review reframes the question from "how much is passing through?" to "where is it coming to rest?" The team walks the system and names the parts: upstream sources (a legacy plating works, firefighting-foam runoff from an airfield, treated sludge spread on farmland), the reservoirs where the compounds actually persist (river sediment, the fatty tissue of fish, private wells in one clay-lined valley), and the interactions ordinary tracking misses — sediment that immobilizes the load for years, then remobilizes it downstream after a flood.
The output is not a number but a labeled map: sources on the left, reservoirs in the middle sized by how much they hold and how slowly they clear, arrows for the leak-and-remobilize pathways, and a flag on the fish tissue where the load biomagnifies up the food chain toward people. That map is what turns "we have a PFAS problem somewhere" into "these three sources feed these two reservoirs, and the fish are where it reaches us" — the starting point every other control needs.
How it works¶
What distinguishes it from generic process-mapping is the reservoir lens:
- Trace to rest, not to exit. Follow each input to where it settles, not where it leaves the frame; a reservoir is anywhere load lingers longer than the system assumes.
- Size stores by persistence, not throughput. Rank reservoirs by how much they hold and how slowly they clear, so a small, slow-clearing sink can outrank a large, fast-flushing one.
- Draw the interactions. Mark where stores mask, immobilize, or remobilize one another — the combinations that make a buildup dangerous even when each source looks minor alone.
- Name the surfacing points. Identify where the stored load finally becomes visible as delayed harm, which is rarely where it entered.
Tuning parameters¶
- Scope boundary — how wide to draw the system edge. Wider catches upstream sources and downstream sinks the obvious view misses, but a boundary drawn too wide dilutes the review into an atlas nobody acts on.
- Resolution — whether reservoirs are named coarsely ("the sediment") or finely ("the sediment behind the weir"). Finer resolution locates intervention precisely but multiplies the mapping effort.
- Evidence standard — how much a mapped reservoir must be confirmed by measurement versus inferred from how the system behaves. Leaning on inference is fast and surfaces suspects; demanding confirmation is slower but avoids chasing phantom stores.
- Refresh trigger — a one-time map, or a living document re-drawn whenever a new source appears or a reservoir remobilizes.
When it helps, and when it misleads¶
Its strength is that it makes a hidden, distributed stock into a named object a whole organization can point at — and it exposes the reservoir no single team owned because everyone was watching flows. It is the diagnosis the rest of the archetype is only as good as.
Its central failure mode is a map mistaken for the territory: a confident diagram lends false certainty to reservoirs that were inferred rather than measured, and quietly omits the stores nobody thought to look for — the map's blind spots become the system's. It is also the step most often run backwards, drawn after a cleanup to rationalize where the team already chose to dig rather than to find where the load actually is. The discipline that guards against both is to carry each reservoir's evidence status and uncertainty on the map itself, and to treat "we haven't looked here" as a marked region rather than empty space. A useful anchor is the source–pathway–receptor linkage from contaminated-land risk assessment: a reservoir only matters when a complete path connects a source to something that can be harmed, which keeps the map focused on live linkages rather than cataloguing every store for its own sake.[n1]
How it implements the components¶
Reservoir Mapping Review fills the diagnostic, locate-the-stock components — the map, not the response:
accumulation_reservoir— its central output: the named, sized set of stores where load is retained.inflow_source_inventory— the source-tracing step enumerates the channels that feed each reservoir.interaction_map— it documents where stores mask, immobilize, or remobilize one another rather than reasoning as if inputs were additive.
It does not set limits, clear, or contain: the inflow_limit and source_isolation_boundary belong to Source Reduction Program, the clearance_path to Clearance Pathway Enhancement, and the ongoing stored_load_signal to Stored Load Dashboard. Mapping tells them where to point.
Related¶
- Instantiates: Bioaccumulation Prevention — Reservoir Mapping Review supplies the reservoir-and-source map every other control depends on.
- Sibling mechanisms: Stored Load Dashboard · Hidden Load Audit Sampling · Source Reduction Program · Clearance Pathway Enhancement · Containment Barrier · Quarantine or Isolation Protocol · Remediation Sweep · Technical Debt Burndown · Pollutant Load Reduction Plan · Fatigue or Stress Clearance Cycle
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Reservoir Mapping Review operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it maps where a system's retained load enters, settles, concentrates, and eventually surfaces — turning a diffuse buildup into a named set of reservoirs, sources, and interactions you can act on.
Independent corroboration: The frozen evidence defines Reservoir Mapping Review as 'Maps where a system's retained load enters, settles, concentrates, and eventually surfaces — turning a diffuse buildup into a named set of reservoirs, sources, and interactions you can act on', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Representation, Specification & Plan — Reservoir Mapping Review 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: Systems Thinking & Cybernetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: System dynamics maps sources, stocks, inflows, outflows, accumulation, and delays; environmental reservoirs provide a major substantive application rather than the sole origin.
Related originating lineages:
- Biology & Ecology — biology_ecology contributes population diversity, recovery, and persistence under selection pressure to the mechanism’s formative or independently convergent form; that contribution does not displace the primary systems_cybernetics lineage.
- Environmental Science & Climate Studies — environmental_climate contributes resource monitoring, restoration, and sustainability practice to the mechanism’s formative or independently convergent form; that contribution does not displace the primary systems_cybernetics lineage.
Review resolution: The blind reviewers disagreed on primary lineage; authoritative research supports systems_cybernetics over the competing primary. System dynamics maps sources, stocks, inflows, outflows, accumulation, and delays; environmental reservoirs provide a major substantive application rather than the sole origin. The cited MIT OpenCourseWare: Stocks, Flows, and Accumulation provides direct evidence for that defining form. Alternates are retained only where they contributed an independent formative tradition, while domain_reach=multi_domain records later transfer separately from historical origin.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
Reservoir Mapping Review is qualitative topology, not measurement: it says where the stores are, not how much is in them right now. Pairing it with a sampling assessment (which quantifies a suspected reservoir) and a dashboard (which watches the confirmed ones over time) is what turns a static map into a live control — the map scopes what is worth measuring, so sampling is not spent blindly.
[n1] The source–pathway–receptor (or "pollutant linkage") model, standard in contaminated-land risk assessment, holds that a hazard is only a risk when a source, a pathway, and a vulnerable receptor are all present and connected. Used here to keep a reservoir map focused on complete, live linkages rather than an exhaustive inventory of stores. ↩