Etch

Etch turns one sentence into a real circuit board. You say “build a GPS tracker like an AirTag” and walk away. A team of agents picks real parts, writes the board spec, and places and routes it in KiCad. Then it has to prove the board works before it’s allowed to say done. Done is defined up front. Your spoken requirements become measurable checks, like board size, part count, current draw and LED behavior. A model only maps each requirement to a check. Plain code measures every value from the real build outputs: the .kicad_pcb, the gerbers, ERC, DRC and an ngspice simulation. A requirement that can’t be measured is reported as “cannot measure”, never guessed. For microcontroller boards, the generated firmware actually runs. The pin levels it sets drive the simulation, so the simulated LEDs come from the tested program. When a check fails, the agents repair the spec and rebuild, up to 4 times. A watchdog runs beside every build with a time limit for each stage. If a run goes silent or loops, it’s stopped with an honest message instead of a fake success. Nothing is invented. Every symbol, footprint and 3D model is a published file from KiCad’s libraries, LCSC or GitHub, with its source, licence and hash attached. If no real file exists, Etch says “not found”. Stack: Nemotron 3 Super and Nemotron 3.5 Lightning on Crusoe Managed Inference, NVIDIA’s prompt complexity classifier for routing, You.com Web Search for finding parts, KiCad 10, ngspice, easyeda2kicad, a Python backend, and a Three.js 3D viewer on Vercel.