17.1 Purpose and Scope
This chapter instantiates RelationWorld theory for a practical mobile manipulator architecture:
- Mobile base: 4-wheel swerve drive on the plane
- Manipulator: 4-DOF arm
- Sensors: RGB/depth camera, 2D/3D LiDAR, IMU, odometry, joint states, optional force/contact
The aim is not to replace Chapters 1--16, but to provide an embodiment-level map:
17.2 Ontological Role of the Robot
In this embodiment, the robot is specialised as:
Hence, its operational priority is not arbitrary in-fruit dexterity, but reliable traversal over stem regions and intervention at door boundaries.
17.3 State and Action Model
17.3.1 Base state (swerve)
Discrete-time kinematics (time step ):
17.3.2 Arm state
17.3.3 Combined robot state and action
17.4 Base-Arm Coupled Kinematics
Let end-effector pose be
Then velocity is
or compactly
This coupling equation is the mechanical core of the end-to-end formulation.
17.5 Sensor to Relational Field
Sensor stream:
History encoder:
Node/edge construction:
Embodiment-conditioned edge score (example):
17.6 World Decomposition
Given thresholds and :
World summary:
17.7 Role Inference and Task Generation
Role family:
Role selection:
World deficit:
Task generation:
17.8 Navigation-Manipulation Pairing
Each task is decomposed as
with canonical execution phases:
For the first benchmark family (door handle/tray), these phases are mandatory.
17.9 Motion Latent and Hybrid End-to-End Objective
Motion latent:
Coupled objective (horizon ):
where
17.10 ROS 2 Interface Contract
Implementation-facing message/action contracts are standardised in package
antbot_relational_e2e:
RelationalWorld.msgRoleAssignment.msgGeneratedTask.msgDoorManip.action
This contract is the bridge between theory-level variables and executable ROS graphs.
17.11 Traceability to Core Theory
| Core theory (Ch.1--16) | Embodiment mapping (this chapter) |
|---|---|
| Relation tuple and weighted field | Sensor-conditioned graph features |
| Fruit/stem/door decomposition | Workspace partition and door intervention points |
| Theorems A--H (stability and structure) | Constraints and penalties in world-consistency objective |
| Existence and world reading | Role assignment + task generation pipeline |
| Dynamics (Ch.14) | Online update of world graph and role/task refresh |
17.12 Validation Gates
To move from specification to simulation:
- Dimensional consistency of state/action/kinematics equations.
- Interface completeness for world, role, task, and manipulation action.
- Task closure: door-handle/tray scenario must complete all four phases.
- Objective traceability: each objective term mapped to at least one theoretical primitive.
These gates define readiness for the simulation implementation phase.