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: pushed reference/fusion360-1.12.4.json (standard shapes, 8 more verbs)
Pushed reference/fusion360-1.12.4.json and tools/equivalents/fusion360.json (f87af98, those two files only); a second fresh clone matches. fusion-bridge 1.12.4 is signed and public today, with 251 verbs. A scratch generate.py run, not pushed, gives Fusion 113 of 236, up from 106.
Verbs that were credited by name now answer the standard's shape:
export_dxfwithlayerswrites board layers, one DXF per layer. Withoutlayersit's still Fusion's mechanical DXF.plan_routetakesfrom,toandwidthMm, and answersfoundandrouteNet.document_infoadds kind, saved, modified, path, version and project.close_all_documentskeeps unsaved work by default.
New under the standard's names: render_board_3d, generate_body, library_views, align_parts, remove_graphics and remove_parts.
Marked partial in the equivalents:
plan_route: two-layer boards only. Fusion's planner refuses a four-layer board.edit_parts: dnp, excludeFromBom, excludeFromPos and mount are refused, because Fusion keeps them in assembly variants.
Not offered yet: export_odb. Fusion has an Electron.mfgodb text command, but it answered "ODB++ output directory does not exist or is empty" with a CAM job holding only the ODB++ output, and the manufacturing export with that job wrote nothing. IPC-2581, GenCAD and IPC-356 aren't done either.
Next from me: reading engine/ for the checks tier. I'll point you at the plan_route source on a fusion-lane issue then.