Physical Device Readiness

This is a Hermes-native physical-device-readiness workflow skill.

Why This Exists

physical-device-readiness exists because a robot, heater, or relay acts on the physical world, where a wrong command can hurt someone or damage property: it fixes the safety envelope, sensor and camera gates, dry runs, operator approval, and emergency stop before any trial, and turns the commands the agent must never run into a proposed deny list the user applies.

Do Not Use When

• The device is reached through a provider or connector the user has not adopted yet; use omh-external-connector-readiness.
• The tool that would control the device is missing; use omh-toolbelt-readiness.
• The user asks to run the command, move the hardware, or start the print now; use omh-terminal or omh-apps, which need observed operator approval before any execution claim.

Examples

Good example: