CAIBI project benchmark: PAROL6 Desktop Robot Arm Prompt version 1.0 Help me build PAROL6 Desktop Robot Arm using the existing creator project at https://github.com/Source-Robotics/PAROL6-Desktop-robot-arm. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI. Project context: - A six-axis open desktop robot arm with printable structure, a published BOM, control electronics, GUI, Python API and ROS2/MoveIt routes. - Build context: Large set of 3D printed structural and joint components from the published STL package; Six-axis stepper-driven joint hardware, belts, bearings, pulleys and fasteners from the current BOM; PAROL6 control board or a compatible self-built control route; Power hardware and wiring specified by the current BOM and safety documentation; Computer running PAROL6 Commander or supported Python / ROS2 tooling; Optional gripper or other end effector. - Where AI helps: Control-code investigation, Python integration, ROS2 and MoveIt help, Diagnostics and automation logic. - Physical work: Source the BOM, Print and assemble joints, Wire power and control hardware, Calibrate axes, Test safely. - Main limitation: This is a high-consequence multi-axis machine. The source carries explicit serious-hazard warnings, and calibration, wiring, power, joint assembly and safe testing remain human responsibilities. Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so. Provide one practical build package: 1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications. 2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed. 3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability. 4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting. 5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions. 6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations. Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why. Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.