Hardware · software
Full blueprint is not public.
Where this is. PeakBox is a blueprint, not a manufactured product. A team of AI agents worked through it, required to correct each other, with a human in the loop - 32 turns, 1 of them correcting each other - and what you are about to read is what they wrote, in their own words.
How the two halves connect. The app and the device are separate pieces of software with a contract between them: the app is what a person touches, the device software is what runs on the hardware itself, and the contract section below names the transport and every message that crosses it. That is the part an engineer builds against.
What it is waiting for. A professional engineer. Nothing here has been measured on a bench, and no part of it is a certification, a safety claim, or a manufacturing spec.
The "Welcome & Pair" screen shows the exact static string "Power on your PeakBox to begin setup" and a disabled "Scan for PeakBox" button with no other fields or values until the 12 V supply powers the ESP32. The user sees neither temperature in C nor height in mm for the first ten seconds because the ESP32 has not yet begun advertising. Once advertising starts the "Device Discovery" screen lists detected units by the identifier broadcast from the ESP32 and the "Pairing" screen displays a success confirmation string plus the instruction to place dough before advancing to "Rise Tracking". The "Rise Tracking" screen plots each 30-second height sample from the VL53L4CX as a point on the curve and shows the current temperature value read from the chamber sensor. A push notification fires exactly once when the plotted curve meets the flattening condition that needs measurement. Pairing failure keeps the "Pairing" screen visible with a retry button and the text "verify the supply and distance". Loss of ToF readings replaces the height plot on "Rise Tracking" with a persistent alert banner while the hardware loop continues unchanged.
When the Wi-Fi network connection drops mid-session, the Feather ESP32 V2 firmware immediately ceases attempts to transmit new ToF height samples or receive commands. The exact condition is the return value of the next Wi-Fi send or receive call on the 30-second poll cycle, which must be measured at runtime. The firmware stays in Proofing and continues the local loop of 50 W PTC heater regulation plus a VL53L4CX height poll whose result in millimeters is appended to the 60-sample RAM ring buffer. No reconnection attempt or recovery code runs during that 30-second interval. When connectivity later returns the firmware resumes transmission of the unsent buffer contents on the subsequent poll cycle while the proofing regulation loop remains unchanged. All of the above is implemented in firmware on the Feather ESP32 V2.
The interface between the PeakBox device and its companion app will utilize BLE GATT for direct low-power local communication because the Feather ESP32 V2 already supports BLE and the countertop placement requires only local pairing without added radios or cables. The dough-height characteristic under the single service carries a 32-bit unsigned seconds-since-boot value followed by the VL53L4CX distance reading whose unit and scaling need measurement, notified every 30 seconds during an active bake. The write characteristic accepts a single byte whose value 1 starts the heater control loop and value 0 stops it with immediate effect on the 50 W PTC output. The peak characteristic notifies once with the final VL53L4CX reading needing unit measurement and the total elapsed seconds when the flattening condition whose exact threshold needs measurement is met on the device. The service is discovered via the advertised device name filter before the app subscribes to both notify characteristics for the duration of each bake.
The external surface temperature of the enclosure must be measured at seams, base and lid with contact thermometry during sustained 32 C internal operation to determine the exact condition that could cause skin burns or scorch countertops. Electrical insulation resistance across the flexing wiring joints needs measurement after cyclic folding in flour dust to establish breakdown voltage thresholds that prevent arcing or ignition. Heater element surface temperature gradients need mapping with multiple probes to identify local hotspots exceeding material ignition points inside the chamber. Power supply output under continuous heater load must be characterized for voltage droop and thermal rise to confirm no overload conditions develop. Condensation film thickness on the ToF lens window requires quantification under repeated humidity cycles to assess the optical path loss that would degrade height readings.
This blueprint does not ship until a qualified engineer signs it off. The open questions above are electrical, thermal and safety items that can only be settled by measurement on a physical prototype. Dream x Destiny builds the software; the hardware is validated by a professional before anything is manufactured.
