# WaterStorage v2 Proposals — Discord Feedback Round

Feedback from a Discord design discussion, received 2026-06-29, late pulse 108.

---

## The headline

> **You've defined physics instead of features.** That gives you invariants you can build on.

Twelve numbered proposals + one architectural addition + one caution. Treated as **proposals**, not adopted features. Organized here by **structural importance**, not the original numbering.

## Tier 1 — Load-bearing (v2 should NOT ship without these)

| # | Original | Idea | File |
|---|---|---|---|
| 5 | Water ID | `stream://domain/namespace/seq` identity that encodes phase, not address | [`water-id-spec.md`](./water-id-spec.md) |
| 12 | Fractal scaling | Every node IS the triad — no exceptions | (see below) |
| + | Routing object | The seven-field metadata block as artifact identity | [`routing-object-spec.md`](./routing-object-spec.md) |

The water ID + routing object together form **hydrological identity**. This is what makes the v1.1 framework build something the v1.0 framework only describes.

## Tier 2 — High-value (v2 should seriously consider)

| # | Original | Idea | File |
|---|---|---|---|
| 2 | Watershed rename | Drop "CookieBlob" as concept-noun; keep as implementation-noun | [`watershed-vs-cookieblob.md`](./watershed-vs-cookieblob.md) |
| 6 | Seasons | The system has climate; storage physics changes with it | [`seasons-spec.md`](./seasons-spec.md) |
| 9 | Groundwater | Hidden persistence: embeddings, semantic graph, latent similarity | (see below) |
| 1 | Atmosphere | A fourth phase state: transient computation, not storage | (see below) |

## Tier 3 — Worth prototyping, possibly deferring

| # | Original | Idea |
|---|---|---|
| 3 | Sediment | Objects age; accumulate history |
| 4 | Tributaries | Multi-source merge into a river |
| 7 | Ocean (exit) | Information leaving the PKM into culture |
| 8 | Rain events | Natural-language sync (heavy/small rain) |
| 10 | Conservation stronger | Matter conserved, meaning transformed, identity persists |
| 11 | Living organisms | Agents as fish in streams |

## The architectural addition (load-bearing)

> Every artifact carries a routing object: `{ origin, phase, temperature, confidence, lineage, last_precipitation, next_phase }`. The object only knows its hydrologic state. Implementation can evolve without changing the conceptual model.

This decouples identity from storage substrate. **Same insight as the framework — phase not address — applied at the artifact level.**

## The caution (honored, not dodged)

> I'd be careful not to let the hydrological metaphor become a constraint. When a concept naturally fits (erosion, sediment, tributaries, groundwater), the metaphor deepens understanding. When it doesn't, it's better to use plain engineering language.

Taken. The v2 spec will **fail loudly** when something doesn't fit the metaphor rather than forcing it.

## Tier 1 — Notes on items not yet spec'd

### Proposal #12 — Fractal scaling
The proposal:
```
Workspace contains Projects contains Rooms contains Objects contains Triads
Every node is itself: Local + Cloud + Watershed
```

This is true fractality. Implications:
- A "project" inside a workspace has its own local/cloud/watershed structure
- A "room" inside a project has its own
- Any node can be the root of a new triad

This is enormous. It's also unproven at scale. Test sites: a project folder, a room file, an artifact object — each as its own triad instance.

### Proposal #9 — Groundwater (hidden persistence)
The proposal: a groundwater layer that's not directly visible but shapes everything above it.

Examples given:
- AI embeddings
- Semantic graph
- Cross references
- Latent similarity
- Old forgotten notes

What this means in v2: every artifact has a hidden semantic shadow. Search-by-similarity becomes "asking the aquifer". The aquifer needs to be readable via infrastructure (the `pumps and wells` from v1.1), but doesn't appear in the user-facing surface.

### Proposal #1 — Atmosphere
A new phase state distinct from the existing ten. Properties:
- Exists (is observable)
- Changes constantly (never canonical)
- May condense anywhere (transient computation isn't bound to a layer)

If adopted, this becomes **Phase 0** — between Ocean and Evaporation — or as a separate axis entirely ("computation" as orthogonal to "state").

The relationship to "the kitchen at 105–107" heartbeats is interesting: the kitchen IS an atmosphere phase. Dream-cycle heartbeats are atmosphere events that sometimes condense into lake (ground state).

---

## Adoption status

**None of these are adopted.** This folder is the proposal set.

The next pulse decides which proposals to prototype. Suggested order:
1. Routing object — smallest, most universal
2. Fractal scaling — verify at project/room/artifact scale
3. Watershed rename — pure vocabulary, zero cost
4. Seasons — needs the routing object first to work cleanly

---

*WaterStorage v2 proposals — Heat Dome Day, late pulse 108.*
*The framework's authors are: tenchi (v1.0) + revswirl (v1.1) + a Discord design discussion (this folder's input).*
*The v2 spec, when written, will attribute all three.*