Codex

@@ -35,11 +35,21 @@ This establishes explicit per-net/per-trace control. The crossover fixture uses  <video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4" style="width:100%;max-width:1100px"></video> -[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. **Full routing is still in progress.**+[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. This is the earlier partial run; the full comparison below completes connectivity.  -## Real Adom boards: next comparison+## Real Adom boards -A copy of [Adom's Pinch toolboard](https://wiki.adom.inc/adom/workcell-control-toolboard-pinch-v1) has been inspected: 162 footprints, 1,697 trace segments, 405 vias and 51 zones. Baseline KiCad DRC reports 29 errors and 483 warnings, with no missing-connection errors. Those findings are recorded before any changes. Independent rerouting has not yet been demonstrated on this board.+The public Teazzers comparison shows the reference, a stripped copy, independently calculated routing, and measured native KiCad results. Only publicly accessible designs are used in published recordings. A combined reel will follow approval of the individual runs. -The original stays intact. Each completed comparison will show the reference, a stripped copy, the routing process, and measured before/after results. Reference reconstruction will be labeled separately from independently calculated routes. A combined reel will be assembled after the individual runs are approved.+## Public Adom board: full routing comparison++<video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/04-public-adom-solenoid-full-routing.mp4" style="width:100%;max-width:1100px"></video>++[Download the full comparison](https://wiki.adom.inc/api/pages/adom/codex/files/videos/04-public-adom-solenoid-full-routing.mp4). The public [Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1) has 94 footprints and five output channels. The video tours the original human layout, removes all 484 segments and 58 vias from a copy, verifies zero remaining traces/vias, and shows Astra's independently calculated routing appearing through live KiCad IPC edits.++Astra runs in Adom Hydrogen and writes a custom geometry/A* planner. It reads the retained placement, pads, netlist and zone outlines; checks candidate paths against copper, pads, holes and board edges; and uses back copper and vias where needed. No Freerouting or other external autorouter is used, and the original trace geometry is not used to generate the replacement paths. Planning and iterative native DRC happened before this recorded execution. The tour and result play at normal speed; route creation plays at 3x, with the validation wait omitted.++The final saved live board contains **1,463 segments and 33 vias, with zero unconnected items** after native KiCad zone refill and DRC. Four pre-existing errors remain: two courtyard overlaps, one zone intersection and one starved thermal. There are no new clearance or crossing errors. The human reference reports three open items and 27 errors under the same KiCad checks; the stripped starting copy reports 118 open items and five errors. This demonstrates connectivity routing on this board. Current capacity, USB signal integrity and production electrical qualification remain engineering review tasks.++`kicad_routing_state` supplies the live revision and verifies copper counts. `kicad_remove_route` removes the original copper in one native Undo transaction. Then 132 `kicad_route_net` calls create the independently calculated segments and vias, guarded by `expectedRevision`. These calls use `validate:false` because the whole candidate was already checked; the actual saved live board is checked again using `kicad-cli pcb drc --refill-zones` through Adom Bridge `run_script`. `desktop_record_window_start` / `desktop_record_window_stop` capture one continuous KiCad-window take. The edited film is derived from that take, with caption timing and an edit manifest retained.

@@ -1,5 +1,5 @@ # Codex follow-up work  - [ ] Give every sub-readme a substantial visual pass: many real screenshots, annotated steps, demo stills, and consistent layouts. Deferred at John's request while the complicated KiCad board takes priority.-- [ ] Independently route a stripped copy of a verified public Adom board (Teazzers solenoid driver selected), validate against its published baseline, then record and caption the live KiCad comparison. Private development boards are excluded from showcase media.+- [x] Independently route a stripped copy of a verified public Adom board (Teazzers solenoid driver selected), validate against its published baseline, then record and caption the live KiCad comparison. Private development boards are excluded from showcase media. - [ ] Implement the Codex Desktop bridge and dock installation flow.

@@ -26,7 +26,7 @@ This is an explicit routing algorithm for a constructed fixture. It demonstrates - `desktop_record_window_start` / `desktop_record_window_stop`: native Adom Bridge recording of the KiCad window. - `pull_file` / `send_files`: moves recordings and PCB files between Windows and the Hydrogen container. -`kicad_remove_route` also exists on the development branch for targeted removal; it is not used to manufacture the appearance of routing in these clips. The complex fixture was created without copper before recording.+The first two fixtures started without copper. In the full public-board comparison below, `kicad_remove_route` visibly removes every original segment and via before independent routing begins.  ## Development source @@ -46,11 +46,23 @@ The third clip uses Adom's public Teazzers Solenoid Driver RP2040 v1.1. Both the  <video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4" style="width:100%;max-width:1100px"></video> -[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. **Full routing is still in progress.**+[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. This is the earlier partial run; the full comparison below completes connectivity.   The planner reads pads and nets from the stripped board, tries straight and diagonal/orthogonal paths, and checks other-net copper, pads, keepouts and board-edge clearance. The accepted batch was checked with native KiCad DRC before recording. No external autorouter generated these paths.  `kicad_routing_state` verifies the empty live board and obtains its revision. Sixty `kicad_route_net` calls with `expectedRevision` and `validate:false` commit the already checked paths. The last call saves the copy. Native `kicad-cli pcb drc --refill-zones` then checks the actual saved board through Adom Bridge `run_script`. Recording uses `desktop_record_window_start` and `desktop_record_window_stop`. Idle startup is trimmed, retained action is 3x, and the final frame is held. -The recorded board has 60 open items and five baseline errors: two courtyard overlaps, two starved thermals and one zone intersection. No new track-clearance or crossing errors were introduced. The published reference itself has three open items and 27 errors under KiCad 10; it is not described as perfect. Full routing and electrical review remain unfinished.+The recorded board has 60 open items and five baseline errors: two courtyard overlaps, two starved thermals and one zone intersection. No new track-clearance or crossing errors were introduced. The published reference itself has three open items and 27 errors under KiCad 10; it is not described as perfect. The full comparison below completes connectivity; electrical review remains unfinished.++## Public Adom board: full routing comparison++<video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/04-public-adom-solenoid-full-routing.mp4" style="width:100%;max-width:1100px"></video>++[Download the full comparison](https://wiki.adom.inc/api/pages/adom/codex/files/videos/04-public-adom-solenoid-full-routing.mp4). The public [Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1) has 94 footprints and five output channels. The video tours the original human layout, removes all 484 segments and 58 vias from a copy, verifies zero remaining traces/vias, and shows Astra's independently calculated routing appearing through live KiCad IPC edits.++Astra runs in Adom Hydrogen and writes a custom geometry/A* planner. It reads the retained placement, pads, netlist and zone outlines; checks candidate paths against copper, pads, holes and board edges; and uses back copper and vias where needed. No Freerouting or other external autorouter is used, and the original trace geometry is not used to generate the replacement paths. Planning and iterative native DRC happened before this recorded execution. The tour and result play at normal speed; route creation plays at 3x, with the validation wait omitted.++The final saved live board contains **1,463 segments and 33 vias, with zero unconnected items** after native KiCad zone refill and DRC. Four pre-existing errors remain: two courtyard overlaps, one zone intersection and one starved thermal. There are no new clearance or crossing errors. The human reference reports three open items and 27 errors under the same KiCad checks; the stripped starting copy reports 118 open items and five errors. This demonstrates connectivity routing on this board. Current capacity, USB signal integrity and production electrical qualification remain engineering review tasks.++`kicad_routing_state` supplies the live revision and verifies copper counts. `kicad_remove_route` removes the original copper in one native Undo transaction. Then 132 `kicad_route_net` calls create the independently calculated segments and vias, guarded by `expectedRevision`. These calls use `validate:false` because the whole candidate was already checked; the actual saved live board is checked again using `kicad-cli pcb drc --refill-zones` through Adom Bridge `run_script`. `desktop_record_window_start` / `desktop_record_window_stop` capture one continuous KiCad-window take. The edited film is derived from that take, with caption timing and an edit manifest retained.

@@ -35,3 +35,9 @@ Validate the output with a full decode and sampled sequential frames, not only a ## Deliver where the user watches  Use pull_file to bring the host recording into the container for editing. Use send_files to deliver the finished MP4 back to the intended host. If asked to open it, use host shell_execute/file association and verify the player window. Read codex-adom-operation-results for approval and result handling; a container path or xdg-open does not open the user's Windows player.++## Continuous comparison evidence++Record the reference tour, complete trace/via removal, zero-copper state and replacement route commits in one take when demonstrating independent rerouting. Replay only the final accepted candidate geometry; historical planning logs can contain discarded routes. Verify live counts and native DRC on the actual saved replay.++Window-recorder encoded duration can differ from wall-clock call timing. Treat logs as approximate edit guides: inspect frames at every cut, especially the final additions, and retain all route commits. A global time scale alone can cut off the last vias. Keep the raw take and document manually verified cut boundaries.

⋯ 1 unchanged line ⋯