STATERA Library · Series 09 · Volume 06 · Chapter 09 · EN
Source: https://github.com/Statera-Library/09_Vol_06_Physical_AI_Hardware_Software_Co_Design/blob/main/Chapter_09_Case_Studies/Chapter_09_Case_Studies_EN.md

Volume 06. Physical AI Hardware Software Co Design

Chapter 09. Case Studies

09.01. Indoor AMR Co Design

Indoor autonomous mobile robots are an instructive example of Physical AI co-design because navigation quality emerges from the interaction of mechanics, sensing, computation, software, and control rather than from any single subsystem. An indoor AMR must move reliably through corridors, warehouses, factories, hospitals, and logistics facilities while sharing space with people, vehicles, racks, doors, and dynamically changing obstacles. The design therefore begins with operational requirements rather than with an isolated AI model.

The mechanical platform defines the physical envelope within which autonomy must operate. Wheel configuration, wheelbase, caster placement, center of gravity, payload distribution, suspension, tire properties, and structural stiffness influence acceleration, turning behavior, vibration, odometry, and stopping distance. A navigation algorithm cannot completely compensate for poor mechanical stability or unpredictable wheel-ground interaction, so mobility hardware and autonomous-control requirements should be developed together.

Differential-drive architectures are common because they provide mechanical simplicity, low cost, compact packaging, and straightforward kinematic control. However, wheel diameter differences, motor asymmetry, floor friction, caster dynamics, payload shifts, and manufacturing tolerances can introduce heading errors. Closed-loop velocity control, encoder calibration, inertial feedback, localization correction, and suitable caster geometry must therefore be considered part of the mobility design rather than treated as independent software improvements.

Actuator selection is similarly coupled to autonomous behavior. Motor torque, gear ratio, wheel radius, drive efficiency, acceleration limits, braking capability, and controller bandwidth determine the feasible motion envelope presented to the planner. AI-generated velocity commands must remain inside these physical limits, while low-level motor controllers should execute commands at substantially higher frequencies than perception or planning. This layered architecture separates fast deterministic stabilization from slower intelligent decision making.

Sensor architecture should be derived from the environments and failure modes that the robot is expected to encounter. LiDAR can provide reliable geometric measurements, cameras can contribute semantic and visual information, wheel encoders provide local motion estimates, and an IMU captures rotational and inertial changes. Additional depth cameras, ultrasonic sensors, bumpers, or safety scanners may be incorporated when required by operational risk, environmental geometry, redundancy objectives, or human-robot interaction requirements.

Placement is as important as sensor type. Occlusion from the chassis, payload, forks, manipulators, or surrounding structures can create blind regions even when high-quality sensors are installed. Sensor height and field of view affect detection of low obstacles, pallets, table surfaces, glass structures, and nearby people. The resulting configuration should provide sufficient spatial coverage while controlling data bandwidth, computational demand, power consumption, wiring complexity, and hardware cost.

Localization combines these measurements into a consistent estimate of robot pose. Wheel odometry may provide high-rate local motion information but accumulates error through slip and calibration uncertainty. LiDAR-, vision-, or map-based localization can correct longer-term drift, while inertial measurements improve short-term orientation estimation. The important co-design principle is that localization accuracy depends on sensor quality, mechanical repeatability, synchronization, calibration, environmental observability, and compute latency simultaneously.

The perception pipeline converts raw measurements into representations useful for safe navigation. Depending on the AMR, these may include obstacle maps, occupancy grids, free-space estimates, semantic objects, traversability information, dynamic-object tracks, or learned environmental features. Increasing sensor resolution or adding modalities can improve environmental understanding, but it also increases memory traffic and inference workload. Sensor selection and AI architecture must therefore be evaluated against the available compute platform as a unified system.

Indoor navigation normally contains multiple timing layers. Motor current and velocity loops operate at relatively high frequencies, localization and obstacle processing run at intermediate rates, and global planning or higher-level reasoning may operate more slowly. What matters is not simply maximum processor throughput but predictable sensing-to-action latency. Excessive delay or jitter can make an otherwise accurate perception model operationally unsafe because the physical environment continues evolving while computation is performed.

This requirement favors heterogeneous computing. Microcontrollers or real-time processors can manage motor control, emergency interfaces, watchdogs, and deterministic I/O, while CPUs execute middleware, localization, mapping, and system management. GPUs or NPUs can accelerate deep perception, multimodal fusion, learned planning, or more advanced Physical AI models. Separating control compute from AI compute also provides fault containment: overload or failure of an intensive AI workload need not immediately destabilize basic vehicle control.

Compute sizing should be based on the complete workload rather than nominal accelerator performance. Camera decoding, point-cloud processing, localization, neural inference, map updates, planning, logging, visualization, communications, and safety monitoring compete for processor time, memory bandwidth, and storage bandwidth. Peak utilization should retain sufficient margin for transient workloads and degraded conditions. Otherwise, apparently adequate hardware can produce latency spikes precisely when environmental complexity increases.

Power and thermal design impose another physical boundary on AI capability. Drive motors usually dominate energy during motion, but processors, sensors, networking equipment, storage, and cooling create continuous electrical loads. A larger accelerator can enable more sophisticated models while reducing battery runtime and increasing cooling requirements. Sustained inference performance should therefore be evaluated thermally, because benchmark performance available for short periods may not be maintained inside an enclosed AMR during extended operation.

Safety architecture should remain functional even when advanced autonomy becomes unavailable. Emergency stopping, motor disable, protective sensing, speed limitation, watchdog supervision, communication-loss handling, and controlled fallback behavior should not depend exclusively on a large neural model. A useful design principle is graceful degradation: loss of a camera, GPU workload, network connection, or high-level planning component should move the robot toward a defined reduced-capability state rather than an uncontrolled system failure.

Connectivity can enhance an indoor AMR without becoming a prerequisite for immediate physical safety. On-robot computation should retain localization, obstacle avoidance, essential planning, and control capabilities required for autonomous operation. On-premise infrastructure can support fleet coordination, shared maps, heavier inference, data aggregation, monitoring, and model distribution, while cloud resources can provide large-scale training, analytics, and lifecycle management. This hierarchy allows workload placement according to latency and availability requirements.

Fleet deployment introduces additional co-design constraints because individually capable robots must coexist efficiently. Traffic management, intersection negotiation, charging schedules, task allocation, map consistency, network capacity, and congestion management affect both robot hardware utilization and autonomy software. Local collision avoidance should remain onboard, whereas broader traffic optimization can be performed by infrastructure with a longer decision horizon. The architecture consequently distributes intelligence according to the physical scope and timing of each decision.

Payload variation must also be included in the autonomy design. Added mass changes acceleration, braking distance, wheel loading, energy consumption, structural deflection, and sometimes sensor visibility. An AMR optimized only in an unloaded laboratory configuration may behave differently when carrying its rated payload. Motion constraints can therefore be parameterized by load state, allowing planners and controllers to reduce acceleration, cornering speed, or stopping assumptions when the physical configuration changes.

A practical co-design process iterates between requirements, physical modeling, simulation, prototype measurement, and software profiling. Engineers can establish target payload, speed, stopping distance, localization accuracy, runtime, perception range, compute latency, and cost, then allocate these requirements across mechanical, electrical, sensing, compute, and software subsystems. Measurements from prototypes reveal whether performance limitations originate from AI accuracy, actuator dynamics, sensor geometry, timing, power, thermal behavior, or interactions among them.

The resulting indoor AMR should therefore be understood as a cyber-physical intelligence platform rather than a mobile computer carrying sensors. Mechanical dynamics shape what can be controlled, sensors determine what can be observed, computation limits what can be inferred in time, and software determines how available information becomes action. Hardware-software co-design aligns these elements so that improvements in one subsystem translate into measurable improvements in complete-system autonomy.

This case also demonstrates why Physical AI architecture should be scalable rather than optimized for one fixed model. A well-designed AMR can evolve from classical localization and navigation toward learned perception, multimodal world representations, predictive models, and more capable reasoning without replacing every underlying subsystem. Modular sensors, heterogeneous compute, deterministic control boundaries, standardized data interfaces, and explicit resource budgets create the foundation for that evolution.

09.02. Outdoor AMR Co Design

Outdoor autonomous mobile robots (Outdoor AMRs) represent a more demanding Physical AI co-design problem than indoor platforms because the robot must operate under continuously changing terrain, weather, lighting, connectivity, and localization conditions. Roads, construction sites, farms, campuses, industrial yards, and mixed outdoor environments introduce slopes, uneven surfaces, gravel, mud, water, vegetation, curbs, and unpredictable obstacles. Consequently, the system must be designed around the interaction between mobility hardware, sensing, computation, autonomy, energy, communication, and environmental robustness rather than treating outdoor navigation as an extension of indoor software.

The mechanical platform establishes the physical capabilities available to the autonomy system. Wheel diameter, wheelbase, track width, ground clearance, suspension, steering geometry, drive configuration, tire characteristics, chassis stiffness, and center of gravity determine how the robot responds to terrain. Payload distribution can further change traction, braking distance, rollover stability, and energy consumption. A planner cannot compensate indefinitely for inadequate mechanical capability, so terrain requirements, target speed, payload, obstacle height, slope, turning radius, and required ride stability must be considered simultaneously during platform design.

Outdoor actuation must tolerate substantially greater variation in wheel-ground interaction than indoor operation. Loose soil, gravel, wet pavement, grass, mud, and uneven terrain can produce wheel slip and rapidly changing traction. Motor torque, gearbox selection, differential or steering architecture, braking capability, suspension travel, and actuator control bandwidth therefore become part of the autonomy problem. Closed-loop wheel control should combine encoder information with inertial and localization feedback so that the controller can distinguish commanded motion from actual vehicle motion and provide reliable state information to higher-level planning.

Localization is one of the most important differences between outdoor and indoor AMRs. GNSS can provide global positioning, but multipath, signal obstruction, atmospheric effects, poor satellite geometry, and intentional or accidental interference can reduce reliability. High-precision RTK GNSS can improve absolute accuracy when correction services are available, while IMU and wheel odometry provide short-term continuity. LiDAR, cameras, landmarks, maps, and other localization methods can provide complementary information. A robust outdoor architecture therefore treats localization as a multi-source estimation problem rather than depending on one absolute positioning technology.

Outdoor perception must handle a much wider range of visual and geometric conditions. Sunlight, shadows, reflections, rain, fog, dust, snow, nighttime operation, vegetation, and rapidly changing backgrounds can affect cameras and other sensors. LiDAR provides useful geometric information but can also be influenced by weather and surface properties. Radar can contribute robustness for selected detection tasks, while cameras provide semantic information that geometric sensors alone may not capture. Sensor selection should therefore consider complementary failure modes, spatial coverage, update rate, bandwidth, compute requirements, and environmental protection.

Sensor placement becomes particularly important when the robot must detect terrain and obstacles rather than simply maintain a planar navigation map. Forward sensing should provide sufficient stopping distance at the intended speed, while downward or angled sensing can reveal potholes, steps, curbs, rocks, terrain discontinuities, and traversability changes. Sensor mounting must also protect the sensing system from vibration, contamination, water, dust, and mechanical impacts. Calibration and time synchronization are critical because small spatial or temporal errors can become significant when a moving robot fuses measurements from multiple sensors.

The perception and world-modeling stack should transform raw outdoor observations into representations that support both navigation and physical risk assessment. These representations may include occupancy, elevation, traversability, semantic objects, dynamic obstacles, terrain classes, predicted obstacle motion, and uncertainty. Unlike a simple indoor occupancy map, an outdoor world representation may need to distinguish between a visually open region that is physically traversable and one containing soft soil, steep terrain, standing water, vegetation, or an unsafe surface. The autonomy system therefore needs to connect perception with the physical capabilities of the platform.

Outdoor planning must account for vehicle dynamics as well as geometric feasibility. A path that is mathematically collision-free may still be unsuitable because of excessive slope, insufficient traction, high rollover risk, poor surface conditions, excessive vibration, or energy cost. Local planning should therefore incorporate vehicle speed, steering or differential-drive limits, braking capability, terrain confidence, and obstacle uncertainty. Global planning can optimize longer routes according to distance, time, terrain quality, energy, and mission priorities, while local control continuously adapts to the actual physical environment.

Computing architecture must support these workloads without compromising real-time control. A real-time controller can manage motor commands, safety interfaces, watchdog functions, and deterministic I/O, while CPU resources handle localization, mapping, planning, and system management. GPU or NPU resources can execute camera perception, LiDAR processing, sensor fusion, learned traversability estimation, object detection, and more advanced Physical AI models. Because outdoor environments can generate substantially more complex observations than controlled indoor environments, compute capacity should include margin for peak workloads and degraded operating conditions.

Outdoor AMRs also require a carefully designed edge and offboard computing relationship. Essential perception, localization, obstacle avoidance, planning, and control must remain available on the robot because connectivity may be intermittent or completely unavailable. On-premise infrastructure can support fleet management, shared maps, heavy analytics, model evaluation, and centralized monitoring, while cloud resources can support large-scale training and long-term data analysis. This separation allows the robot to preserve operational autonomy while using external computing resources whenever communication quality, latency, security, and mission requirements permit.

Power and thermal co-design become more significant as outdoor robots increase in size, speed, payload, and sensing capability. Larger motors consume substantial energy during acceleration and difficult terrain traversal, while GPUs, sensors, networking, and cooling systems create additional continuous loads. Battery capacity should therefore be evaluated together with mission distance, terrain resistance, payload, ambient temperature, compute workload, and charging strategy. Thermal design must also account for direct solar heating and outdoor temperature variation because sustained AI performance can decrease when processors reach thermal limits.

Safety and graceful degradation are essential because outdoor robots may operate farther from human supervision and in environments with greater physical uncertainty. Emergency stopping, protective sensing, communication-loss behavior, watchdog monitoring, redundant localization or sensing, and controlled fallback modes should remain functional when advanced AI components fail. If confidence in localization, perception, terrain classification, or communication falls below an acceptable threshold, the robot should reduce speed, restrict maneuvering, stop, or return to a predefined safe state rather than continuing with unjustified confidence.

Fleet operation introduces another layer of co-design because multiple outdoor AMRs must share roads, paths, work zones, charging resources, maps, and communication infrastructure. Task allocation, traffic management, route coordination, shared environmental knowledge, and fleet-level monitoring can improve utilization, but local collision avoidance and immediate safety decisions should remain available onboard. The overall architecture should allow individual robots to operate independently while exchanging useful information with the fleet. This creates a scalable transition from single-robot autonomy toward distributed Physical AI.

A practical outdoor AMR co-design process therefore proceeds iteratively from mission requirements to mechanical design, sensor architecture, compute allocation, autonomy software, simulation, prototype testing, and field validation. Simulation can evaluate terrain, dynamics, sensing, planning, and workload before physical deployment, while field testing reveals interactions that are difficult to model accurately. Measurements of localization error, traversability accuracy, stopping distance, latency, energy consumption, thermal behavior, communication reliability, and failure recovery should feed back into the next design iteration.

The resulting outdoor AMR should be understood as an integrated cyber-physical system whose intelligence is constrained by the physical environment and whose physical capability determines the useful operating range of its AI. Robust outdoor autonomy emerges when mechanics, actuation, sensing, localization, world representation, planning, control, computing, power, communication, and safety are designed together. The objective is not simply to install a more powerful AI model, but to create a platform in which available intelligence can be executed reliably, within physical limits, under real environmental uncertainty and over the complete operational lifecycle.

09.03. Mobile Manipulator Co Design

A mobile manipulator combines autonomous mobility with robotic manipulation, creating a Physical AI system in which the base, arm, end effector, sensors, computing platform, and control architecture must be designed as one integrated system. Unlike a fixed industrial manipulator, the robot must continuously account for changes in its position, orientation, payload, support conditions, and surrounding environment. The co-design problem therefore extends beyond achieving arm accuracy or navigation performance independently and focuses on how mobility and manipulation interact during complete task execution.

The mobile base determines the physical conditions under which manipulation can be performed. Wheel configuration, chassis stiffness, suspension behavior, footprint, payload capacity, center of gravity, and positioning accuracy influence the stability of the arm and the repeatability of end-effector motion. When the arm accelerates or carries a payload, reaction forces can affect the base, while uneven floors or small localization errors can change the manipulator workspace. Mechanical design must therefore consider the combined center of mass, dynamic loading, stability margin, and required manipulation accuracy rather than treating the base and arm as independent products.

Manipulator selection must be matched to the intended mobile tasks. Degrees of freedom, reach, payload, joint torque, joint speed, compliance, repeatability, and end-effector configuration determine which operations are physically achievable. A long-reach arm may provide greater workspace but can create larger moments on the mobile base and increase stability requirements. Conversely, a compact arm may simplify mechanical integration but restrict access to objects. The appropriate architecture is therefore determined by the relationship between task geometry, base mobility, manipulation workspace, payload, and required precision.

The end effector represents the final physical interface between AI decisions and the environment. Grippers, suction devices, tools, force-controlled interfaces, or application-specific mechanisms must be selected according to object shape, material, weight, contact conditions, and task requirements. Manipulation performance depends not only on the mechanical design of the end effector but also on perception, grasp planning, force estimation, and actuator control. A co-designed system should allow the AI to reason about what actions are physically executable instead of generating abstract manipulation commands without considering contact and grasp limitations.

Perception must cover both navigation and manipulation requirements. Cameras, depth sensors, LiDAR, force or torque sensing, joint encoders, and inertial sensors provide complementary information about the robot, objects, and environment. Navigation requires awareness of free space, obstacles, and robot pose, while manipulation requires accurate object localization, geometry, surface information, grasp points, and relative pose. Sensor placement is therefore a system-level optimization problem because sensors mounted for navigation may not provide sufficient visibility for close-range manipulation, while arm-mounted sensors may introduce vibration, occlusion, or changing viewpoints.

The world representation for a mobile manipulator must connect the global environment with local task geometry. A navigation system may maintain a map of rooms, corridors, obstacles, and reachable regions, while the manipulation system requires detailed representations of objects, surfaces, contact points, and arm configuration. These representations must remain spatially and temporally consistent as the robot moves. The system should understand not only where the robot is, but also where the target object is relative to the robot base, manipulator, and end effector at the moment an action is executed.

Planning consequently operates across multiple levels. A high-level task planner determines what sequence of actions is required, while navigation planning determines where the mobile base should move and manipulation planning determines how the arm should reach and interact with the target. These plans cannot be completely independent because the final manipulation pose may require a particular base position and orientation. Mobile base placement should therefore be treated as part of the manipulation problem, allowing the system to search for configurations that jointly satisfy reachability, collision avoidance, stability, visibility, and task accuracy.

Control must bridge these planning layers while respecting the dynamics of both the mobile base and manipulator. The base controller manages vehicle motion, while joint-level controllers regulate position, velocity, torque, or force at much higher frequencies. Coordinated control may be required when arm motion changes the robot\'s center of mass or when manipulation forces influence base stability. AI-generated actions should remain within actuator limits, joint limits, velocity constraints, collision boundaries, and stability margins. This layered structure allows high-level intelligence to operate at a slower rate while deterministic low-level control maintains physical stability.

Computing architecture should separate deterministic control workloads from computationally intensive AI workloads while maintaining sufficiently low end-to-end latency. Real-time processors can handle motor control, safety functions, joint control, and watchdog operations, while CPUs can support localization, planning, system coordination, and robot middleware. GPUs or NPUs can accelerate visual perception, object detection, 3D reconstruction, multimodal fusion, grasp prediction, learned policies, and more advanced Physical AI models. Memory bandwidth and data movement become particularly important because camera, depth, LiDAR, and joint data may need to be processed simultaneously.

Mobile manipulators also require careful edge and offboard computing partitioning. Essential perception, localization, collision avoidance, motion control, and manipulation execution should remain available on the robot so that the system can continue operating safely when network connectivity is limited. More computationally intensive model training, fleet analytics, large-scale data processing, simulation, and model evaluation can be performed on on-premise or cloud infrastructure. This architecture enables the robot to retain immediate physical autonomy while benefiting from centralized intelligence when communication and latency requirements permit.

Power and thermal constraints become more complicated because the platform must support both mobility and manipulation. Driving motors, arm actuators, sensors, compute accelerators, networking equipment, and cooling systems compete for the same energy resources. Manipulation can create short-duration peak loads, while continuous perception and AI inference generate sustained compute loads. Battery capacity, power distribution, actuator efficiency, thermal design, and runtime should therefore be evaluated together with mission duration and task frequency. The objective is not maximum instantaneous capability but predictable performance throughout the complete operating cycle.

Safety requires explicit coordination between mobility, manipulation, perception, and control. The robot must prevent collisions involving both its chassis and extended arm, maintain safe separation from humans, detect unexpected contact, and enter controlled fallback states when perception or planning becomes uncertain. Emergency stopping and low-level protective functions should not depend exclusively on complex AI models. When localization confidence decreases, an object is lost, communication fails, or the manipulation state becomes inconsistent, the system should reduce motion, stop the relevant subsystem, retract when safe, or transition to a predefined recovery behavior.

A practical mobile-manipulator co-design process therefore connects mission requirements, mechanical integration, sensing, compute allocation, manipulation planning, mobility planning, simulation, prototype testing, and field validation. Simulation can evaluate reachability, collision geometry, dynamics, sensor visibility, workload, and power behavior before physical integration. Prototype testing then exposes real effects such as vibration, cable routing, calibration drift, structural deformation, actuator backlash, wheel slip, and timing variation. Measurements should be fed back into the architecture so that each iteration improves the complete robot rather than optimizing isolated components.

The resulting mobile manipulator should be understood as an integrated cyber-physical intelligence system. Mobility determines where manipulation can occur, manipulation determines how the robot can interact with the environment, perception determines what can be observed, computing determines what can be inferred within the available time, and control determines whether the intended action can be physically executed. Hardware-software co-design aligns these elements so that navigation, manipulation, perception, planning, actuation, safety, power, and computing operate as one coherent Physical AI platform. This integrated approach provides a foundation for progressively more capable autonomous robots without sacrificing real-time behavior, physical feasibility, or operational reliability.

09.04. Quadruped Co Design

A quadruped robot represents a distinctive Physical AI co-design problem because locomotion depends on continuous interaction among morphology, actuators, sensors, computation, control, and terrain. Unlike wheeled platforms, a quadruped must actively regulate body posture and foot placement while maintaining dynamic balance. Its autonomy therefore cannot be separated from legged mechanics. The robot hardware determines the feasible motion space, while AI and control determine how that physical capability is exploited under changing environmental conditions.

The leg mechanism is the foundation of quadruped mobility. Leg length, joint arrangement, actuator placement, body dimensions, foot geometry, structural stiffness, and total mass influence gait stability, stride length, energy consumption, and obstacle negotiation. The distribution of mass is particularly important because the robot must repeatedly accelerate and decelerate individual legs while controlling the body. Mechanical design should therefore consider the relationship among payload, center of mass, joint torque, ground clearance, expected terrain, and required locomotion speed rather than optimizing the body and legs independently.

Actuator design is tightly coupled with locomotion intelligence. Each leg normally requires coordinated control of multiple joints, and the available joint torque and speed determine whether the robot can support its body, recover from disturbances, climb slopes, step over obstacles, or accelerate dynamically. Gear reduction, motor efficiency, torque density, thermal capacity, backlash, compliance, and control bandwidth all affect the achievable gait. AI-generated motion commands must remain within these physical limits, while low-level joint controllers provide fast and stable execution beneath higher-level locomotion policies.

Foot-ground interaction introduces another major co-design requirement. A foot may encounter hard floors, gravel, grass, mud, rocks, stairs, or irregular terrain, and the contact state can change rapidly. The robot must estimate whether a foot is securely supporting the body, slipping, colliding with an obstacle, or losing contact. Proprioceptive sensing from joint position, velocity, torque, and current measurements can be combined with inertial and external perception to estimate contact and body state. Reliable contact estimation is essential for stable gait generation and recovery behavior.

The sensing architecture must support both body-state estimation and environmental understanding. IMUs provide high-rate information about body orientation and acceleration, while joint encoders and actuator measurements describe the internal configuration of the robot. Cameras, depth sensors, LiDAR, and other external sensors provide information about terrain, obstacles, and traversability. Sensor placement must account for leg motion, body vibration, self-occlusion, dust, water, lighting variation, and changing viewpoints. The resulting architecture should provide sufficient observability without creating excessive compute, power, or communication demands.

A quadruped requires a world representation that combines terrain geometry with the robot\'s physical state. The system may need to estimate elevation, surface inclination, roughness, obstacles, free space, traversability, and uncertainty while simultaneously tracking body pose, joint configuration, foot positions, and contact states. A terrain that appears geometrically accessible may still be unsafe because of low friction, excessive slope, unstable ground, or insufficient foothold quality. The world model must therefore connect environmental perception with the robot\'s current locomotion capability.

Locomotion planning operates across multiple temporal and spatial levels. A high-level planner can determine the desired direction, route, or task objective, while a locomotion planner selects appropriate gait patterns, foothold locations, body trajectories, and movement speeds. Local control then continuously adapts these decisions to actual contact conditions and disturbances. The planning system should consider terrain confidence, energy consumption, stability margins, actuator limits, and predicted body motion rather than selecting paths solely from geometric maps. This creates a direct relationship between world modeling, gait planning, and physical execution.

Control architecture must coordinate body motion, leg motion, and contact forces. High-level AI or locomotion policies can generate desired behaviors, while intermediate controllers convert those behaviors into body trajectories, foot trajectories, joint targets, or desired forces. High-frequency joint-level controllers then regulate position, velocity, torque, or impedance. This hierarchy allows learned policies to operate at manageable frequencies while deterministic controllers preserve stability and actuator protection. When terrain conditions change rapidly, feedback from proprioception and contact estimation must be able to modify the motion before instability develops.

Computing architecture should separate safety-critical real-time control from computationally intensive perception and AI workloads. Real-time processors can execute joint control, actuator monitoring, safety functions, watchdog operations, and deterministic communication. CPUs can support localization, mapping, planning, and system coordination, while GPUs or NPUs can accelerate visual perception, terrain understanding, sensor fusion, learned locomotion policies, and advanced world models. Memory bandwidth and data movement become important because multiple sensors and many joint channels may need to be processed simultaneously with strict timing requirements.

Power and thermal constraints are particularly significant for quadrupeds because locomotion requires repeated actuator work even when the robot is not carrying a large external payload. Motors may experience high transient loads during jumping, climbing, rapid acceleration, or recovery from disturbances. Continuous computation for perception and learned control adds another energy demand. Battery capacity, actuator efficiency, motor thermal limits, power electronics, cooling, and compute workload should therefore be evaluated as one system. The objective is sustained locomotion capability rather than short-duration peak performance.

Safety requires the robot to remain controllable when perception, communication, or learned autonomy becomes uncertain. Joint limits, torque limits, thermal protection, emergency stopping, watchdog supervision, contact monitoring, and controlled recovery should be implemented independently enough that failure of an advanced AI component does not immediately cause uncontrolled motion. When terrain perception becomes unreliable or a leg loses expected contact, the robot should be capable of reducing speed, changing gait, stabilizing its body, stopping, or entering a predefined recovery state.

A practical quadruped co-design process connects mission requirements, morphology, actuator sizing, sensing, compute allocation, locomotion algorithms, simulation, prototype testing, and field validation. Simulation can evaluate gait stability, terrain interaction, actuator loads, energy consumption, sensor behavior, and AI workload before extensive physical testing. Real robots then reveal effects such as compliance variation, backlash, vibration, thermal accumulation, contact uncertainty, actuator aging, and terrain behavior that are difficult to model perfectly. These measurements should continuously feed back into both hardware and software design.

The resulting quadruped should be understood as an integrated cyber-physical intelligence system in which morphology, sensing, world modeling, locomotion planning, control, computation, power, and safety are inseparable. The robot\'s physical structure determines what motions are possible, sensors determine what can be observed, computing determines what can be inferred in time, and control determines whether the intended behavior can be executed safely. Hardware-software co-design therefore transforms quadruped autonomy from a collection of independent algorithms into a coordinated Physical AI platform capable of adapting its behavior to changing terrain, contact conditions, and mission requirements.

09.05. Humanoid Co Design

A humanoid robot represents one of the most comprehensive Physical AI co-design challenges because its mechanical structure, sensing, actuation, computation, control, and intelligence must operate together across a highly variable physical environment. Unlike specialized mobile robots, a humanoid is expected to move through spaces designed for humans, manipulate objects using human-scale interfaces, maintain balance on two legs, and coordinate many degrees of freedom simultaneously. The design problem therefore cannot be reduced to selecting a capable AI model or a powerful actuator. It requires an integrated architecture in which physical embodiment and artificial intelligence continuously constrain and complement one another.

The humanoid body establishes the physical capabilities available to the autonomy system. Body dimensions, joint arrangement, limb proportions, mass distribution, structural stiffness, joint range of motion, and foot geometry influence balance, reachability, energy consumption, manipulation capability, and collision behavior. A human-like morphology provides access to environments built around human tools, doors, shelves, stairs, and workstations, but it also introduces mechanical complexity and unstable dynamics. The co-design process must therefore determine which aspects of human morphology are essential for the intended tasks and which can be simplified or redesigned to improve reliability, efficiency, manufacturability, and maintainability.

Actuator architecture is especially important because a humanoid contains many independently controlled joints that must operate simultaneously under changing loads. Motors, gearboxes, harmonic drives, transmissions, bearings, brakes, encoders, and joint controllers determine the available torque, speed, compliance, precision, and thermal capacity. The actuator system must support standing, walking, turning, climbing, reaching, lifting, and recovering from disturbances. High torque density is valuable for reducing mass, but compact actuators can create thermal and maintenance challenges. Hardware selection should therefore consider the complete duty cycle rather than optimizing peak joint performance in isolation.

Bipedal locomotion creates a strong coupling between mechanical design and control intelligence. Unlike a wheeled robot, a humanoid must continuously regulate its center of mass relative to its support region while changing foot contacts. Walking therefore requires coordination among body posture, hip motion, knee and ankle control, foot placement, contact forces, and momentum. The robot must respond to disturbances such as uneven ground, unexpected contact, payload changes, and external forces. A suitable architecture combines high-level learned locomotion policies with deterministic lower-level control so that intelligent behavior can adapt while physical stability remains continuously supervised.

The feet and lower limbs form the physical interface between the humanoid and the ground. Foot size, sole material, contact geometry, ankle range, compliance, and force sensing influence stability and walking efficiency. The robot must determine whether each foot is securely supporting the body, transitioning between contacts, slipping, or encountering an unexpected obstacle. Force-torque sensing, joint torque estimation, motor current, encoders, and inertial measurements can provide complementary information about contact state. These signals are particularly valuable because reliable locomotion requires the robot to understand not only where its body is, but also how its body is physically coupled to the environment.

Perception for a humanoid must support both navigation and manipulation within environments that contain objects, people, furniture, tools, and dynamic activities. Cameras, depth sensors, LiDAR, IMUs, joint encoders, force sensors, and tactile interfaces can provide complementary observations. Vision can identify objects and semantic relationships, depth sensing can provide geometry, LiDAR can support spatial mapping, and proprioceptive sensors can estimate the robot\'s internal configuration. Sensor placement is a major co-design problem because the robot\'s moving arms, head, torso, and legs can create occlusions and rapidly changing viewpoints. The system must provide sufficient observability without excessive computation, power, weight, or wiring complexity.

The humanoid world representation must connect large-scale environmental understanding with detailed body and object state. A useful representation may include global maps, local geometry, semantic objects, humans, free space, terrain, robot pose, joint configuration, contact states, and task-relevant relationships. The system must understand not only where an object is located but whether the humanoid can physically reach it, approach it, grasp it, and manipulate it without losing balance. This makes the world model inherently embodiment-aware. Perception, geometry, physical capability, and uncertainty must be represented together so that planning can reason about what is actually achievable.

Manipulation introduces another layer of co-design because humanoids are often expected to use tools, operate doors, move objects, and interact with human-oriented interfaces. The arm, hand, wrist, torso, and lower-body system must cooperate to create stable manipulation configurations. A reaching motion may require repositioning the feet, shifting the center of mass, or changing torso orientation before the hand can safely contact the target. Consequently, manipulation planning should not treat the arms as isolated mechanisms. Base posture, whole-body balance, hand configuration, contact forces, object properties, and task constraints must be considered as one whole-body manipulation problem.

Planning therefore operates across task, navigation, locomotion, and manipulation layers. A high-level task planner can determine what the robot should accomplish, while a navigation planner determines where the humanoid should move and a manipulation planner determines how the robot should interact with objects. A whole-body planner must connect these decisions because many tasks require simultaneous movement and manipulation. The robot may need to walk while carrying an object, reach while maintaining balance, or reposition its feet while applying force through its hands. Planning should consequently optimize task success together with reachability, stability, collision avoidance, energy, and execution uncertainty.

The control architecture should provide clear separation between high-level intelligence and fast physical stabilization. High-level policies can generate desired behaviors, locomotion targets, manipulation goals, or whole-body actions, while intermediate controllers translate these objectives into body trajectories, foot trajectories, joint targets, impedance commands, or contact forces. High-frequency servo loops then regulate individual joints and actuators. This hierarchical structure allows advanced AI models to operate at computationally practical frequencies while real-time controllers continuously enforce joint limits, torque limits, balance constraints, collision boundaries, and actuator protection.

Humanoid computing requirements are correspondingly substantial. Real-time processors must maintain deterministic joint control, safety monitoring, watchdog functions, communication, and actuator supervision. CPUs can manage localization, mapping, task planning, motion coordination, and system middleware, while GPUs or NPUs can execute visual perception, multimodal fusion, 3D reconstruction, learned locomotion, manipulation policies, world models, and potentially vision-language-action models. Because many sensors and joints operate simultaneously, memory bandwidth, synchronization, data movement, ...