Subterra’s integration architecture exposes timestamped pose, velocity, transform trees, covariance, point clouds, occupancy or voxel maps, semantic entities, dynamic obstacles, traversability, trajectory history and navigation integrity to the host robotics stack.
ROS 2-compatible adapters and platform APIs carry frame identifiers, acquisition timestamps, covariance and integrity with each output. Each contract specifies transform direction, covariance ordering and perturbation convention, clock domain, update rate, latency budget, quality of service and stale-data handling. Sensor extrinsics and timing offsets belong to the estimation and calibration contract; a delayed observation cannot silently acquire the time or frame of its arrival.
Map-frame corrections remain separate from the continuous odometry consumed by the controller. A correction invalidates affected route assumptions and triggers bounded replanning; it does not become an instantaneous body command. Spatial outputs inform autonomy while the host platform’s deterministic controllers enforce motion limits, stopping behaviour and recovery authority.