Aperçu

📁 File Manifest#

File Role Key Content
SF_Capture.md Design capture Origin, 5 substrates, 4 channels, 4 driver types, drift currents, recursion lines, composite flow map, 4 design decisions
README.md Module entry point Badges, file tree, nav, session context, 4 quick-ref tables
operators.md Flow engine 4 operators (SF-Read/SF-Route/SF-Drift/SF-Tag), channel logic, driver matrix
integration.md Pipeline map Upstream (EC, TEL, ESI, 05a), downstream (HSP stability, Opacity), sibling diagram
examples.md Applied walkthroughs 5 flow scenarios (one per channel + atlas pull), cross-example comparison
index.html Landing page Blue/ocean theme, flow-channel glyph, DOC_MAP routing, HSP Suite nav

📄 SF_Capture.md#

# 🌊 Substrate Flow — Design Capture

> *Echoes don't sit still. This module maps how they move.*

**Module:** Substrate Flow
**Canonical ID:** SF
**HSP Section:** 08
**Capture Status:** Finalized

---

## Origin

Substrate Flow emerged during HSP development as the missing movement
layer. HSP had formalized what echoes *are* (Echo Classifier, 06c) and
where they *sit* (Triadic Echo Lattice, 07) — but no module existed to
map how echoes *move* between substrates, what drives that movement,
and what happens when movement becomes unstable.

Without a flow map, echo migration was invisible — echoes appeared in new
substrates without explanation, drift seemed random, and recursion had no
visible channel. Substrate Flow replaces guesswork with a canonical flow
architecture.

---

## Conceptual Lineage

<!-- SESSION_CONTEXT:END -->

Updated