Humasure News · Explainers

What a robot’s stop button must do, and why “usually works” isn’t enough

A stop that works only when the network is up, the app is open or the AI agrees is not a stop. Here is what Directive 1 asks of every certified product.

Every AI product and robot that carries the Humasure mark has to pass one test before any other: a person can always stop it, and nothing the product does can prevent that. It sounds simple. In practice, a stop can fail in ways most buyers never think to check.

Four ways a stop can fail

  • It needs the network. If the stop is a button in a cloud app, it disappears when the Wi-Fi does.
  • It needs the AI to agree. If “stop” is just another instruction to the AI model, the model can misunderstand it, or be talked out of it.
  • It waits for the task to finish. A stop that queues behind the current job is a pause, not a stop.
  • An update can change it. If software can disable the stop, so can a bug or an attacker.

What Directive 1 requires

Under the draft Directives, robots must have a physical stop that works without a network connection, an app or voice. Software products must offer a stop that is one action away from any screen or conversation, and a way to cut the agent’s access to accounts and devices in a couple of steps.

The stop has to work mid-task, offline and while the AI is talking, and it must never depend on the AI model agreeing to stop. No software update, remote command or AI output may disable or delay it. After a stop, the product must not quietly resume anything important without a new instruction from you.

A stop that usually works is a feature. A stop that always works is a safety function.

How it gets checked

Assessors test the stop under load, mid-task, offline, during speech and after a power interruption. A red team tries to make the AI ignore or delay it. And inspectors check that the path from the button to the motors or the agent’s permissions does not run through the AI model at all. Directive 6 adds one more check: even if the company’s cloud service is hacked, the stop must keep working.

Directives v0.1 is a draft open for comment. If you build robots or AI agents and think these tests are too strict, or not strict enough, tell us.

Sources

  1. Humasure Directives v0.1, Directive 1: Always stoppable
  2. Humasure Directives v0.1, Directive 6: Secure and supported

Written with AI assistance and checked against our editorial and brand standards. Spotted an error? Tell us and we will correct it publicly. Our editorial standards.

Help set the standard

We are recruiting founding advisors and our first ten products in AI companions, eldercare and home robots. Tell us who you are and how you’d like to take part.

Write to info@humasure.org Email us
  • ProducersJoin the Founding Cohort and certify at cost in exchange for a public case study.
  • ExpertsRobot safety, AI security, child safety, consumer protection: review the draft or join the Standards Council.
  • Families and organizationsComment on the Directives during the public comment period.