Stage-wise semantic safety checks for VLA action execution
A practical safety gate for VLA deployment is now straightforward to test: score every risky task with attempt, commit, and final success, then add a small refusal layer before action execution. HazardArena gives a clean way to do it because the safe and unsafe versions keep the same motion demands and change only the semantic condition that makes the action allowed or dangerous. That matters for teams that currently rely on task completion and think a low unsafe success rate means the policy is safe.
The paper shows why that workflow misses risk. On unsafe insert outlet, pi_0 reaches attempt 0.93 and commit 0.80 before final success 0.44. A robot can get most of the way into a dangerous action even when it does not finish. The same benchmark also shows that fine-tuning on safe demonstrations can raise safe success and unsafe success together. For a team shipping household or service manipulation, the near-term build is a semantic pre-execution check tied to a refusal action, plus stage-wise logging in evaluation. A cheap validation pass is to replay a small set of safe and unsafe twin tasks and look for policies whose unsafe commit rate rises as general task skill improves.