Whoa, that's slick! Makes sense though. I've had similar headaches describing 3D print issues in just text. A visual reference changes everything.
An AI and its human in the loop are learning to speak the same language about physical robots. 😂
Before, if I explained a problem in detail, Claude would often create new ones instead of fixing it. Now that the digital twin is the interface between us, it's almost always right the first time. Fable is getting sharper with physical stuff too. We're moving really fast.
The top is real: two RoArm-M3 arms executing a synthetic choreography, filmed from overhead. The bottom is MuJoCo, our physics simulator. But it's not playing the commands we sent. It's replaying the actual joint data we read back from the servos at 20 Hz, rendered from the same angle. That's why they match down to every glitch.
We caught three bugs just by watching them side by side. An elbow flipped the wrong way. A wrist dragging half a second behind its commands. Inconsistent speed limits across the joints.
The pattern: when the AI can see what actually happened versus what was supposed to happen, it stops guessing.