
OSO BOOK B1
joeycastillo/The-Open-Book
For details on how to build, test and use Open Book, I've made documentation available here.

Collaborative Hardware Description Language
Sensor node is an open-source printed circuit board by conol-ai, from the conol-ai/cohdl repository on GitHub, published under the MIT licence. It is a 2-layer board with 14 parts on 14 nets.
It is built around the ESP32-S3-WROOM-1-N8. Its parts include 5 capacitors, 4 resistors, 2 ICs, 1 diode and 1 connector. It belongs with the home automation and IoT and sensors and measurement boards and the ESP32 boards of this library.
The acceptance test from the MVP Definition
(docs/design/09-mvp-definition.md): from a one-paragraph natural-language
spec — "An ESP32-S3-based sensor node: USB-C power/data, one MEMS microphone,
one status LED, a 3.3V LDO regulator, standard decoupling" — an LLM (no
fine-tuning, prompted only with the language reference) writes .cohdl
source; the compiler grades it; diagnostics are fed back verbatim; the loop
lands on a clean design that emits a real KiCad netlist + BOM.
Reproduce with python3 harness/repair_loop.py (see the harness README
header for backends).
| Run | Model | Reference | Attempts | Caught & repaired |
|---|---|---|---|---|
| 1 | claude-opus-4-8 | full | 2 | E202 ×2 (unresolved name), D003 warning |
| 2 | claude-opus-4-8 | full | 1 | — clean first try |
| 3 | claude-opus-4-8 | full | 1 | — clean first try |
| 4 | claude-opus-4-8 | full, reworded spec | 1 | — clean first try |
| 5 | claude-opus-4-8 | lean (no design notes) | 1 | — clean first try |
| 6 | claude-opus-4-8 | lean, detailed spec | 2 | E202 (unresolved name) |
| 7 | claude-haiku-4-5 | lean | 1 | — clean first try |
| 8 | claude-opus-4-8 | lean, +custom tantalum device | 1 | — clean first try (wrote device + impl mapping + part correctly) |
| 9 | claude-haiku-4-5 | lean, +custom tantalum device | 2 | E701 — unresolved required pin, repaired |
transcript-flagship-haiku-e701.md is
the run the MVP's non-negotiable clause asks for. On attempt 1 the model left
the ESP32-S3's chip-enable pin unwired, and the type checker — not DRC —
caught it as a compile error naming the exact line:
error[E701]: required pin `SensorNode::esp32.EN` is unresolved: add it to a `net` or explicitly mark it `nc`
--> src/main.cohdl:20:5
|
20 | inst esp32: ESP32_S3_WROOM_1_N8
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
:: std/soc.cohdl:13:9
|
13 | required EN: 3 [input]
| ---------------------- `EN` is declared `required` on device `ESP32_S3_WROOM_1` hereThis is the exact mistake class (a forgotten wire) that v1 shipped silently
and that RFC-002 moved into the type system. The diagnostic was fed back
verbatim; attempt 2 wired EN through a 10k pull-up and landed clean —
sensor-node.net and
sensor-node-bom.csv are its emitted artifacts.
Two supplementary transcripts:
transcript-opus-e202.md — a resolution-error
catch + repair cycle (the model invented a v1-style bare net reference,
which the MVP grammar deliberately dropped).transcript-opus-custom-device.md —
the expressiveness half of the thesis: asked for a part the std library
doesn't have, the model declared a polarized tantalum device, the explicit
impl TwoTerminal pin mapping (A: Anode, B: Cathode), impl Capacitor +
impl Polarized, and a part binding — all first try, all checked at the
impl statements.A note on difficulty: 6 of 9 runs were clean on the first attempt. The type system's catches fire exactly when the model errs — with a complete language reference in context, frontier models err rarely, which is the AI-generatability half of the design working as intended (Constitution priority #2). The failed attempts are what the compiler-as-oracle is for.
The import was driven through real KiCad (pcbnew 10.0.4, its own engine, via
tools/kicad_checkpoint.py — the same work File → Import Netlist performs):
sensor-node.kicad_pcb (open it directly in
pcbnew — footprints placed, pad nets assigned, connectivity drawn), with a
rendered sensor-node-board.pdf showing the
components and net connectivity: USB-C → CC pulldowns, VBUS → LDO → 3.3V
rail → decoupling bank + tantalum, ESP32 → I2S mic, EN pull-up, LED chain.The checkpoint caught a real netlist-fidelity bug, exactly as intended: the
std USB-C device used combined pad names (A1B12, S1) that don't exist on
KiCad's official HRO footprint (separate A1…B12 pads, shield SH). The std
device was corrected against the real footprint and everything regenerated.
To confirm by eye: open sensor-node.kicad_pcb in KiCad (or just the PDF),
and cross-check sensor-node-bom.csv — every line item carries a real MPN.
| Qty | Value | Footprint | References |
|---|---|---|---|
| 3 | 100nF | C_0402_1005Metric | C1, C2, C3 |
| 2 | 5.1kohm | R_0402_1005Metric | R2, R3 |
| 1 | 100uF | CP_EIA-3216-18_Kemet-A | C5 |
| 1 | 10kohm | R_0402_1005Metric | R4 |
| 1 | 10uF | C_0603_1608Metric | C4 |
| 1 | 1kohm | R_0402_1005Metric | R1 |
| 1 | AP2112K_3V3 | SOT-23-5 | U2 |
| 1 | ChipLED | LED_0603_1608Metric | D1 |
| 1 | ESP32_S3_WROOM_1 | ESP32-S3-WROOM-1 | U1 |
| 1 | ICS43434 | InvenSense_ICS-43434-6_3.5x2.65mm | MK1 |
| 1 | USB_C_Receptacle_2_0 | USB_C_Receptacle_HRO_TYPE-C-31-M-12 | J1 |

joeycastillo/The-Open-Book
For details on how to build, test and use Open Book, I've made documentation available here.

hackclub/OnBoard
💡 Join 1,000 teenagers and make your first PCB with a $100 grant!

bitaxeorg/bitaxeGamma
Bitaxe based on the BM1370 from the S21 Pro



hhuysqt/esp32s3-keyboard
USB/BLE keyboard driver based on ESP32S3-WROOM-1

katbinaris/nanofoc_devkit
Compact All-In-One BLDC Controler featuiring ESP32-S3, TMC6300 and Magalpha sensors. Small 35x35mm footprint.

Hack-a-Day/2025-Communicator_Badge
The 2025 Hackaday Supercon RF Communicator Badge
14 parts, built around the ESP32-S3-WROOM-1-N8. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
From the conol-ai/cohdl repository on GitHub, at the commit this page was made from: the board is docs/demo/sensor-node.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.
Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).