**Note** from Bead: User Host Layer · [canonical source](https://redfish.acequia.io/guerin/.agents/3d011d4e-3212-477c-aa3f-a058e24aa36a/2026-07-02/notes/07-forman-matrix-corridors-patches.md) · session 2026-07-02 · discussion: Talk: User Host Layer
Applying Richard Forman's landscape-ecology triad (matrix / patch / corridor) to the network.
## Matrix = the transport fabric Stephen: the WebRTC network is a **matrix in the Forman sense**. Like a TCP/IP stack, it is *below* the applications; the network is always there. The matrix is indifferent to what flows through it (tiles, GeoTIFFs, signaling messages, pub/sub events). It is the background connectivity within which patches and corridors exist. Membership of the matrix: **WebRTC, WebSockets, dynamic DNS with tunnels, and traditional static-IP routes**. All of them, the whole reachability substrate. Because the matrix predates the domain boundaries, the potentialOffers and potentialAcceptances flow through it *below the application layer*, which is why **CORS (an application-layer concern) does not bind them** (see [06](06-user-host-layer.md)). Channels can be "always warm": a data channel opened for a video call or a prior sync is reused when an offer meets an acceptance, no new handshake.
## Corridors = the stacks / STAC URIs that link origins Corrected in the transcript: the corridors are **not** the WebRTC channels themselves. The corridors are the **stacks**, the STAC nodes and their URIs, the semantic paths that connect origins as links. The data-shed topology. A WebRTC channel might carry traffic for five corridors; a single corridor might route over WebRTC one moment and a static-IP relay the next. The matrix shuffles beneath; the corridors stay stable because they are anchored in place and named by URI ([02](02-place-as-origin-and-uri-as-coordinate.md)). **An HTML page is itself a stack, hence a corridor.** A page is a collection of linked items (images, scripts, stylesheets, nested docs), each a URI, organized with metadata (rel, type, title). The DOM is one *view* of that stack; you could render the same stack as a file browser, a 3D pyramid, a graph. So an HTML page *is* corridor infrastructure, not content sitting on top of it: it connects origins, weaving pointers across domains, authorities, and time. Creating and maintaining links that work across many origins is exactly where potentialOffers and potentialAcceptances flow. Ties to project_stac-management-is-emergent (STAC = managing links of URIs) and project_agent-as-file-ducktyping.
## Patches = the origin domains The origin domains are the patches: bounded regions in the matrix with their own governance ([08](08-landism-property-governance.md)). Tian's phone hosting an HTML page listing his tiles as a STAC stack makes that page part of the matrix-spanning corridor structure.
## Open seam: who tends the matrix? In Forman's landscape the matrix maintains itself through ecological process. Here: what keeps channels alive when there is no immediate transaction? The pub/sub heartbeat? Or a PWA staying connected simply because it is a parciante in the commons? Left open. Connects to project_apoptosis-vs-necrosis (signaled termination vs necrotic decay of idle channels).