Define interfaces before choosing a controller

List the sensing, motion, compute, and power jobs the robot must perform before comparing individual boards. Each job should have inputs, outputs, update rates, and a failure response.

That list naturally exposes dependencies across USB, UART, CAN, CSI, PWM, and power rails, and reveals shortfalls in ports or power headroom early.

Compatibility should not be a brand or software-version label. Record voltage range, logic level, connector, bandwidth, driver status, and mounting constraints for every critical connection.

The store specifications, build lists, and guides should be organized around those conditions so builders can trace a part back to the systems it can work with.