Adom Fields

@@ -1,162 +0,0 @@-{-  "name": "board",-  "title": "The board flow: parts placement to a qualified board",-  "scope": "Starts at the 3D models and parts placement on a board whose schematic, libraries and part choices already exist. Ends when the board is 100 percent routed, DRC-clean, poured, its copper measured, its current and thermal analyses passed, its nets and its 3D view walked through on camera, and the AI has delivered the video.",-  "steps": [-    {-      "name": "intake",-      "who": "ai",-      "does": "read the board and the spec, write the spec from the schematic if it is missing, plan",-      "record": "nothing on screen yet: the clip is the board opening on the test box (capture open) and the spec being read"-    },-    {-      "name": "models",-      "who": "ai",-      "does": "every footprint on the board has its 3D model resolved (kicad_model_check): fetch the vendor STEP, build one, or fix the path, so the board renders as it will be built; a bare footprint in the 3D view is a missing model",-      "binary": [-        "models"-      ],-      "record": "nothing to film: the model check's list and the fixes; the 3D walkthrough later is the proof"-    },-    {-      "name": "placement",-      "who": "ai",-      "does": "place the parts for routability, current and heat; the binary packs, checks courtyards and lands moves",-      "binary": [-        "place pack",-        "place check",-        "land moves"-      ],-      "record": "the parts landing ONE AT A TIME (land moves): each part is its own undo step, so the camera sees the board fill up part by part, never an empty board that is suddenly full"-    },-    {-      "name": "routing",-      "who": "binary",-      "does": "route to 100 percent with the spec's rules, gate with KiCad's DRC, land as undo steps; the AI takes it with take route=ai",-      "binary": [-        "route",-        "gate",-        "land route",-        "land vias"-      ],-      "record": "the traces drawn ONE AT A TIME (land route), then the vias: a net with several paths lands as several undo steps, so every trace is seen being drawn; the longest clip, the one viewers speed up"-    },-    {-      "name": "pours",-      "who": "binary",-      "does": "pour every net the spec names, keepouts along Kelvin taps, thermal and stitching vias, land, measure the copper kept",-      "binary": [-        "pour",-        "land pours",-        "measure"-      ],-      "record": "the pours filling in (land pours) and the copper readback; keep the DRC refusals in the clip, they are the story"-    },-    {-      "name": "current",-      "who": "binary",-      "does": "IPC-2221 on every loaded net, pour and via capacity, the same-layer rule; then the AI's own current density drawing and a walkthrough of the pours it judged",-      "binary": [-        "analyze current",-        "artifact --kind analysis-image",-        "tour nets --nets <the pour nets>"-      ],-      "record": "the analysis table on the board, then the AI's current density drawing (fullscreen in the video, the one place it leaves the editor), then each pour net lit and framed"-    },-    {-      "name": "thermal",-      "who": "binary",-      "does": "copper and vias at every hot tab against the rise budget; then the AI's own temperature rise drawing and a walkthrough of the pours it judged",-      "binary": [-        "analyze thermal",-        "artifact --kind analysis-image",-        "tour nets --nets <the pour nets>"-      ],-      "record": "the hot tabs and their copper, the AI's heat map fullscreen, then each pour net lit and framed; when it fails, the return to pours or placement is the clip worth keeping"-    },-    {-      "name": "fields",-      "who": "both",-      "does": "the fields on the board: adom-fields solves the current density of every loaded net, the heat flow in each copper layer with the vias, and the temperature over the board; the AI reads the issues and walks the board in the app on camera",-      "binary": [-        "adom-fields analyze",-        "adom-fields serve",-        "tour fields"-      ],-      "record": "the Adom Fields window: the board in 3D drifting gently through each beat, the heat on the top copper, each pour isolated on its own, the board turned over to the bottom, the temperature, then an issue or two; slow on purpose, the final video plays it at ten times speed"-    },-    {-      "name": "nets",-      "who": "binary",-      "does": "walk the key nets on camera: each loaded, wide or Kelvin net selected as a whole so the editor highlights its pours, tracks, vias and pads together, framed with Zoom to Selection",-      "binary": [-        "tour nets"-      ],-      "record": "the editor with one net lit at a time, framed; the markers say which net"-    },-    {-      "name": "3d",-      "who": "binary",-      "does": "the 3D walkthrough: the viewer opened from the editor, then fit, top, tilt, orbit, zoom in, swing, front, bottom, flip, top, fit, all by menu command, no mouse",-      "binary": [-        "tour 3d"-      ],-      "record": "the 3D Viewer window itself: the board turning, the components up close; full of motion, so the action cut keeps most of it"-    },-    {-      "name": "capture",-      "who": "binary",-      "does": "window recording with markers, so every engine's video lines up",-      "binary": [-        "capture open",-        "capture start",-        "capture mark",-        "capture stop"-      ],-      "record": "this step is the recorder itself: every step's clip is a window capture of the PCB editor, started when the step is declared"-    },-    {-      "name": "finish",-      "who": "both",-      "does": "finish refuses until everything is true; the AI cuts the video and delivers",-      "binary": [-        "finish",-        "deliver"-      ],-      "record": "the finish line passing (0 unconnected, 0 new errors), then the cut video and the delivery message"-    }-  ],-  "returns": "any step may send the AI back to any earlier step: step <name> --back --why \"...\"",-  "later": [-    {-      "name": "components",-      "does": "choose the parts from the requirements; SPICE may send the AI back here"-    },-    {-      "name": "libraries",-      "does": "symbols, footprints, 3D chips for every part"-    },-    {-      "name": "schematic",-      "does": "the schematic, and the spec that falls out of it"-    },-    {-      "name": "simulation",-      "does": "SPICE on the critical loops before the board exists"-    },-    {-      "name": "moleculize",-      "does": "machine pins so the board lives in the probing workcell"-    },-    {-      "name": "paste",-      "does": "solder paste jetting calculations"-    },-    {-      "name": "probe",-      "does": "how to probe the board when it comes off the InstaPCB process"-    }-  ],-  "clips": "every `step <name>` stops the previous step's clip and starts a new window recording tagged with the step, when the board is open on a test box; run.json captures[] carries one entry per clip with its step, start, stop and file, and deliver lists them; the final video is cut from these clips, one segment per step, so two engines' videos line up step for step; a return (step <name> --back --why) is a new visit and gets its own clip, tagged <step>-<visit> with the reason, so the rework is on camera and the final cut can show the loop",-  "screenshots": "every step visit gets two background screenshots of the editor window, at its start and at its end (shot-<step>-<visit>-start.png, shot-<step>-<visit>-end.png), logged as artifacts, so a run's own README has a picture for every step without anyone taking one"-}