Industry

NVIDIA just shipped a safety system for robots. The map changed overnight.

2 min readMati Melchior
NVIDIA just shipped a safety system for robots. The map changed overnight.

On 22 June 2026, NVIDIA announced Halos for Robotics — described as the industry's first full-stack safety system for physical AI. It pairs safety-capable compute (the IGX Thor module, which carries an independent on-chip safety processor) with a safety software stack and an accredited inspection lab. More than forty partners signed on at launch, and Agility's humanoid Digit is the first robot to adopt it.

For two years, the claim that AI-driven robots need a dedicated hardware safety layer was a minority position — the kind of thing you had to argue for from first principles. The largest company in AI just moved it to the centre of the industry. Hardware safety for physical AI is no longer a fringe research topic. It is a product category.

I'll be direct: I argued this was inevitable. In May I published The Software Safety Ceiling — the case that physical AI cannot be made safe in software alone, because the substrate a software monitor runs on is the same substrate it is supposed to be watching. Aviation, nuclear and rail each reached that conclusion decades ago and mandated hardware-isolated safety. Robotics was next. NVIDIA just agreed, in the loudest way the industry has.

What NVIDIA got right is the architecture. Halos puts an independent safety processor — its own cores, its own power, its own clock — alongside the AI compute, rather than asking the AI stack to police itself. That is precisely the hardware safety layer the software-only camp said wasn't necessary. It turns out it is.

What the announcement leaves open is the harder question. NVIDIA's safety processor lives on the same chip, comes from the same vendor, and is designed by the same team as the AI it supervises. Is on-chip isolation the same thing as independence — or is it shared fate dressed up as separation? That question now decides how much any safety layer is actually worth, and it is the subject of the next post.

The category is set. The next race is over who provides the independent, vendor-neutral version of it.

Share

Physical AI Safety Dispatch

Monthly analysis. No spam. One exclusive insight per issue.

One issue per month. Unsubscribe in one click from any email. Privacy policy.

Regulation

What five weeks of counting found

104 days separate 8 October 2026 from 20 January 2027, when Regulation (EU) 2023/1230 will apply as a cut-off with no transition period. Thirty-nine notified bodies held a current notification on 13 September 2026, against one hundred and forty-four under the Directive it replaces. No harmonised standard has yet been cited under the Regulation, the application guide is expected in the fourth quarter of 2026, no readiness figure has been published, and none of the seven certification bodies checked publishes how long the work takes. The deadline is measured to the day. Almost nothing behind it is.

Read →

Regulation

You have 127 days. Nobody publishes how long this takes.

127 days separate 15 September 2026 from 20 January 2027, when Regulation (EU) 2023/1230 will apply. Seven certification bodies were checked for a published duration benchmark and not one publishes it, so what follows is what is documented instead: the first assessor notified on 8 September 2024, roughly twenty-eight months before the Regulation applies, no harmonised standard yet cited under the Regulation, and seven trade associations on record that machinery was the only sector left out of the Omnibus IV transition period.

Read →

We use cookies

This site uses essential cookies to function and, with your consent, analytics cookies (Google Analytics) to understand how the site is used. Learn more.