# WaterStorage Integration

**How WaterStorage fits into the Anthrocybernetics course**

---

## What WaterStorage Is

**WaterStorage** is a **universal hydrological information framework** — a 9-phase-state model for understanding how information flows through any system.

**Core Claim:** Information behaves like water. It's never "stored" in a location — it's always in motion between states.

---

## Why This Matters for Anthrocybernetics

The Five-Field framework teaches **domains** (Phase/Field/Arc/Form/Lattice). WaterStorage teaches **phase states** — how information moves *through* those domains.

Together, they form a complete picture:
- **Five Fields** = What the organs are
- **WaterStorage** = How the blood flows

---

## The Nine Phase States

| Phase State | Water Analogy | Information Equivalent |
|-------------|---------------|------------------------|
| **Ocean** | Raw signal intake | Log streams, sensor feeds, unfiltered input |
| **Evaporation** | Uplink, phase change | Abstraction, pattern extraction, encoding |
| **Clouds** | Field-state distribution | Distributed knowledge, shared context, culture |
| **Precipitation** | Field-sync landing | On-demand retrieval, context trigger, decision |
| **Soil Surface** | First-contact processing | Triage, immediate processing, attention allocation |
| **Creeks/Rivers** | Structured flow | Formal reports, queries, structured retrieval |
| **Lakes/Reservoirs** | Domain storage | Databases, knowledge bases, indexed repositories |
| **Groundwater** | Deep memory | Institutional memory, hidden assumptions, legacy patterns |
| **Return** | Feedback loop closure | Organizational learning, outcome integration |

---

## Mapping to the Five Fields

Each WaterStorage phase maps to a Five-Field domain:

| WaterStorage | Five-Field | Example |
|--------------|------------|---------|
| Ocean | Phase input | Raw data hitting the organization |
| Evaporation | Phase processing | Body lifting signal into coherence |
| Clouds | Field | Ambient distributed knowledge (culture, intuition) |
| Precipitation | Arc | Decision moment, aesthetic spark landing |
| Creeks/Rivers | Thalamus (Lattice) | Structured communication flow |
| Lakes/Reservoirs | Form | Domain-organized storage (knowledge base) |
| Groundwater | Deep Form | Institutional memory, unwritten rules |
| Return | Feedback loop | Learning loop closure |

---

## Conservation Law

> **Information, like water, is neither created nor destroyed.**

This is a philosophical and architectural claim:
1. No permanent deletion — old records sink to groundwater
2. No permanent loss — "lost" data is in an inaccessible state
3. No creation ex nihilo — new information is always transformation
4. Cycle closure is coherence — systems that don't close loops are leaky

---

## How It Integrates With the Course

### In the Practitioner Workbook

**§3 — Field Measurement Protocol**

The WaterStorage 9-phase-states is explicitly used as the measurement framework:

1. **Ocean** → Raw inputs (rainfall, water table, demand)
2. **Evaporation** → Abstraction ("what is the field" mental model)
3. **Clouds** → Distributed knowledge (founding crew's shared context)
4. **Precipitation** → Decisions precipitated from field
5. **Soil Surface** → First-contact processing (cell's intake)
6. **Creeks/Rivers** → Structured reports (cell council meeting minutes)
7. **Lakes/Reservoirs** → Domain storage (cell-registry)
8. **Groundwater** → Institutional memory (founding stories, unwritten rules)
9. **Return** → Feedback loop closure (retrospective → next season)

---

## Ground Rules for System Designers

(From the WaterStorage framework itself)

1. **Don't fight the phase states** — work with the cycle
2. **The terrain shapes where rain lands** — design for your topography
3. **Creeks before lakes** — not everything needs a reservoir
4. **Polluted groundwater takes decades to recover** — prevention is critical
5. **Evaporation requires energy** — the uplink phase is not free
6. **Precipitation is trigger-based, not schedule-based** — build conditions, not calendars

---

## What WaterStorage Is NOT

- **WaterStorage is NOT** a database architecture (it's a conceptual framework)
- **WaterStorage is NOT** specific to Anthrocybernetics (it's universal)
- **WaterStorage is NOT** the same as the Five Fields (it's the flow layer)

---

## Draft Status

WaterStorage is **complete and stable** — v1.0, standalone, system-independent. It's ready to be used as a teaching framework.

---

*Reference: https://zo.pub/revswirl/water-storage*