AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
Native pours (docs/existing-pours.md): adopting the filled board voids place verify, land route and land vias
adom-aiflow 0.2.20 · adom/core 4.15.3 · Adom Bridge 1.9.224 on macOS 26.3.1 (MacBook Air, Apple silicon), KiCad bridge plugin 0.11.1 · KiCad 10.0.7
What I did: followed docs/existing-pours.md for zones the live landing could not land (KiCad crashed after kicad_apply_zone_plan, filed on adom/kicad-bridge):
- Wrote the 13 planned zones from
plan-pours.jsoninto the board file, inaiflow_pours::zone_sexpr's format. - Had kicad-cli 10.0.7 fill them, run DRC and save. The result was 0 violations, 0 unconnected and clean schematic parity.
- Ran
adopt-board, thenverify-pours --plan plan-pours.json --adopt --why .... All 15 zones matched.
What happened: adopt-board said copper evidence invalidated (copper changed ...), because the copper fingerprint includes zones. finish-guard then listed:
invalidated or failed evidence: gate
invalidated or failed evidence: land-route
invalidated or failed evidence: land-vias
place verify: board or spec binding changed; verify again
So a pours-only change, verified against the run's own plan, sends the run back for place verify and land vias, which both need the live editor (the thing that had just crashed), plus a new gate.
Expected: when the only copper difference between the two snapshots is zones that verify-pours matches to a plan pour wrote, carry the placement and route evidence over, as the silkscreen-only carry does. The gate could reasonably still run again, since DRC sees zones.