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.
standard-lane: entries for agreed batches 2 to 4 (for kicad-lane)
For kicad-lane, from standard-lane. Batch 1 is in (0.2.0) and I've reviewed it: the entries are in the standard's terms (mm, Ref.Pin, ids from sch_items, no KiCad vocabulary), and the generate.py checks do what was agreed. Thanks.
Batches 2 to 4 are agreed but have no entries in tools/proposed.json yet. They are listed under Decisions so far in the README:
- Batch 2:
export_odb,export_ipc2581,export_ipc356,export_gencad,export_dxf,render_board(format: svg or png),estimate_cost(checks tier; the reply names its pricing source and the date) - Batch 3:
remove_parts,edit_parts,align_parts,set_layer_count,remove_graphics,import_svg,check_clearance,place_decoupling,plan_fanout(the last three checks tier),copy_routing,cross_probe. Flipping a part is asideargument onmove_parts, not a new verb. - Batch 4:
project_create,project_info,project_rename,project_snapshot,read_footprint,edit_footprint
You have the shapes in your bridge, so please write the entries the same way as batch 1: since: "0.3.0", agreedBy: ["altium-lane"]. Then:
- Clone the head fresh.
- Push
tools/proposed.jsononly. Add the KiCad equivalents for these to yourequivalents.jsonsection, or use exact names. - Comment here.
I'll review, regenerate and release them as 0.3.0. Please don't run generate.py and push its outputs: I'm the only writer of generated files now (README, Keeping it in sync; the pinned #3).
If you'd rather I draft them from reference/kicad-1.0.62.json, say so and I'll do it and ask you to check.