Harness Engineering for Physical AI: Robot Middleware Is the Harness Layer
2026-06-08 • Robotics
RoboticsArtificial IntelligenceSoftware Engineering
AI summaryⓘ
The authors discuss how robot middleware, the software layer that helps different robot parts work together, needs to take on a new role as robots now use AI models that affect control, timing, and communication all at once. They suggest that middleware acts like a "harness," managing and enforcing how AI outputs are handled to keep robots working safely and reliably. The authors identify three key functions missing from current middleware—Projection, Isolation, and Transfer—that help check AI outputs and fallback safely when needed. They propose adding these functions into robot middleware, specifically in ROS 2, to better handle AI-driven robot control.
robot middlewarePhysical AIROS 2harnesslearned policiesprojectionisolationtransfercontrol pathDDS
Authors
Sanghoon Lee, Jiyeong Chae, Kyung-Joon Park
Abstract
Robot middleware faces a new role in the era of Physical AI. Learned policies, planners, and vision-language-action (VLA) models now enter deployed robots as causal participants on the control path, but the layer that integrates them with timing, scheduling, and network has not been named. Recent language-agent work names this layer the harness, the external system that mediates tools, manages state, bounds resources, and records execution. The robotics community has not yet adopted this framing, and we propose that robot middleware is that harness. A Physical AI harness differs from a software harness in where it intervenes. A software harness mediates at tool-call boundaries. A Physical AI harness must mediate at control, computing, and communication simultaneously, because a learned policy's output crosses all three: its commands shift the trajectory, its inference time shifts the schedule, and its payload shifts the bandwidth. Robot middleware is the lowest robot-stack layer with mediating abstractions over all three, so it is best positioned to compose their enforcement. It already provides most of what a harness needs but lacks the enforcement for an AI model. We name this missing enforcement as three functions: Projection gates each output at emission, Isolation bounds the model's execution and transmission slot, and Transfer falls back to a verified baseline when checks fail. Each appears today as hand-built application code in deployed robot systems, built on surfaces robot middleware already provides. Robot middleware should host them not as the best single-axis enforcer but as the layer that composes all three. We sketch this as a ROS 2 Harness Profile, a deployment artifact that carries an AI model's declared output region, inference budget, and operating regime while the middleware enforces them across ROS 2, DDS, and Zenoh.