Physical AI glossary
What is Embodiment?
In the guide: 1.1 Two kinds of AI
- There is no internet to train on. The useful data, such as how a particular factory line runs or how a hand closes on an egg without crushing it, is not on the web. Video of people working shows what happened but not the forces involved, and it is recorded from a human body, not a robot's. Robot data is also tied to the machine that produced it: a recording of one arm's joint angles does not transfer directly to an arm with different link lengths or a different gripper, a problem known as the embodiment gap. Someone has to go and collect this data, usually one demonstration at a time, which is why data is the field's biggest bottleneck (Part 4).
- Safety comes first. A heavy machine, or a humanoid that could fall on a child, needs far more testing than software does. What matters is behaviour in the long tail, the large set of rare situations that each occur seldom but together occur often: a reflective surface that confuses a camera, a person stepping into the work area, an object of an unfamiliar shape. A system can perform well on average and still fail badly in exactly these cases, so its average performance says little about whether it is safe to deploy.
- It runs in real time. A chatbot waits for a prompt and then answers. A robot works continuously and must react within milliseconds; the low-level control loops that hold a joint at its commanded position typically run at hundreds of hertz to a kilohertz. The robot also depends on hardware that changes over time: motors overheat and lose torque, sensors drift out of calibration, gears wear, and cables fatigue. The software has to keep working as the body underneath it degrades.
- It is tied to national interests. Physical AI touches defence, critical infrastructure, export controls and national rules on where data may be stored. Robots also record video inside factories, warehouses and homes, which raises questions of security and privacy that pure software rarely does. As a result each country tends to develop its own market rather than adopting one global product.
In the guide: 3.10 Cross-embodiment transfer
Embodiment means a specific robot body, with its own sensors, motors, joints and proportions. Cross-embodiment means one model controlling many different bodies. Surprisingly, a single model has worked on robots with different numbers of joints, and even on multi-fingered hands, without being told which robot it was running on.
In the guide: 3.10 Cross-embodiment transfer
The technical obstacle is that bodies differ in their degrees of freedom (the number of independent ways a robot can move, roughly one per joint), their camera placements, their joint limits and their dynamics. Practitioners handle this in a few standard ways. Action vectors from different robots can be padded to a common length, with unused entries ignored. Actions and joint readings can be normalised to a shared range so that one robot's large numbers do not dominate another's small ones. Some designs give each embodiment its own small input and output layers around a shared core, so that the core learns skills common to all bodies while the edges handle each body's specifics.