Embodiments
The same intelligence, through different forms.
A body is a way of reaching the world, not a separate product. Each embodiment below implements the same interface, so capability developed against one carries to the next.
Forms
Four ways Petrixia reaches the world.
Mobile robot
A mobile embodied assistant that moves through a home or care setting, carries out approved tasks, and stays available between them.
Petrixia Town
A simulated world for developing and testing robot behaviour before it is deployed physically — and for scoring it honestly once it is.
Phone and voice
The same conversation, memory and procedure capabilities without a physical robot, for settings where a body is not wanted or not yet affordable.
Future robot bodies
New hardware implements the same interface. A different body is a configuration change, not a rewrite.
Why this matters
A new body should be a configuration change.
The hardware adapter implements the same contract the simulated world does. That is what makes the claim testable rather than aspirational: the code that drives a body does not know, and does not need to know, which kind of body it is driving.
The practical test. Moving the embodiment process from the machine running the simulation to a separate one is a directory copy and a configuration edit. Nothing in the control loop, the skills or the telemetry depends on where it runs.