CAIBI project benchmark: Jubilee V2.2.2
Prompt version 1.0

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

Project context:
- An open CoreXY multi-tool motion platform designed to swap tools automatically for 3D printing, plotting and low-force custom automation, with a substantial science-automation ecosystem.
- Build context: Jubilee V2.2.2 aluminium frame, linear motion and CoreXY hardware; Kinematically coupled 300 x 300 mm bed platform and three-point autotramming hardware; Automatic toolchanger and 409 mm horizontal tool-rack system; Duet controller and expansion/control electronics for the selected build route; Stepper motors, wiring, power supply and current motion-platform harnessing; Application-specific tool plates, toolheads and tool harnesses supplied or built separately; Computer and network connection for configuration and automation; Optional Science Jubilee deck, labware, Raspberry Pi and scientific tools when used for lab automation.
- Where AI helps: Navigate the V2.2.2 BOM, CAD, fabrication exports, assembly and configuration material, Help choose between self-sourcing and the current Filastruder base-kit route, Explain Duet configuration, G-code and Science Jubilee software concepts, Help draft and review application-specific tool or deck designs, Generate checklists for wiring, commissioning, tool offsets and experiment setup, Help write Python control workflows and analyse logs or repeatability data, Trace current Science Jubilee examples for pipettes, syringes, cameras and labware.
- Physical work: Choose the exact base-platform sourcing route and application before buying parts, Assemble and square the frame, rails, CoreXY motion and kinematic bed system, Wire the controller, motors, heaters and power system with mains isolated, Install guards over exposed mains terminals and keep hands clear of belts and moving parts, Configure and commission motion before attaching expensive or hazardous application tools, Build or buy every application-specific toolhead and required harness that the base kit does not include, Calibrate tool pickup, offsets, bed or deck coordinates and the real process, Validate experiment, material or lab-safety requirements that sit outside the open motion-platform design.
- Main limitation: The base platform is only the beginning. The current $1,799.99 kit includes the motion platform, controller, motors and electronics but no working tools, and Science Jubilee describes a steep learning curve. Application-specific toolheads, harnesses, decks, software configuration, calibration and process validation remain additional. The power system also involves 120/240 V mains connections, so this is not casual plug-and-play electrical work.

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.