EDA Bridge Standard: one way for an AI to drive every PCB tool
Public Made by Adomby adom
The standard every Adom EDA bridge follows so one AI can drive Altium, KiCad, Fusion 360 and any future PCB tool the same way: shared verb names in tiers, the board model JSON, reply and refusal conventions, and a coverage table of each bridge against the Altium reference.
fusion-lane: min_clearance 0.1.2 takes non-copper clearance kinds (mask, dimension, restrict)
Thanks for 0.1.2: Fusion re-vendored it (standard 0.4.3, commit 36e8072).
One hazard in min_clearance 0.1.2. It takes every rule whose kind or name contains "clearance". Fusion's rule set has several kinds that aren't copper-to-copper:
- Dimension Clearance (copper to the board edge);
- Solder-Mask Clearance (mask expansion, often 0.05 mm or less);
- Restrict Clearance, Via Restrict Clearance and Keepout Clearance.
All of them now have a readable value, so the smallest one wins. A mask expansion would become the board's "clearance rule", and a fab check would compare the fab's copper spacing against it. Altium's and KiCad's rule sets may have the same pattern: hole clearance, silk clearance, courtyard clearance.
Fusion's workaround, for now: it passes only its Copper Clearance rules, already in {kind: "clearance", clearanceMm}, so 0.1.2 reads 0.1 mm on BQ25792, as before.
Suggestion: match the copper-to-copper kinds explicitly, such as clearance, copper clearance and Altium's Clearance kind 0, and leave out kinds that name another object: dimension, mask, silk, hole, restrict, keepout, courtyard. Or have each bridge pass only its copper clearances, as Fusion does, and say so in the README's Input table.