Engineering
Wrap, don't certify: runtime monitors and verification gates for physical AI
If you can't certify the model, what can you certify? The thing around it.
Yesterday's chapter showed why a text guard isn't enough. A VLA completes the task. The guard misses the implied harm. I found no VLA that claims a SIL under IEC 61508. So the 2026 answer is a wrapper: a check between the model and the motor.
Four recent sources show the pattern.
Check the action before it runs. Pre-VLA (arXiv 2605.22446, May 2026, preprint) scores each candidate action chunk before execution. It predicts a safety confidence and an advantage score. Low-quality chunks get filtered and resampled. On the LIBERO benchmark, average closed-loop success rose from 30.79% to 37.62%. Average verification time was 183.9 ms per action chunk.
Match the monitor to the model. SafeContract (arXiv 2605.28726, May 2026, preprint) ran three policy architectures through 450 episodes. Direction reversal predicted failure in all three. Velocity violations alone did not predict it anywhere. Yet the paper notes velocity checking is the most common safety mechanism in VLA deployment code. Its conclusion: "No single monitor works universally."
Keep safety out of the model's hands. In June 2026, Oxford's Fazl Barez called for "safety layers that don't depend on the AI being right". His examples: zones around people that a robot's arms cannot enter, and a physical emergency brake.
Watch from outside the robot. NVIDIA's Halos Outside-In Safety Blueprint, announced 22 June 2026, uses external cameras and AI agents to control robot behaviour in industrial settings. It's open source and in early access. NVIDIA says its inspection lab helps partners prepare for third-party certification. That's certification-ready. It isn't certified.
Here's how the four line up:
| Layer | Example | What it checks |
|---|---|---|
| Before execution | Pre-VLA | each candidate action chunk |
| During execution | SafeContract | motor-command signals |
| Around the person | Barez | keep-out zones, a physical brake |
| Outside the robot | Outside-In Blueprint | the cell, through external cameras |
One idea runs through all four. Treat the model's output as a draft. Check it before it becomes motion.
A note on related work. I published a method with the same shape, for a different job. The Verification Gate (a working paper, not peer-reviewed) is a work method for engineers who use generative AI tools. It puts one mandatory hold point between tool output and any commitment, such as a signature. It isn't a robot runtime monitor, and it reports no results yet.
Here's the honest limit. Pre-VLA and SafeContract are preprints. Pre-VLA reports benchmark success rates. It doesn't report harm prevented. SafeContract tested three architectures on two task sets. The Outside-In Blueprint is in early access. None of the four sources claims a certified monitor. A wrapper is only as safe as the evidence behind the wrapper.
Bottom line: wrap, don't certify = move the safety claim onto a part you can test. Then test that part like any other safety function, with a safe state it can always reach.
Safety engineers: in your safety case, which part carries the rating, the model or the check around it?
Part 5 of 12 · The Survey: what keeps physical AI safe in 2026.
Sources
- arXiv — Sun et al., Pre-VLA: Preemptive Runtime Verification for Reliable Vision-Language-Action and World-Model Rollouts, 2605.22446v1, preprint (read 29 October 2026)
- arXiv — Gupta, How VLAs Fail Differently: Black-Box Action Monitoring Reveals Architecture-Specific Failure Signatures (SafeContract), 2605.28726v1, preprint (read 29 October 2026)
- Oxford Martin School — Fazl Barez, AI robots can go rogue: a researcher on how easily it happens, 15 June 2026 (read 29 October 2026)
- NVIDIA — press release, NVIDIA Announces Halos for Robotics, 22 June 2026 (read 29 October 2026)
- Physical AI Safety — Melchior, The Verification Gate, method page with its DOI and version history (read 29 October 2026)
Cite this
APA
Melchior, M. (2026, November 18). Wrap, don't certify: runtime monitors and verification gates for physical AI. Physical AI Safety. https://physical-ai-safety.com/blog/wrap-dont-certify-runtime-monitors-for-physical-ai
BibTeX
@misc{melchior2026wrap,
author = {Melchior, Mati},
title = {{Wrap, don't certify: runtime monitors and verification gates for physical AI}},
howpublished = {Physical AI Safety},
year = {2026},
month = nov,
date = {2026-11-18},
url = {https://physical-ai-safety.com/blog/wrap-dont-certify-runtime-monitors-for-physical-ai}
}- Published