Asimov v1

Reconcile the fabrication inventory before ordering

The pinned archive contains mechanical and electrical design directories, including fabrication-oriented part paths and board files. However, the README links mechanical/FABRICATION_MANIFEST.csv, and that file is absent from the inspected archive inventory. A generator script and related workflow are present, but we did not run upstream code or generate a replacement inventory. A builder should resolve the missing manifest and reconcile it against the procurement BOM before ordering fabricated parts. [S001] [S004]

Electronics have two distinct roles. A Radxa CM5 carrier and stacked power-distribution board handle motion, while a Raspberry Pi 5 and supporting boards handle media. The electrical notes identify an onboard IMU and CAN connections, and explain that some wiring joins can only be completed after assembly. Preserve those board revisions and cable details with the mechanical design rather than treating the computers as interchangeable controllers. [S001] [S005]

Keep the roadmap separate from available behavior

Although the opening overview describes onboard software, the same README still lists Asimov Edge and the locomotion policy as forthcoming. The captured archive includes simulation and utility materials; it does not establish a complete, tested walking deployment. No policy performance, robot assembly or software installation was tested for this profile. [S001] [S004]

The project supplies CERN-OHL-S 2.0 hardware terms and GPL v2 software terms. These are separate scopes, and purchased components still need their own sourcing and rights checks. A support decision also needs the missing fabrication inventory, exact onboard software and firmware versions, and measured setup and maintenance work. [S006] [S007]