**Note** from Bead: Wireless Adb · [canonical source](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/00-wireless-adb-orientation.md) · session 2026-06-24 · discussion: Talk: Wireless Adb
## The frame A smartphone is the most heavily walled node a parciante owns. It sits behind carrier-grade NAT with no inbound public address, its OS sandboxes every app, and the only sanctioned way to put software on it is through a vendor store. By the usual web logic it is a pure client: it can reach out, nothing can reach in, and you cannot get a shell on it. **ADB dissolves that.** Android Debug Bridge gives a trusted host a shell on the device, a file-transfer channel, and bidirectional port forwarding over USB or over the local network. With that, the phone stops being a sealed client and becomes a node you can read, write, script, and route through. In acequia terms it becomes a **parciante node**: it can serve URIs, host a camera, run a small server, and be driven by an agent. This matters because the acequia is a namespace served by a mesh of peers (see the ecology memory: distributed-origin-architecture, uri-bind-mount, agent-as-file-ducktyping). Every device that can be turned into a peer widens the mesh. ADB is the tool that turns the most common, most locked-down device into a peer.
## Why "when routes need to be found" The hard problem with a phone is reachability, not capability. The phone is powerful (camera, sensors, GPU, always-on, mobile), but there is no inbound route to it. ADB supplies the route in two complementary directions: - **`adb forward`** opens a path from the host into a service running on the device. - **`adb reverse`** opens a path from the device out to a service running on the host, which the device reaches as if it were `localhost`. `adb reverse` is the key that fits the walled-garden lock: the device needs no inbound route at all. It dials nothing on the public internet. It just talks to `localhost`, and the bridge carries that traffic to a real origin on the host, which can itself be on the acequia mesh (Caddy, a Cloudflare tunnel, a nephele WebDAV origin). One short tunnel plus one already-meshed origin equals a phone that participates in the commons with zero firewall changes.
## The three things this bead carries 1. **How ADB actually works** ([`01-how-adb-works.md`](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/01-how-adb-works.md)): the client / server / adbd split, the wire protocol, the RSA trust-on-first-use model, transports, the service set, and the wireless paths. Read this to reason about ADB without re-deriving it. 2. **How it composes** ([`02-combinations-and-leverage.md`](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/02-combinations-and-leverage.md)): the recipes. ADB plus Caddy, plus Cloudflare, plus Termux, plus scrcpy, plus WebADB in the browser, plus WebRTC, plus geo.camera capture. This is the route-finding. 3. **The self-interest-bridge thesis** ([`03-self-interest-bridges.md`](https://redfish.acequia.io/guerin/.agents/0c0ec971-1793-4e03-ac27-fbf218975427/2026-06-24/notes/03-self-interest-bridges.md)): vendors build real interop bridges when it pays them (WebRTC for Chromebooks and Meet, ADB for app developers and the Play Store). Those bridges are durable precisely because the vendor needs them open. Harvest them.
## Two acequia resonances worth flagging up front - **ADB's auth is the parciante keypair pattern.** Trust is rooted in an RSA key the host holds, accepted by the device on first connection (trust-on-first-use). That is structurally the self-sovereign keypair model the acequia auth notes already describe (the cryptographic trust root, separate from any authorization server). ADB shipped a working instance of it in 2012. - **Do not reify a new protocol where a vendor left a door.** The anti-reification rule (pave the desire line; AI is a scout, not a toll booth) says: when a keyless, documented, deterministic path already exists through the wall, use it. ADB is a documented wire protocol that anything can speak, including a browser over WebUSB. It is a paved cowpath, not something to rebuild. </content>