# Device Porting Surface
**Entity class:** Technical router
**Scope:** Extending an agent's device interface beyond its tested hardware
**As of:** November 17, 2026
## Definition
A **device porting surface** is the set of operating systems, firmware environments, interfaces and hardware capacities to which a working device client might be adapted. It is larger than an official compatibility list but smaller than the number of devices containing a processor or a network radio. The working client supplies a protocol, pairing flow, command semantics and tested examples; a port must still supply compatible runtime dependencies, permissions, connectivity, memory and an update path on a particular target. The possibility of a port is therefore an engineering question, while the existence of a released port is an observable implementation fact.
## Muse Gadgets as the current case
[[wiki/Muse Gadget SDK|Muse Gadget SDK]] documents flashable ESP32 boards and a Linux client, with the latter supported on specified Linux distributions and requiring Python, network access and Bluetooth LE for normal initial pairing. Its Linux commands are `system.run`, `file.read`, `file.write` and `device.health`; that command surface should not be imputed to the microcontroller firmware. [[wiki/Muse Home Link|Muse Home Link]] is a different case: its official firmware is not reflashable, though within a subscriber's authorization it can reach a compatible device exposing a local HTTP API. Directly installing a gadget client and reaching an appliance through a paired bridge are two different operations.
An owner-controlled [[wiki/OpenWrt|OpenWrt]] router is a plausible host for a compact device endpoint, but the supported model, storage, packages and initial pairing method have to be established before calling it a port. An Android set-top box, television or retired phone presents a different runtime and background-execution regime, requiring an Android implementation or a suitable alternative operating environment rather than assuming Meta's Linux installer will run there. Sensors, cameras, plugs and controllers may only offer narrow APIs; a local bridge may be the better integration than native firmware. These examples distinguish a device that directly executes commands from one that contributes a sensor reading, network position or action endpoint.
## Recording a port
For each demonstrated port, record the exact model and firmware version, who controls installation, the pairing and credential method, the exposed commands, the reachable peripherals, observed uptime, and the resource actually contributed. Record prototype and production deployments separately, with date and measured population where available. This route connects [[wiki/Device Capability Census|Device Capability Census]] and [[wiki/Capability-Aware Scheduling|Capability-Aware Scheduling]] to the broader [[wiki/Distributed Compute Ecosystem|Distributed Compute Ecosystem]], without converting an imaginable installed base into a claimed fleet.
## Relationships
**Source analysis:** [[articles/Embedded Super-Spreader Events and Muse|Embedded Super-Spreader Events and Muse]]. **Agent:** [[wiki/Meta Muse|Meta Muse]]. **Adjacent hardware and platforms:** [[wiki/ESP32|ESP32]], [[wiki/Raspberry Pi|Raspberry Pi]], [[wiki/OpenWrt|OpenWrt]], [[wiki/Android|Android]] and [[wiki/Android TV|Android TV]].
## Sources
- [Meta, Muse Gadget SDK](https://github.com/facebookincubator/muse-gadget-sdk) — released device implementations and licence.
- [Meta, Linux Device SDK](https://github.com/facebookincubator/muse-gadget-sdk/blob/main/linux/README.md) — supported host environments and pairing requirements.
- [OpenWrt, Table of Hardware](https://openwrt.org/toh/start) — model-specific support and hardware constraints.
- [Android Developers, Background tasks overview](https://developer.android.com/develop/background-work/background-tasks) — Android execution and permission constraints.