CAIBI project benchmark: OpenScan Mini
Prompt version 1.0

Help me build OpenScan Mini using the existing creator project at https://github.com/OpenScan-org/OpenScan-Doc/blob/main/docs/hardware/OpenScanMini.md. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A compact open-source photogrammetry scanner that rotates small objects through controlled camera positions to create detailed 3D models.
- Build context: 3D printed OpenScan Mini frame, rotor, gears, backplate and object holders; Raspberry Pi 3B+ or 4 with microSD card; OpenScan Pi Shield and two stepper drivers; Two NEMA 17 stepper motors, one higher-torque and one lower-torque unit; Arducam IMX519 autofocus camera, with supported Pi Camera alternatives; Ring light and cross-polarizer module; 12 V power supply, ribbon cable, screws and nylon camera hardware.
- Where AI helps: Scan workflow planning, Image and mesh troubleshooting, CAD cleanup guidance, Configuration help.
- Physical work: Print parts, Assemble motors and camera, Prepare objects, Capture scans, Validate dimensions.
- Main limitation: Scan quality still depends on lighting, surface preparation, focus, object positioning and photogrammetry processing. The hardware does not make every object easy to scan.

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.