CAIBI project benchmark: OpenMower
Prompt version 1.0

Help me build OpenMower using the existing creator project at https://github.com/ClemensElflein/OpenMower. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A conversion that replaces the electronics in compatible robot mowers with GPS-guided, map-aware open hardware and software.
- Build context: Donor robotic mower chassis; OpenMower mainboard or supported universal board; Raspberry Pi 4 or supported compute route; RTK GNSS hardware; Motors and sensors from donor mower; Power and charging hardware.
- Where AI helps: Configuration help, Code investigation, Diagnostics.
- Physical work: Modify mower, Wire hardware, Install, Map, Test safely.
- Main limitation: This is a substantial machine conversion involving electronics, Linux, mechanical work and outdoor safety. AI does not remove the consequences of getting those parts wrong.

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.