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.
Placement gate needs exact courtyards and preserved project rules for compact molecules
Versions: AI Flow installed binary 0.1.25; service-kicad native KiCad 10.0.2; Linux CLI; STM32F407ZGT6 molecule, 30.4mm outline.
place check rejects a physically legal placement in two independent ways:
- It uses bounding boxes for concave LQFP courtyards and circular machine contacts. Its overlap list reports 8 overlaps that native KiCad exact courtyard DRC does not report.
- It imposes a hardcoded 0.5mm courtyard-to-edge inset, even though our selected contract is 0.30mm copper to edge, with courtyard inside the outline. It reports 10 parts outside despite their courtyards remaining within the outline.
The offline DRC upload also loses the .kicad_pro and checks a default 0.5mm copper edge rule. The resulting 6 copper_edge_clearance errors explicitly say required0.5000, actual0.3875–0.4875mm. Running the exact same candidate with its project and the declared0.30mm edge rule produces ZERO errors (106 unrouted, expected at placement). Silkscreen/library warnings are retained for later correction.
Please preserve project/custom rules across start/copies/gate and apply exact transformed courtyard geometry. Separate component/body/courtyard edge policy from copper edge policy. pack may conservatively use boxes for speed but check must not promote those approximate overlaps to hard errors. Keep explicit molecule access reservations separate from physical courtyards.
An explicit adopt-board --board ... --evidence ... for AI-owned stages would also help: currently custom placement can be declared but there is no documented way to set its independently checked board as the next router input without editing run.json. This trial will record any necessary adapter in the ledger and retain the independent native proof; no rule exclusions or increased inherited-error baseline.