VERID: when working code makes an impossible move

Transcript

The original narration, preserved as published. Relative dates refer to the episode’s coverage window.

Can an AI write working code and still crash a lab robot? Google Research described VERID on October sixteenth: a system that checks an agent’s plans against the lab’s actual physical state before a robot moves.

VERID keeps a live digital model of the workbench. It tracks equipment geometry, liquid volumes and available pipette tips. The agent can inspect that state and dry run a proposed action in a virtual copy before sending commands to hardware.

One case study caught a move that looked fine in code: a pipette head would not fit inside a narrow container. The simulator rejected it, and the agent changed its plan. Valid syntax alone could not catch that mismatch.

Another run hit a plate reader failure. Persistent state let the agent resume without repeating completed liquid transfers. Synchronized video and action records also helped diagnose misleading measurements caused by physical mixing effects.

These demonstrations used colored water, not a breakthrough drug discovery. Google says humans review protocols and supervise robot runs. The paper describes research infrastructure; it does not establish a general, unsupervised lab. The practical lesson: test plans against the world they will change.