Robot program verification
Robot program verification is proving — before anything reaches the floor — that a robot program stays within joint limits, reaches every target, collides with nothing, and does what the plan says in the time the plan claims. When the program was written by an AI, verification is not optional diligence; it is the difference between a tool you can trust and a demo you can't run.
Why AI-written programs must be machine-checked
A language model's default failure mode is a confident answer. Ask an unguarded model for a pick-and-place program to a target outside the robot's reach and it will hand you one anyway — plausible-looking, well formatted, and wrong. Human review alone doesn't close the gap: the errors that matter are not syntax errors but a pose two degrees past a joint limit, or a swept volume that clips a fixture only while the gripper carries the part. Those are found by computation, not by eye.
The 8-check kinematic oracle
Every program the Factory Agent authors must pass an eight-check verification suite against the robot model's datasheet kinematics before it is marked verified:
- Reachability — every target pose is confirmed reachable, with the actual margins reported
- Joint limits — no commanded pose exceeds any axis limit at any point along the path
- Path continuity — no teleports, no discontinuities between motion segments
- Collision checking — the full swept motion is sampled against the cell (600+ samples per program), part-in-gripper included
- Payload — part mass and tool mass are checked against the robot model's rated capacity
- Timing — claimed cycle time is validated against achievable joint velocities
- Tool and frame consistency — offsets and reference frames match the cell as built in the twin
- Task completeness — the program provably performs every step the plan assigned it
When a task is infeasible, the agent refuses with the number — "target 214 mm beyond reach," not a program that fails on the floor.
Verification you can hand to an auditor
Each deploy pack carries verification provenance: which checks ran, what they measured, which strategy variants were compared, and who (agent or human) approved each change. Your PLC and safety engineers keep the final word — an approvals workflow gates anything consequential — but they review evidence, not vibes.
Common questions
Does verified mean safe? Verified means kinematically proven in the twin: reach, limits, collisions, timing, payload. Site safety validation — risk assessment, guarding, commissioning checks — remains your process; the deploy pack's safety-zone proposals and provenance feed it.
What robots does this cover? Industry-standard 6-axis robot models with datasheet kinematics; programs are generated in vendor-native code that runs unmodified on the controller.
Related: factory layout planning · Emboscale vs traditional OLP
Book a demo to see a program authored, verified, and refused-when-wrong, live.