Startup NetworxMountain West
DirectoryPeoplePatentsClinical TrialsRFPs & GrantsAnalysisSignal
Sign In
Startup Networx

A commons for deep tech in the Mountain West. Built and maintained by the community it serves. Open data, CC-BY.

© 2026 Startup Networx
Discover
DirectoryOpen RFPsEvents
Community
NewsResourcesDashboard
Contribute
Add an orgSuggest an editClaim an org
About
Embed widgetsModerationPrivacySign in
← News
News

No Free Checker: A Survey of Verifiers for Robot Policies

A verifier for robot policies reads a candidate behavior and returns a score for how well it did, used both to evaluate vision-language-action policies and to train them. Verifiers range from success detectors and reward models to runtime monitors, sa

robotics
Read on arxiv.orgvia RSS

From the feed

A verifier for robot policies reads a candidate behavior and returns a score for how well it did, used both to evaluate vision-language-action policies and to train them. Verifiers range from success detectors and reward models to runtime monitors, safety filters, and temporal-logic specifications. We survey roughly 150 verifiers and compare them along two properties. Availability is how much a verdict costs, how early in a rollout the verdict arrives, and how often a verdict can be asked for. Availability rises as verdicts get cheaper, earlier, and denser. Credibility is how much a high score tells us about the task. Credibility falls as the judgment becomes gameable and self-serving. We group the verifiers by who supplies the judgment: human verifiers, rule-based and formal verifiers, learned and pretrained verifiers, and model-intrinsic verifiers. Across the four families, we find that credibility falls as availability rises. Regardless of who supplies the judgment, there is no free checker. We then examine what validates a verifier itself, and how much a high score tells us. Three measures appear in the literature: agreement with human labels, the performance of the policy it trains, and behavior under reward hacking. We close with nine metrics that make a verifier claim checkable, and coordinates for the verifiers still to be built.

Continue reading on arxiv.org