Verification

On the schematic

Check	What it catches
Pre-flight	Symbol and footprint names that do not exist. Unambiguous typos are corrected and listed; the rest are returned as findings.
SKiDL compile	A script that does not build a netlist. The error goes back to the synthesizer with the code.
ERC score	Unconnected pins, driver conflicts, missing power, single-pin nets. A ported electrical-rules check with a score.
KiCad ERC	KiCad’s own electrical-rules check on the written schematic.
Floating subsystems	A cluster of parts with no path to the rest of the circuit.
Footprints	A part with no footprint, or a custom IC without a real package.
Sourcing	A part with no distributor listing in stock. Reported, with candidates.

A design review reads the passing circuit and can send it back with blocking findings.

On the board

Check	What it catches
KiCad DRC	Clearance, track width, annular ring, hole-to-hole, copper-to-edge, courtyard overlaps, silkscreen on pads. Run by `kicad-cli pcb drc` with the project’s rules after a zone refill.
Fab minimums	The project carries the fab’s floors: minimum track, minimum drill, copper-to-edge clearance. The JLCPCB preset adds the per-feature limits KiCad only has as custom rules, such as plated ring and hole-to-track spacing.
Connectivity	KiCad’s ratsnest. A stranded pad or a severed pour counts, even when the router reported the net as done.
Parity	The board has exactly the footprints the netlist has. Mounting holes and fiducials the engine adds are marked board-only.
Plane integrity	Islands, slivers and stranded pads on poured nets.
Physics	Rail width against current, pair coupling and skew, impedance from the stackup.

The release gate

Fab files are built only when both of these hold:

Zero DRC errors from KiCad, with the fab’s rules.

Nothing unconnected in KiCad’s ratsnest.

A board that fails the gate is still yours. The KiCad project, the board and the DRC report are downloadable, the report names every open net and every violation, and the chat agent can diagnose it and run again. What you do not get is a gerbers.zip for a board that would come back wrong.

“Mostly routed” is the most expensive kind of board, because the error surfaces after the fab order. Koppar reports it as a failed board, not as a result.

Start

Your own agent

Free tools

Engine

Reference

On the schematic

On the board

The release gate

The same checks for agents

​On the schematic

​On the board

​The release gate

​The same checks for agents

On the schematic

On the board

The release gate

The same checks for agents