Codex

@@ -82,6 +82,29 @@ The 0.1 mm channel width is the user's manufacturing capability, not an electric  [Download the copper-retention video](https://wiki.adom.inc/api/pages/adom/codex/files/videos/fusion/09-bq25792-copper-retention-narrated.mp4) +## 10. Cleaner routes and connected thermal copper — Fusion on CRR++The next experiment applies horizontal/vertical runs with 45-degree transitions and reserves useful heat-spreading copper before ordinary routing. Astra inspects the five MOSFET footprints and their 35 thermal holes, assigns the bottom regions to their actual VAC1, VBUS, VAC2 and VBAT nets, and adds ground-via paths for the charger and linear regulator. The existing four-layer stackup and original component placement are preserved.++The new take runs on ConfRoomROG (CRR), preserving its pinned Fusion bridge. Astra precomputes and checks the route plan, then Adom Bridge draws each accepted native line and via, verifies copper after each batch, fills four priority thermal regions and four PGND pours, and checks the actual replay. The existing Adom activity palette shows public progress summaries, composited beside the canvas from its own native window recording. The edited video uses 3x action, removed waits, inspection holds and Andrew Neural narration through Adom TTS.++The saved live replay contains **576 trace segments, 89 vias and eight pours**. The exported segment-angle audit finds **zero exceptions** to horizontal/vertical/45-degree directions (0.02° tolerance). Autodesk reports **zero airwires, zero warnings and zero new errors**; the same inherited clearance error remains. Estimated total retained copper is **82.2%** across four layers.++| Device / thermal net | Previous connected bottom copper | New connected bottom copper |+| --- | ---: | ---: |+| Q1 / VAC1 | 11.3 mm² | 29.5 mm² |+| Q2 and Q4 / shared VBUS region | 5.3 mm² at each device | 45.0 mm² shared |+| Q3 / VAC2 | 5.3 mm² | 30.3 mm² |+| Q5 / VBAT | 13.0 mm² | 25.8 mm² |++The comparison retains the same diagnostic rule profile described above: only the inherited all-object same-net track-spacing rule is disabled on disposable copies. Different-net clearance rules remain active. Connected projected copper area is an estimate, not a measured temperature improvement; Q2 and Q4 share one VBUS region and must not be double-counted. Actual load currents, power-path bottlenecks, switching layout, sensitive signals and thermal performance still need qualification. Floating retained copper does not count as connected heatsinking.++<video width="100%" controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/fusion/10-bq25792-thermal-45-narrated.mp4"></video>++[Download the thermal-routing video](https://wiki.adom.inc/api/pages/adom/codex/files/videos/fusion/10-bq25792-thermal-45-narrated.mp4)++The package skills now explain how to constrain both planning and cleanup to the chosen bend directions, inventory thermal pads and vias, reserve copper on the correct nets, and check connected area after native refill. See the bundled `codex-adom-electrical-routing` and `codex-adom-routing-video` skills. Manufacturer guidance remains board-specific: [BQ25792 layout](https://www.ti.com/lit/gpn/BQ25792), [CSD17581Q3A MOSFET](https://www.ti.com/lit/ds/symlink/csd17581q3a.pdf), and [TLV760 regulator](https://www.ti.com/lit/gpn/tlv760).+ ## The Adom Bridge calls behind the videos  Astra calculates geometry; Adom Bridge makes it happen in the native editor and returns evidence of what Fusion actually created. That combination is what makes the progression possible: the same automation connection can inspect a board, place copper, run Autodesk checks, record the application and deliver the finished video. These are real CAD objects and native window captures.

@@ -34,5 +34,9 @@   {     "file": "videos/fusion/09-bq25792-copper-retention-narrated.mp4",     "bytes": 17700087+  },+  {+    "file": "videos/fusion/10-bq25792-thermal-45-narrated.mp4",+    "bytes": 14600169   }-]\ No newline at end of file+]

@@ -4,7 +4,7 @@   "type": "app",   "title": "Codex",   "brief": "Codex in Adom Hydrogen: ecosystem setup, dock dashboard and live engineering demos.",-  "version": "0.1.8",+  "version": "0.1.9",   "description": "Codex in Adom Hydrogen with reusable CAD routing, electrical review, copper-ablation and narrated video skills, plus verified KiCad and Fusion demo progressions.",   "org": "adom",   "needs_sudo": false,

@@ -22,7 +22,7 @@ Classify nets before optimizing geometry:  # Routing appearance and thermal planning -Default to horizontal and vertical runs joined by 45-degree transitions. Optimize the number of bends and vias as well as route length; do not leave arbitrary-angle links or search-grid stair steps just because they pass DRC. Preserve intentional pad escapes, component rotations, differential spacing and electrical constraints. Audit segment angles numerically, then inspect the actual board visually. Report any exceptions rather than claiming every segment is orthogonal/45-degree. Smooth tangent arcs are an optional alternative when the native CAD API, clearances and fabrication process support them; use actual native arcs and verify their radius and tangency rather than approximating curves with many tiny segments.+Default to horizontal and vertical runs joined by 45-degree transitions. Optimize the number of bends and vias as well as route length; do not leave arbitrary-angle links or search-grid stair steps just because they pass DRC. Preserve intentional pad escapes, component rotations, differential spacing and electrical constraints. Constrain planner escapes and post-processing too: an unrestricted line-of-sight shortcut can undo an eight-direction search. Remove redundant collinear vertices, and recheck each shortcut against fixed and newly generated copper. Audit segment angles numerically, then inspect the actual board visually. Report any exceptions rather than claiming every segment is orthogonal/45-degree. Smooth tangent arcs are an optional alternative when the native CAD API, clearances and fabrication process support them; use actual native arcs and verify their radius and tangency rather than approximating curves with many tiny segments.  Before allocating routes and pours, inventory heat-producing and high-current components, exposed pads, heatsink tabs, existing thermal-via arrays and thermal features embedded in footprints. Determine each thermal pad's electrical net from the schematic and manufacturer data; do not assume an exposed pad or heatsink tab is ground. Estimate relevant conduction, switching and regulator losses under the load contract and document uncertainty. @@ -42,7 +42,7 @@ Measure retained copper from refilled polygons, tracks and pads, with unions to  # Acceptance and narration -Use native KiCad zone refill and DRC on each accepted candidate. Check schematic/PCB parity and ERC separately, classify inherited issues, and keep evidence for remaining manufacturing, thermal and signal-integrity decisions. Do not suppress real rules to obtain a clean report. Confirm the same result on the actual live replay.+Use the native CAD application’s copper refill and DRC on each accepted candidate (KiCad or Fusion as applicable). Check schematic/PCB parity and ERC separately, classify inherited issues, and keep evidence for remaining manufacturing, thermal and signal-integrity decisions. Do not suppress real rules to obtain a clean report. Confirm the same result on the actual live replay.  For a demo, expose concrete decisions: the load budget, chosen power paths, compact switching loop, paired USB route, ground continuity, copper-retention measurements and final tests. Explain what was precomputed. Use codex-adom-routing-video and Adom TTS for the recorded/narrated artifact. A routing demonstration or simulation is not a substitute for required physical load, transient and USB testing. 

@@ -49,3 +49,9 @@ For voiceover requests, read the installed adom-tts skill and use `adom-tts say` ## Wiki embeds that fit the reading column  Use `<video width="100%" controls playsinline preload="metadata" src="..."></video>` for wiki Markdown embeds. The wiki sanitizer strips inline `style`, so `style="width:100%;max-width:1100px"` alone leaves intrinsic 1920-pixel video widths and horizontal overflow. Verify the published DOM: video width should equal its Markdown parent width, and document scroll width should not exceed the viewport. For readable sub-readmes open `/adom/codex/files/docs/NAME.md`; `/render/docs/NAME.md` may serve raw Markdown. Use full attachment URLs for images in nested readmes when relative paths resolve from the page root. Check actual media readiness and broken images in Pup.++## Native status palettes and replay preparation++Reuse the application's existing Bridge activity palette for public progress summaries. Serialize payloads with JSON and embed script values with a language-safe representation; compile generated Python locally before sending it. A native HTML update may return an empty reply despite visibly updating: verify the palette image rather than treating the reply string as an acknowledgement contract. Capture the palette separately when native window capture excludes child or floating windows, align the recordings from actual frames, and label the resulting composite.++For each replay, verify the exact isolated document and expected copper prefix before drawing. After any failure, inspect the current prefix before deciding whether to resume or make a fresh copy. Preserve failed takes and recording IDs; never overwrite them with a retry.

⋯ 1 unchanged line ⋯