Describe the board. Typmax picks real parts, wires them by rule, checks every number against the datasheet, and hands you a KiCad project with the proof attached.
Ask a language model for a schematic and you get a drawing that looks right. On the public benchmarks about 8 % of those drawings are fully correct, and each edit makes them worse — from 80 % to 26 % over fifteen changes. The model recalls a rule of thumb, drops a pull-up, forgets which pin is a boot strap, and there is nothing in the loop that would notice.
Typmax turns that around. The model is the planner: it proposes small, typed changes to a structured design. Deterministic code does the engineering: it wires by rule, derives every net, sizes every pull-up, checks every logic level and every rail against the parts' own datasheets, and writes the KiCad files. The model never touches them and never holds the design in its head.
The goal is the whole board. Today that means the schematic: real parts, every net derived, every check computed and cited. Next it means layout — the same engine carrying the same constraints onto the PCB, with the layout tool's own design-rule check in the loop, so a rule that held on the schematic still holds on copper. At every stage the principle is the same: every result arrives with its arithmetic, its assumptions, the app note it came from, and an honest list of what was not verified.
And when a domain is dangerous — battery charging, mains, motor drive — it runs its checks and then insists on a human.
"ESP32-S3, BME280 on I²C at 400 kHz, GPS on UART, 3.3 V from an LDO."
Add this part, bind that pin, set this bus speed. Typed, checked, revertible.
Rules from the datasheets, real part records, derived nets, every number computed and cited.
A project with real parts, plus the dossier that says why each check passed — or didn't.
Computed values, the assumptions used, the inputs that weren't verified, and the app note the formula came from. A pass without evidence doesn't exist.
Every part is a record with pins, levels, currents and limits taken from its datasheet, and each value is tagged by who verified it. You see when a number came from a model instead of a person.
Edits are small and typed, with a revision check. What you fixed stays fixed; the model can't regenerate your design by accident.
Schematic, project, netlist and BOM in KiCad's own formats. Export is always on. No format sits between you and your board.
Constants live per part and per mode, citing the app note. Add a rule and every design ever made is re-checked against it.
LiPo charging, mains, motor drive: it runs every deterministic check it has, then marks the design for human review. That never gets softened.
We'd rather tell you now than have you find out on a board.
Seats open in small batches as the catalog grows. The parts you name go to the front of the verification queue.