The Bitsy Board challenge

The Bitsy Board challenge

Rebuild the real thing. From Lesson 1's decomposition only — do NOT press "Load the Bitsy Board" until step 5 — take the Bitsy from silkscreen to fab files, then face the question every real product asks of its spec.

1. From the subsystem table, write the full pin map and per-part ledger by hand; state the predicted totals (24 components, 44 traces) before opening the Studio.
2. Write the complete spec: all nine subsystem lines from Lesson 1's table, 100mm x 80mm, named "My Bitsy". Every required field from memory first, palette to check yourself after.
3. Generate. Reconcile to exactly 24 components, 44 traces, 0 errors — the ledger is your referee before the engine is.
4. Route the PCB; confirm 42 and reproduce the two-net arithmetic in one line. Export Gerbers; verify eleven files and name the drill file.
5. NOW press "Load the Bitsy Board" and compare specs side by side. List every textual difference that does NOT change the board — id strings, version, power, the MCU note — and confirm both specs report identical counts. Two documents, one design: state in one sentence what makes two specs the SAME board.
6. Save your design as "My Bitsy". Open your Gerber zip in an online Gerber viewer and perform Lesson 4's inspection; note one thing you checked.
7. The closing question, in a short paragraph: name one Bitsy product feature the spec does not capture (Lesson 1 Q4's list), and one CIRCUIT the library cannot yet express — an amplifier between the light sensor and the ADC, say — and why (peripherals connect only to MCU pins and rails; there are no peripheral-to-peripheral nets). You have found the edge of the tool. Naming the edge is how the next version of every tool gets built — including this one.