Codex

@@ -54,11 +54,39 @@ The new recording is not ready yet, so no video is embedded for this stage. Once  Read the [electrical-routing worked example](ELECTRICAL-ROUTING.md) for the decisions, failed approaches and reusable lessons being built into the shared Codex skillpack. The diagram shows calculated zones/traces and omits footprints; coverage excludes additional pad/trace copper and is not a laser-time estimate. -## How Adom makes the live work visible+## The Bridge calls behind the videos -Astra runs in the Hydrogen container. `kicad_routing_state` reads the board and revision; `kicad_route_net` commits calculated traces/vias with `expectedRevision`; `kicad_remove_route` clears copper from a copy. Native KiCad refill/DRC checks the saved result through the validation surface or a background `run_script` call, depending on the operation. `desktop_record_window_start` and `desktop_record_window_stop` capture KiCad, and `pull_file`/`send_files` move the media between the desktop and container.+Adom Bridges give the AI a practical connection to the user's engineering tools. Astra calculates the paths in Adom Hydrogen; KiCad Bridge reads the real PCB and commits native copper edits while the KiCad window redraws. Adom Bridge also connects the desktop recording, background validation and file-transfer steps, so the same workflow can produce both an editable board and a shareable explanation. -The routing bridge remains on its development branch, with [draft review #2](https://wiki.adom.inc/adom/kicad-bridge/prs/2); these films do not claim the separate Adom Bridge pin-protection fix is deployed. See [implementation, validation and narration details](ROUTING-IMPLEMENTATION.md), [the shared routing guide](ELECTRICAL-ROUTING.md), and [Codex setup](BOOTSTRAP.md).+### KiCad Bridge: inspect, preview, route and verify++| Verb | What it does in these demonstrations | What the viewer sees |+| --- | --- | --- |+| `kicad_routing_state` | Reads pads, nets, existing tracks/vias, connectivity and the live board revision. Provides the state used to plan edits and check the result. | The AI works from the actual PCB; after removal, the recorded full run verifies zero remaining traces/vias. |+| `kicad_route_net` with `dryRun:true` | Previews a proposed complete net and runs a DRC preview without committing it. Used in the first two fixture demonstrations before live item creation. | Paths can be checked before they appear in the editor. |+| `kicad_remove_route` | Removes the original routing from the demonstration copy in one native Undo transaction. | The human-routed board visibly becomes an unrouted starting point. |+| `kicad_route_net` | Creates calculated segments and vias through KiCad IPC, using `expectedRevision` to reject stale edits. The fixtures use individual-item edits; the full public-board run uses 132 route calls to commit batches. | Real copper appears in KiCad, including layer changes and branches. The resulting board remains editable. |+| `kicad_routing_validate` | Runs native KiCad DRC and reports errors, warnings and unconnected items. Used for the completed fixture checks. | The result is supported by CAD checks, not only by a finished-looking drawing. |++The sequence is **read state → calculate paths → preview/check → commit against the expected revision → validate the saved result**. The full public-board film adds the original-board tour and visible removal before the new routing begins.++The recorded live commits use `validate:false` after their candidate geometry has already been checked; this avoids repeating a full DRC for every visible edit. The saved board is checked again afterwards. Revision checking prevents an edit based on stale board state; it does not replace electrical or DRC validation.++### Adom Bridge: connect the desktop to the finished film++| Verb | Role in the workflow |+| --- | --- |+| `desktop_record_window_start` | Starts recording the actual KiCad window before the demonstration. |+| `desktop_record_window_stop` | Finishes the continuous take and returns the recording artifact. |+| `run_script` | Runs native KiCad CLI checks in the Windows background. The public-board runs use `kicad-cli pcb drc --refill-zones` to validate the saved board and its refilled copper. Current pour-development experiments also use native KiCad Python through this surface. |+| `pull_file` | Brings the desktop recording and validation reports into the Hydrogen container for inspection and editing. |+| `send_files` | Delivers board files and finished captioned/narrated videos back to the selected desktop. |++Trimming, 3× playback and captions are video-processing steps in the container; Adom TTS supplies the narrated edition. They are not KiCad routing verbs. The recorded board changes themselves are genuine native edits. Planning and iterative checks occur before the filmed replay and are disclosed in the videos.++This division of work is the value of the ecosystem: the AI can reason about the design, operate the desktop application through explicit commands, inspect machine-readable results, and show the user what happened. The bridge exposes the controls; the AI-authored planner supplies the route geometry. No external autorouter generated the replacement paths in these films.++The per-net routing verbs shown here are in the KiCad Bridge development build, with [draft review #2](https://wiki.adom.inc/adom/kicad-bridge/prs/2). Discover the connected bridge's live command catalog before reuse; installing the Codex skills alone does not install these development verbs. These films do not claim that the separate Adom Bridge development-pin protection fix is deployed. See [implementation and recording evidence](https://wiki.adom.inc/adom/codex/files/docs/ROUTING-IMPLEMENTATION.md).  ## The methods ship to every user who installs Codex for Adom