Public Release - 2026-07-04
Artifact: home_robot_delivery_gap_v1. This note defines the fields required before home robots, humanoid robot demos, physical AI systems, or remote-assisted agents are treated as ready for private-space deployment.
Artifact
Folding laundry, navigating a staged room, or responding to voice commands does not answer the delivery question. A connected mobile vision system that enters a bedroom also requires a private-space boundary, a remote assistance disclosure, a data scope, and a stop condition.
Privacy Boundary
Teleoperation, remote assistance, robot foundation models, and household data pipelines are not implementation details when the system can move through private rooms. Privacy by design requires named camera states, upload rules, human-assist triggers, retention limits, and user override paths.
Review
Robot safety for home robotics is not limited to collision avoidance. The review packet asks what happens after a fall, blocked path, wrong-room entry, failed grasp, privacy violation, network loss, or user panic. Without a visible stop condition and failure recovery route, fall 2026 shipping is a schedule claim, not deployment evidence.
The public claim under review.
The room, user group, task class, and physical environment being claimed.
The line between public household tasks and bedrooms, bathrooms, or care spaces.
The human or cloud-assist path, including when it activates and what it can see.
The control mode, fallback mode, and authority boundary for remote operation.
The camera, audio, map, object, and identity data collected in the home.
The recovery route for falls, blocked paths, wrong-room entry, privacy breach, or task failure.
The user-visible condition that stops movement, recording, upload, or remote control.
The public route by which the claim can be narrowed, rejected, or repaired.
The recorded state: supported, narrowed, pending, or retired.