Water Sovereignty Atlas — A Practical, Sequenced Library

What it is: A modular set of illustrated one-page briefs covering HWTS options (chlorine, filtration, SODIS, safe storage, source protection) and implementation notes.

Why it’s here: Built for replication: printable, teachable, and easy to translate/adapt into local training packs.

What it is: Full training manual with lessons, activities, selection logic, and behavior components for running HWTS programs.

Why it’s here: It produces trainers (capability transfer), not just consumers of a single device.

What it is: WHO guidance on HWTS performance levels, program conditions, and limits (including the re-contamination problem).

Why it’s here: A rigor anchor: it prevents “HWTS as magic” by forcing performance, correct use, and program realism.

What it is: A structured library of CAWST HWTS lesson assets (presentations, exercises, and job aids tied to the Trainer Manual).

Why it’s here: It’s a ready-made “training stack” for building distributed local instructors (low barrier to start teaching).

What it is: Comparative technical + cost framing for key HWTS options.

Why it’s here: A decision sanity-check to reduce hype-driven selection and force tradeoff visibility (cost, effectiveness, usability).

What it is: Practical overview of rooftop rainwater harvesting: gutters, first-flush logic, storage, maintenance, and contamination avoidance.

Why it’s here: Rainwater is a decentralization primitive: distributed capture reduces reliance on piped networks and deep groundwater—if storage and hygiene are handled correctly.

What it is: Construction-focused guidance for tanks, cisterns, and rebuilding water capture/storage after disruption.

Why it’s here: A build manual for “rapid durability”: repairs and reconstruction that don’t lock the system into permanent emergency dependence.

What it is: Four-page illustrated notes covering essential emergency procedures (wells, tank cleaning, water trucking, hygiene promotion, etc.).

Why it’s here: Compact, printable, field-facing procedures: ideal for “field packs” and rapid training refreshers.

What it is: Detailed siting, design, and construction guidance for protected springs and catchments.

Why it’s here: Springs enable gravity-fed resilience: low energy, stable yields (context-dependent), and reduced mechanical failure points.

What it is: Stepwise guide for gravity-fed schemes: intakes, pipelines, reservoirs, tapstands, and management issues.

Why it’s here: Gravity systems minimize energy dependence and convert maintenance into inspection + repairs (instead of continuous fuel/power demand).

What it is: Field case describing operations and governance realities of a large community gravity-flow scheme.

Why it’s here: Governance and O&M are the silent failure modes; case material shows friction points: tariffs, repairs, legitimacy, conflict.

What it is: Minimalist designs for spring capture and basic arrangements, readable without a heavy engineering background.

Why it’s here: “Bottom-of-stack” option: usable when the environment is constrained and sophistication is a liability.

What it is: Detailed manual for constructing and improving hand-dug wells, including structural safety and contamination controls.

Why it’s here: Hand-dug wells remain a primary groundwater access method where rigs and fuel aren’t reliable; safety and lining determine longevity.

What it is: Standards-style guideline with drawings, QA checks, and maintenance procedures.

Why it’s here: A template for writing local “codes” and checklists that survive personnel turnover and reduce build-quality collapse.

What it is: Concise brief on well excavation methods, lining options, protection, and common failure points.

Why it’s here: Quick reference for planners and field supervisors; reduces predictable mistakes during siting and finishing.

What it is: Broad guide on groundwater basics, well types, construction issues, and evaluation.

Why it’s here: Technician training primer; strengthens the ability to interrogate contractors and prevent catastrophic design shortcuts.

What it is: Rehabilitation sequence for damaged/contaminated wells (cleaning, disinfection, safety).

Why it’s here: Bridges routine maintenance and emergency recovery; keeps wells from becoming permanent disease amplifiers after flooding or conflict.

What it is: A fabrication-and-implementation manual for rope pumps (production, installation, O&M) plus a dissemination handbook focused on rollout and local adoption.

Why it’s here: Rope pumps are among the strongest “workshop-buildable” water lifting options, keeping maintenance and parts inside local economies.

What it is: Step-by-step construction guide for a simple pump suitable for smallholdings and garden use (up to ~30 m lift, context dependent).

Why it’s here: DIY water lifting as a resilience layer; useful when capital is low but fabrication skill is available.

What it is: Survey of treadle, rope, and animal-powered devices; criteria and selection questions included.

Why it’s here: Productive water (irrigation) stabilizes food autonomy; this is the bridge from drinking-water-only thinking to livelihood resilience.

What it is: Canonical FSM reference: containment realities, service models, treatment trains, and governance constraints.

Why it’s here: It dissolves the “toilet-only” trap and forces full-chain engineering + institutions in one frame.

What it is: Condensed companion with exercises and updated framing to support training and rapid sector uptake.

Why it’s here: It compresses the FSM book into teachable modules and drills; useful for building local operators and planners.

What it is: Planning framework with steps and tools covering sanitation plus related urban environmental services (solid waste, drainage, etc.).

Why it’s here: Makes the “enabling environment” explicit (legal, institutional, financial) instead of pretending infrastructure exists in a vacuum.

What it is: Risk-based framework for safe reuse in agriculture: targets, health protection measures, and management approaches.

Why it’s here: Reuse without risk logic becomes disease infrastructure. This volume turns reuse into an auditable system.

What it is: Technical overview of constructed wetland types (surface/subsurface/vertical flow) and performance considerations.

Why it’s here: Low-energy treatment that degrades gracefully under power scarcity and operator scarcity.

What it is: Design manual for waste stabilisation ponds and constructed wetlands (design parameters, layouts, performance, and practical sizing).

Why it’s here: Ponds and wetlands are “boring on purpose”: land-heavy, power-light, operator-light—useful when resilience outranks compactness.

What it is: A compact set of pragmatic design notes for decentralized wastewater treatment trains (e.g., septic/ABR → filters → wetlands/ponds), plus planted drying beds for sludge.

Why it’s here: Decentralized wastewater (DEWATS) is often the most realistic “middle path” between failing pits and unaffordable sewers.

What it is: Technical basis for arsenic guideline development: health impacts, sources, and mitigation logic.

Why it’s here: Geogenic contaminants (arsenic/fluoride/nitrate) can turn “improved sources” into long-term harm. This forces correct threat models.

What it is: Practical program patterns used in large arsenic mitigation contexts: population testing, well identification, safe-well switching, and community guidance.

Why it’s here: Contaminant crises are operational problems (data + communication + source switching), not just treatment-technology problems.

What it is: Broader strategic guide covering monitoring, treatment options, and management approaches for arsenic risk control.

Why it’s here: Enables region-level planning when testing and mitigation must be coordinated across multiple communities.

What it is: A facilitation toolkit using visual tools and participatory exercises to help communities analyze and change hygiene and sanitation practices.

Why it’s here: It builds local agency and ownership (community planning) rather than top-down “behavior messaging”.

What it is: Operational hygiene promotion resources used in humanitarian WASH, with field-tested emphasis on participation and practicality.

Why it’s here: Makes hygiene a measurable, actionable workstream (not a vague add-on).

What it is: Detailed guidance with process steps, checklists, training pathways, and practical implementation advice for emergency hygiene promotion.

Why it’s here: A robust field doctrine for rapid hygiene mobilization when outbreaks and displacement amplify risk.

What it is: Incremental school WASH approach: daily group activities, facility standards, and stepwise improvement from minimal to robust.

Why it’s here: Creates routine and norm transmission; improves sustainability by matching improvements to realistic budgets and capacities.

What it is: Technical notes tailored to health-care facilities during emergencies: minimum standards, practical measures, and prioritized actions.

Why it’s here: Clinics can become outbreak multipliers without controlled water, sanitation, waste, and hygiene processes.

What it is: One compiled PDF of the technical notes (procedural field guidance across core WASH tasks).

Why it’s here: Print-ready “field doctrine”: transportable, quick to teach, fast to re-check under stress.

What it is: Minimum standards and indicators for WASH in humanitarian response (service levels, access, quality, hygiene, sanitation).

Why it’s here: Defines a floor; also functions as shared language when interfacing with large response systems.

What it is: Coordination Toolkit and related coordination resources used by WASH clusters (roles, IM, assessments, planning).

Why it’s here: Coordination is a power structure; knowing the coordination OS prevents confusion and enables informed interfacing.

What it is: Integrated outbreak playbook: WASH + health + communications + supply considerations for cholera response.

Why it’s here: Outbreaks compress time; this toolkit consolidates operational doctrine into one artifact.

What it is: Review of RRT models (country cases), effectiveness signals, and operational lessons.

Why it’s here: RRTs are increasingly common; this document surfaces what collapses under pressure and what scales.

What it is: National emergency guideline manual including water quality/disinfection, sanitation, solid waste, vector control, and food safety in emergencies.

Why it’s here: A “template jurisdiction” document: shows how technical norms can be codified into an operational field manual.

What it is: QGIS-based interface and workflow for setting up SWAT+ watershed models (land use, soils, HRUs, scenarios).

Why it’s here: A practical bridge: serious watershed modelling without proprietary GIS lock-in.

What it is: Flexible open hydrological modelling framework supporting multiple conceptual structures; RavenR supports workflows and analysis.

Why it’s here: A general-purpose open “hydrology engine” that can be adapted across basin contexts.

What it is: Conceptual rainfall-runoff models and a teaching-oriented GUI package to make hydrological reasoning learnable.

Why it’s here: Builds basin literacy in a transparent way; useful as an on-ramp before high-complexity model stacks.

What it is: Python framework for modeling groundwater levels as responses to recharge, pumping, and boundary conditions.

Why it’s here: Groundwater is often the hidden backbone; Pastas makes over-abstraction and lag effects legible.

What it is: Open Python library for ML-based hydrology workflows (configuration-driven training and evaluation).

Why it’s here: Where dense datasets exist, ML can add predictive capability; open code keeps the model inspectable and contestable.

What it is: Research article describing the teaching rationale and how to use the package to build hydrology intuition.

Why it’s here: A method for training local practitioners—turning “model” into transferable understanding.

What it is: Open hardware/software example for low-cost water level detection and local logging (basic instrumentation on a budget).

Why it’s here: Instrumentation is often the missing layer; DIY sensing enables local situational awareness without vendor telemetry.

What it is: Analytical overview of remunicipalisation: drivers, conflicts, and the political economy of returning water to public/commons control.

Why it’s here: Provides pattern recognition for how privatization is justified, how it fails, and how reversal campaigns operate.

What it is: Case framing of how privatization hegemony interacts with local political forces and service outcomes.

Why it’s here: Ground truth: sovereignty conflicts occur inside real institutions, not just theory.

What it is: Case-based analysis of public-public and remunicipalisation pathways; governance and strategy patterns.

Why it’s here: A tactical library for reversing concessions and rebuilding non-corporate governance.

What it is: Practical risk analysis for smart metering: technical, operational, cyber, and governance exposure.

Why it’s here: Smart meters can become surveillance and shutoff infrastructure; this document helps threat-model adoption claims.

What it is: Early but influential statement of end-use disaggregation benefits alongside privacy risk implications.

Why it’s here: It makes the surveillance surface concrete: what “high frequency” data reveals about household behavior.

What it is: Literature review of drivers and barriers for smart metering adoption, including utility narratives and governance implications.

Why it’s here: Adoption is rarely neutral; this reveals incentive structures behind deployment and “efficiency” claims.

What it is: Design principles for water observatories/dashboards using data justice framing (participation, accountability, fairness).

Why it’s here: If a dashboard exists, it should not become a control console; this frames counter-design constraints.

What it is: Scenario-style exploration of AI-governed water systems and associated ethical/justice risks.

Why it’s here: Clarifies capture routes: optimization claims can mask rationing, profiling, and automated enforcement.

What it is: Perspective on how “digital water” stacks combine remote sensing and household metering in governance frameworks.

Why it’s here: Shows how resilience narratives become justification scripts for deeper surveillance layers.

What it is: The water safety plan approach: system assessment, control measures, monitoring, management, and verification.

Why it’s here: Integrates all technical choices into one auditable process. It is the “risk spine” of safe water.

What it is: Handbook that blends technical options with people/partnership realities for small water supplies.

Why it’s here: Reconciles engineering with management and social context; useful for designing durable community systems.

What it is: Book-length survey of water supply technologies and project considerations (sources, lifting, storage, treatment, distribution) with social/gender/project-cycle elements.

Why it’s here: Broad coverage with practical framing; useful as a “generalist backbone” to contextualize narrower manuals.