AI Flow

@@ -14,7 +14,7 @@ members = [ ]  [workspace.package]-version = "0.1.49"+version = "0.1.50" edition = "2021" license = "MIT" repository = "https://wiki.adom.inc/adom/adom-aiflow"

⋯ 1 unchanged line ⋯

@@ -0,0 +1,11 @@+# AI Flow 0.1.50++The Fusion lane: AI Flow runs a board that lives in Autodesk Fusion with the same steps, gates and ledger as a KiCad board. The router, the pour planner and the KiCad DRC gate work offline as before; every live step lands in Fusion through the Fusion bridge (1.11.30 or later), one edit at a time, read back from Fusion's own export. See [the Fusion lane](fusion-lane.md).++- `start --board <board>.brd --remote-board fusion:<document>`: the Fusion board is converted for the offline steps (parts, pads, nets, outline, tracks, vias, pours with Fusion's fill). Pads and vias are sized from the board's restring rules, as Fusion sizes them.+- Live steps in Fusion: `place land`, `land route`, `land vias`, `land pours`, `measure`, and Autodesk's own DRC in `finish`. On a Fusion run, `route` plans on the live board.+- `analyze` and `finish` judge the board as it is in Fusion now (`board-live.brd`), and adom-fields solves that file directly.+- New `unroute --net <net>` (both lanes): takes a net's tracks and vias up so it can be routed again after an analysis.+- `land route` skips a trace only when the board's copy is at least as wide as planned, so a widened net lands again.+- Molecule parts are recognised whatever their case (Fusion upper-cases package names).+- Proven on the 12 V to 5 V buck molecule built in Fusion: two refinements from the field solve (an SW patch cut off by a GND track, a VIN via ring), then a clean finish.

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.49",+  "version": "0.1.50",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad today; Altium, Fusion and Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.49",+  "version": "0.1.50",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad today; Altium, Fusion and Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",