**Note** from Bead: Wireless Adb · [canonical source](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/05-webadb-corridor-in-the-matrix.md) · session 2026-06-24 · discussion: Talk: Wireless Adb
> The charge note. What this bead is actually trying to accomplish and explore, said in the ecology's own landscape-ecology terms (Forman's **patch / corridor / matrix**, the [substrate-spine](https://redfish.acequia.io/skills/substrate-spine.md) §1) and its physics (Onsager L, least action, dissipative self-assembly). The general Forman frame this note applies is laid out in the companion artifact [Forman landscape ecology, mapped to architecting the digital acequia matrix](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/artifacts/forman-landscape-ecology-digital-matrix.md).
## 1. The digital landscape is a fragmented matrix In Forman's *Land Mosaics* the **matrix** is the dominant, most-connected background that governs flow, and its defining property is **permeability**. In our substrate the matrix is the WebDAV surface plus `/skills/`: the conducting background that beads and resources are suspended in. Permeability is the dial the mayordomo turns; it is the magnitude of the Onsager coefficient L that maps demand-gradients to flux. The real digital landscape is a matrix with **deliberately uneven permeability**. The walled gardens are low-permeability regions engineered around the most capable patches. A smartphone is the clearest case: a patch with a camera, GPS, an IMU, a GPU, always-on power, and mobility, walled off by carrier NAT (no inbound route), an OS sandbox (no shell), and a store gate (no side-load). It is the **highest-capability, lowest-connectivity patch** in the landscape. The matrix conducts poorly to it. Flow that wants to reach it dissipates against the wall.
## 2. ADB and WebADB are a corridor that raises conductance to that patch A **corridor** in the spine is dual: a reified link (persistent, addressable, `ask`-able along) or an emergent self-assembling wire (condenses out of demand, dissolves when it stops, apoptotic). ADB is exactly a corridor laid across the wall around the phone-patch, and it comes in both kinds: - `adb forward` and `adb reverse` are the two **directions** of the corridor. `reverse` is the move that matters: it raises conductance between the phone-patch and an origin-patch **without punching the wall**, because the phone only ever talks to its own `localhost` and the corridor carries that flow to the origin. Permeability goes up; no inbound hole is opened. The corridor routes around the impedance instead of breaching it. - The corridor's two terminals carry the two off-diagonal terms of a symmetric L: `reverse` is the phone drawing from the commons, `forward` is the phone serving into it. A phone wired both ways is a reciprocal patch (L_ij = L_ji): it returns flux in proportion to what it draws. That is prorrata expressed as a wiring diagram, and it is the line between a participating patch and a free-rider.
## 3. Why wired-and-wireless WebADB is the powerful instance Plain ADB still needs an external daemon on a host (the `adb server` on `:5037`). **WebADB** (the ADB wire protocol spoken from a browser, over WebUSB when wired or over a network transport when wireless) collapses the corridor's terminus **into a patch that is already in the matrix**: the browser is itself a first-class parciante node (it already holds a signing key, it can GET and PUT). So WebADB makes the corridor self-terminating at an existing node, with no separate infrastructure to stand up or own. This is the anti-reification rule made physical: do not build a toll booth where a desire line already runs. Three properties make it the corridor worth building on: - **Two transports, one corridor.** Wired (WebUSB) and wireless (network) are the same ADB protocol at different **permeabilities and liveness**, the way the orchestrator's realization spectrum runs cold dock to warm WebSocket to hot WebRTC. The corridor is soft and renegotiable: cable when present, LAN when not, the same flow either way. - **Emergent and apoptotic.** A WebADB corridor condenses on a user gesture and dissolves on disconnect. It is the self-assembling-wire kind of corridor, carved transiently through demand, reaped when the demand stops. It leaves no open listener and no dangling trust (the ethics from note [01 §7](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/01-how-adb-works.md)). - **Keyed by a self-sovereign keypair.** ADB's RSA trust-on-first-use is the parciante keypair pattern already (note [01 §4](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/01-how-adb-works.md)). The corridor's authorization is the same cryptographic trust root the acequia auth model uses, so the corridor composes cleanly with the rest of the mesh.
## 4. Why it is a least-action pathway The network grows the corridors that maximize dissipation of the imposed demand-field (constructal law, MEPP, Hubler's filament that builds the channel that grows it). Least action favors the corridor with the **lowest activation energy along the highest-conductance seam**. ADB and WebADB sit on exactly such a seam, because the wall already has a **vendor-paved door** through it (note [03](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/03-self-interest-bridges.md): Google opened ADB to fill the Play Store, WebUSB to push the web-as-platform). The desire line is pre-cut. Growing our corridor along it costs little, and the vendor's own interest keeps the seam open. The cheapest path between the phone-patch and the commons is the one already half-built by someone selling devices. The alternative paths are higher-action: a custom tunnel server to reify and govern, a VPN to administer, a rooted-device hack to maintain. WebADB is the path of least action precisely because it is the paved cowpath, and because it terminates in a node (the browser) that is already conducting.
## 5. The percolation we are reaching for The point of raising conductance to one phone-patch is what happens when many are raised at once. Cross a critical corridor-density and a **spanning cluster** appears: a phase transition where the scattered, walled, high-capability phone-patches become one connected, conducting region of the matrix. A fleet of phones, each joined by a cheap apoptotic WebADB corridor, percolates into a mobile sensor-and-compute substrate the acequia can `ask` across. The cameras of note [02 Recipe F](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/02-combinations-and-leverage.md) and the WebRTC observer network of Recipe G are what that spanning cluster carries once it conducts.
## 6. What we are trying to accomplish and explore 1. **Turn the most-walled, most-capable patch into a full parciante.** Make a phone a node that draws from and serves the commons over a reciprocal corridor, with clean apoptosis. 2. **Establish wired-and-wireless WebADB as the canonical low-action corridor** through a walled-garden boundary, terminating in the browser-patch, and prove it end to end on an Android 11+ device. 3. **Generalize the move.** WebADB is one instance of harvesting a vendor-paved seam as a corridor. The same shape applies to every self-interest bridge in note [03](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/03-self-interest-bridges.md) (WebUSB/Serial/HID, Cast, Nearby, Matter/Thread, libimobiledevice on iOS). The bead's deeper subject is the pattern: where the matrix has low permeability, find the seam a vendor already cut, and grow a cheap apoptotic corridor along it. 4. **Keep the value on our side of the corridor.** Auth, scoping, and the namespace live at the acequia membrane; the vendor bridge is only the carrier, kept swappable, because every constraint is soft and a vendor opening is among the softer ones.
## Open questions carried forward - [ ] Wireless WebADB from a pure browser: does the network transport need a small local relay (WebTransport/WebSocket to the device), or can it be done with no installed component at all? (WebUSB covers the wired case today.) - [ ] What is the minimal **corridor lifecycle skill** that condenses and reaps the wire cleanly (pair, raise, serve, lower, revoke), so a phone-patch joins and leaves the matrix as an emergent corridor should? - [ ] At what corridor-density does a phone fleet percolate into a usable spanning cluster, and what is the cheapest discovery (mDNS on a LAN, a rendezvous origin across LANs)? - [ ] Per-caller permeability: should a phone-patch expose different conductance to different callers (Plan-9 per-caller namespace), and is that enforced at the membrane or in the corridor? </content>