Format
Every number in your board, written down.
Four document kinds, one of them the dossier. Everything the engine produces validates against the same contract it consumes — including its own output. The reference lands with the private alpha; here's the shape of it.
Document kinds
Four kinds, one schema.
component
A real part
Pins with KiCad's own type enum, rails, levels as rail ratios, currents operating and abs-max, strapping with consequences, thermal, sourcing.
interface_def
Rules as data
Roles, parameters and validation rules with the app note each constant comes from. Add one and every design ever made is re-checked.
design
Your board
Instances, buses, connections, rails, declared assumptions and risk flags. Nets are never written here — they're derived.
validation_report
The dossier
Findings with computed intermediates, assumptions, unverified inputs, source authority and a machine-actionable fix hint.
The dossier
Read the whole argument in one screen.
Every check the engine ran, its arithmetic, the authority behind the formula, and an honest list of what it could not verify. This is what you review — not a drawing.
gps-tracker-v0 rev 17 · 19 of 31 checks run PASS i2c.pullup_range sda:i2c0 fast_400k window 0.967 – 8.43 kΩ chosen 4.7 kΩ (i2c0_RSDA, i2c0_RSCL) C_b 42 pF = U1.GPIO8 2 + U3.SDI 10 + c_trace 30 source TI SLVA689 · NXP UM10204 FAIL connection.must_connect U2.RF_IN marked must_connect, nothing in the design touches it fix add_connection connect U2.RF_IN WARN power.rail_capability 3V3 peak load 540.004 mA = U1 500 + U2 40 + U3 0.004 source is 'external' — capability unspecified fix regulator with I_OUT ≥ 702.005 mA trust: contains_unverified_inputs — 40 unverified inputs 1 of 5 records here human-verified (1 of 465 in the catalog)
The rule library
Every rule cites its authority.
Formulas and constants live as data, per part and per mode, with the app note each one comes from. Add a rule and every design ever made is re-checked against it.
i2c Pull-up window · bus capacitance · addressesTI · NXP
power Rail budget · LDO headroom · decoupling · thermalper part
levels VOH/VIH and VOL/VIL joined per derived netrecord
uart · spi Role pairing · baud and clock vs device limitsrecord
strapping Strapping pins, with the consequence of loading onedatasheet
risk LiPo, mains, motor drive → stops for a humanHARD
Want to see a dossier on your own board?
Bring a design you already trust and we'll run it through. If the engine finds nothing, that's a useful result too — and if it finds something, you'll see exactly how it got there.