EDA Bridge Standard: one way for an AI to drive every PCB tool

@@ -42,7 +42,8 @@ A verb one bridge gains should become every bridge's to-do: that is what this pa and its companions go in as plain JSON, findings and plans come out, and nothing calls a bridge or a tool. A bridge links the crate (vendored at a tagged standard version, since Cargo cannot fetch from the wiki) or runs the command, and answers each check under its own prefix. It now answers `copper_balance`, `return_path`, `fab_check`, `impedance` and-`current_capacity`, moved over from the Altium bridge and giving the same answers on Altium's test boards. Its+`current_capacity`, moved over from the Altium bridge and giving the same answers on Altium's test boards. It also+carries board-file writers (`export_gencad`, `export_dxf`, `import_svg`) for a bridge whose tool has no native exporter. Its conformance tests read a bridge's saved replies from `ADOM_EDA_FIXTURES`; fixtures live on each bridge's own page (Altium's: [adom/altium-bridge](https://wiki.adom.inc/adom/altium-bridge) `fixtures/`). @@ -155,6 +156,8 @@ Decisions so far (proposals from the KiCad and Fusion bridges, 2026-10-27; issue  ## Status +Version 0.5.0: the engine (0.2.0) carries shared board-file writers, GenCAD, DXF per layer and SVG to regions, from+altium-lane's writers (#16, PR #1); its DXF draws the copper actually poured when given `pours`. Version 0.4.5: the engine (0.1.4) lists each layer once in `current_capacity`'s `poursOn` (kicad-lane #15); KiCad now answers four checks from the engine too. Version 0.4.4: the engine (0.1.3) counts only copper-to-copper clearance rules: a rule naming the edge, mask, silk,

@@ -1,8 +1,8 @@ [package] name = "adom-eda-checks"-version = "0.1.4"+version = "0.2.0" edition = "2021"-description = "The EDA Bridge Standard's checks, computed from the board model JSON: no bridge calls, no tool."+description = "The EDA Bridge Standard's checks and board-file writers, computed from the board model JSON: no bridge calls, no tool." license = "MIT"  [lib]@@ -14,6 +14,9 @@ path = "src/main.rs"  [dependencies] serde_json = "1"+# the SVG parser behind writers::svgart (pure Rust)+roxmltree = "0.20"+svgtypes = "0.15"  [profile.release] opt-level = 3

@@ -1,4 +1,4 @@-# adom-eda-checks: the shared checks engine+# adom-eda-checks: the shared checks engine and board-file writers  The checks tier of the EDA Bridge Standard, computed from the board model and its companions as plain JSON. It makes no bridge calls, runs no tool and does no I/O. A bridge links the crate (the Altium, KiCad and Fusion bridges are all@@ -20,6 +20,18 @@ boards the engine gives the same answers the Altium bridge 0.2.76 gives. The other checks-tier verbs (assembly, 3D heights, placement, schematic review, pair routing, length tuning, designators, via fences, panels, the board report) come over from the Altium bridge a module at a time. +## Writers++For a bridge whose tool has no native exporter (`writers`, from altium-lane, #16). They stay native-tier verbs in the+standard: a bridge whose tool can write the file keeps its own exporter. No I/O: each returns the file text or the+regions, with `writtenFrom`, and the bridge writes the file or places the regions.++| Verb | Reads | What it answers |+|---|---|---|+| `export_gencad` | board | GenCAD 1.4 text, in inches: outline, pads and padstacks, shapes, components (a bottom part `MIRRORX FLIP`, as KiCad writes it), devices, signals, routes |+| `export_dxf` | board, pours? | one DXF (R12) per layer in `args.layers`: Edge.Cuts as lines and arcs or one closed polyline (`contours`), copper as tracks, arcs, pads, vias and pours. With `pours` a copper layer shows the copper actually poured; without, `poursAsDrawn` names the layers that show the pour as drawn |+| `import_svg` | svg (text) | `regions` in board mm (y up) for a layer: each shape with its holes as one contour reaching the holes through zero-width slits |+ ## Input  Every check takes one JSON object:@@ -61,6 +73,8 @@ As a command: adom-eda-checks list adom-eda-checks return_path --board board.json --stack stack.json --pours pours.json --args '{"resolutionMm": 0.1}' adom-eda-checks fab_check bundle.json        # or - for stdin+adom-eda-checks export_dxf --board board.json --pours pours.json --args '{"layers": ["Edge.Cuts", "F.Cu"]}'+adom-eda-checks import_svg --svg logo.svg --args '{"at": [10, 10], "widthMm": 20, "layer": "F.SilkS"}' ```  Replies keep the standard envelope (`success`, `errorCode`, `error`, `_hint`) and name verbs without a prefix

@@ -1,6 +1,7 @@ //! adom-eda-checks: the EDA Bridge Standard's checks tier, computed from the board model and its companions as plain-//! JSON. No bridge calls, no tool, no I/O: a bridge links this crate (or runs the `adom-eda-checks` command) and-//! answers the check under its own prefix (`kicad_return_path`). Replies keep the standard envelope (`success`,+//! JSON, plus board-file writers (`writers`: GenCAD, DXF, SVG to regions) for a bridge whose tool has no native+//! exporter. No bridge calls, no tool, no I/O: a bridge links this crate (or runs the `adom-eda-checks` command) and+//! answers the verb under its own prefix (`kicad_return_path`). Replies keep the standard envelope (`success`, //! `errorCode`, `error`, `_hint`) and name verbs without a prefix. //! //! Every check takes one input bundle, `{board, stack?, pours?, rules?, silk?, fab?, bodies?, sheetParts?, netlist?, args?}` (see `input`).@@ -12,18 +13,20 @@ pub mod fab; pub mod geom; pub mod impedance; pub mod input;+pub mod writers;  /// The checks this build answers, by standard verb name. pub const CHECKS: &[&str] = &["copper_balance", "current_capacity", "fab_check", "impedance", "return_path"]; -/// Run one check by its standard name.+/// Run one check or writer by its standard name. pub fn run(check: &str, input: &Value) -> Value {+    if let Some(out) = writers::run(check, input) { return out; }     match check {         "copper_balance" => coppermap::copper_balance(input),         "current_capacity" => current::current_capacity(input),         "fab_check" => fab::fab_check(input),         "impedance" => impedance::impedance(input),         "return_path" => coppermap::return_path(input),-        _ => input::refuse("not_supported", &format!("{check} is not a check this engine answers (it answers {})", CHECKS.join(", "))),+        _ => input::refuse("not_supported", &format!("{check} is not a verb this engine answers (checks: {}; writers: {})", CHECKS.join(", "), writers::WRITERS.join(", "))),     } }

@@ -1,5 +1,6 @@ //! adom-eda-checks <check> [bundle.json | -] //! adom-eda-checks <check> --board b.json [--stack s.json] [--pours p.json] [--args '{...}']+//! adom-eda-checks import_svg --svg art.svg --args '{"at": [10, 10], "widthMm": 20}' //! Prints the check's reply as JSON. `adom-eda-checks list` names the checks. use serde_json::{json, Value}; use std::io::Read;@@ -27,6 +28,8 @@ fn bundle(rest: &[String]) -> Result<Value, String> {                 b[key] = read(val)?;             }             "--args" => b["args"] = serde_json::from_str(val).map_err(|e| format!("--args: {e}"))?,+            // SVG artwork is text, not JSON+            "--svg" => b["svg"] = Value::String(std::fs::read_to_string(val).map_err(|e| format!("{val}: {e}"))?),             _ => return Err(format!("unknown flag {flag}")),         }     }@@ -36,8 +39,8 @@ fn bundle(rest: &[String]) -> Result<Value, String> { fn main() {     let argv: Vec<String> = std::env::args().skip(1).collect();     let out = match argv.first().map(String::as_str) {-        None | Some("-h") | Some("--help") => json!({"success": true, "usage": "adom-eda-checks <check> [bundle.json | -] | <check> --board b.json [--stack s.json] [--pours p.json] [--args '{...}']", "checks": adom_eda_checks::CHECKS}),-        Some("list") => json!({"success": true, "checks": adom_eda_checks::CHECKS}),+        None | Some("-h") | Some("--help") => json!({"success": true, "usage": "adom-eda-checks <check> [bundle.json | -] | <check> --board b.json [--stack s.json] [--pours p.json] [--args '{...}']", "checks": adom_eda_checks::CHECKS, "writers": adom_eda_checks::writers::WRITERS}),+        Some("list") => json!({"success": true, "checks": adom_eda_checks::CHECKS, "writers": adom_eda_checks::writers::WRITERS}),         Some(check) => match bundle(&argv[1..]) {             Ok(b) => adom_eda_checks::run(check, &b),             Err(e) => json!({"success": false, "errorCode": "bad_args", "error": e, "_hint": "Pass one bundle file {board, stack, pours, args}, or --board, --stack, --pours and --args."}),

@@ -1,6 +1,6 @@ {   "slug": "eda-bridge-standard",-  "version": "0.4.5",+  "version": "0.5.0",   "type": "skill",   "title": "EDA Bridge Standard: one way for an AI to drive every PCB tool",   "description": "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.",

@@ -1,5 +1,5 @@ {- "standard": "0.4.5",+ "standard": "0.5.0",  "reference": {   "bridge": "altium",   "version": "0.2.78"

@@ -1,5 +1,5 @@ {- "standard": "0.4.5",+ "standard": "0.5.0",  "reference": {   "bridge": "altium",   "version": "0.2.78"