Adom Wiki Skill Pack

@@ -15,7 +15,7 @@ description: >-   kicad altium orcad fusion library, parametric specs, mouser digikey price stock,   provenance, prove the data, datasheet page citation, embed symbol footprint   viewer, open chip in tool, reusable component README, generic component page,-  component hero, chip hero, GLB orientation, Z-up, Y-up, chip standing on edge.+  component hero, chip hero, GLB orientation, Z-up, Y-up, chip standing on edge. ordering variants, several part numbers one page, which variant do we stock, basic part reel, datasheet callout, hero note, pads look wrong, copper fill, verified by, verification log, trust mark, adom-verified, datasheet-built 3D model, overlay proof. ---  Parent skill: **adom-wiki-skillpack**@@ -648,6 +648,89 @@ CAD tab and the exact SamacSys entry with its part id), cite a page for every pi include the cited pages as images, compare the footprint pad-by-pad against the vendor land pattern and publish the comparison, and record every 3D transform. Keep session and machine notes out of it. +## Ordering variants: one page per package, and be honest about what Adom stocks++When a maker sells several orderable parts in the same package with the same land pattern (Worldsemi's+WS2812B-2020, -V6, -V7, WS2812C-2020-V6, WS2812E-2020; Bourns' CR0402-FX values; Samsung CL21 values),+make ONE page for the package, not one per part: separate pages are wiki bloat. Ray's `ray/ws2812b` and+`adom/ws2812b-2020` are the worked examples.++- Add an **Ordering variants** table: part number, the specs that differ (current, brightness, voltage,+  logic threshold, temperature, wavelength), a note on when to pick it, and a link to that part's own+  datasheet. State that the footprint, symbol and pinout fit every row, and why (same drawing, same land+  pattern, checked sheet by sheet).+- **Check each variant's datasheet before claiming it fits.** Compare the package drawing and the PCB land+  pattern of every revision; makers reuse drawings but change electrical figures between revisions (the+  WS2812B-2020 V1.0 sheet says 16 mA, V1.2 on say 12 mA). Cite the revision your specs come from.+- **An Adom Basic Part page names the exact part on the reel.** Read the reel label or the order record and+  pnp-inventory; if nothing is on hand, say so in the intro and the Ordering table ("listed as a Basic Part,+  no reel on hand yet") instead of implying stock. When a reel arrives, mark that variant stocked (page and+  verification log) and make the 3D model, photo and specs follow it.+- Where several variants differ visibly (die order, moulding), the model follows the stocked variant and the+  others are noted.+- Separate pages are for parts that need their own owners or release cadence (see **wiki-family**), or a+  different package or land pattern. The wiki's `hardware --kind group` page type exists for sets of parts.++## Datasheet callouts inside the hero GLB++When a footprint is correct but LOOKS wrong next to the 3D part (pads smaller than the terminals, copper+offset from a castellation, an unusual gap), explain it in the hero itself, where the reader is looking, so+nobody files an issue against a correct footprint. Worked example: `adom/ws2812b-2020`+(`provenance/tools/hero_post_callout.py`): from below, amber dashed boxes mark the terminal strips that get no+copper, dimension arrows show the 0.40 mm pad gap, and a text panel cites the datasheet page.++- Put it in its own declared layer (`extras.adomLayer`, e.g. key `datasheet_note`, label "Datasheet note") so+  a reader can switch it off, and add `extras.tooltip` on every piece with the same explanation.+- Dashed outline only, no fill inside it; amber reads as "note", distinct from the teal pad outlines.+- Text is a textured quad (unlit, alpha blend), written to read upright in the **Adom viewer's** Bottom view+  (ViewCube "BOT"); check it in the real viewer, not only in a local renderer, because the viewer's Z-up+  load flips the frame. Place it just under the part's seat (about 6 um below z = 0) and above the copper fill.+- Say only what the datasheet says. If the maker gives no reason for a layout, write that, and label any+  inference as such ("a 0.40 mm gap is the usual guard against solder bridges").+- Ship the script as `provenance/tools/hero_post_<name>.py`: hero rebuild tools run every `hero_post_*.py`+  after the copper fill, so a rebuilt hero keeps its callout. Keep the script self-contained.++## Hero copper fill and outlines outside the copper++Heroes carry a faint translucent copper fill built from the footprint's own pads (shape, size, rotation), in+its own "Copper pads" layer, so a reader sees the copper area and its true edge and can see the part through+it from underneath. The teal dashed pad outlines sit just OUTSIDE the copper: each pad's dashed ring is scaled+about the pad centre so its inner edge lands on the copper edge. Move rings as a whole (an affine scale per+pad); shifting vertices one by one twists the dashes at corners. Pads follow the datasheet: plain rectangles+when the maker draws rectangles (no added corner rounding), the IPC/KiCad rounded rectangle only when the+datasheet has no land pattern and IPC is the stated fallback.++## Datasheet-built 3D models: prove them by overlay++When the maker publishes no 3D model (a reseller's model was drawn from the same datasheet anyway), build it+from the datasheet and redistribute it, but it must be exact:++- Printed dimensions as printed; undimensioned features measured off the drawing at a known px/mm (calibrate+  on the printed edges, check that every printed dimension measures true); odd shapes traced from the drawing.+- Prove it: render orthographic views at the drawing's scale and blend them over the datasheet views (top,+  bottom, side). Publish the overlay image as evidence and log it in the page's verification log.+- Colours from the maker's product photo when there is one; mark the part number where the maker or the+  reviewer says (side walls for LEDs, dark marks on light bodies when a light mark would not read).+- Keep the builder and its data in `provenance/tools/`, the previous model in `provenance/`, and say in the+  README that the model is AI-generated from the datasheet.++## Verification log and the `::adom-verified` trust mark++Every component page that a person has checked carries a `verification.json` (schema `adom/verification@1`)+and shows it near the top with:++```markdown+::adom-verified{src="/OWNER/SLUG/render/verification.json"}+```++The widget (john/component-verification) shows a big green check with who verified the page and when, a card+per ordering variant with what has been verified for it, and the full log: each entry's checks, evidence+links (overlay images, datasheet pages, IPC references) and the SHA-256 of every verified file. It re-hashes+those files in the reader's browser and turns amber when one changed after it was verified, so trust cannot+outlive what was checked. Add entries with `tools/verify_log.py` from john/component-verification; record+open questions as `--status open` entries rather than leaving them out. Anyone who verifies something adds+their own entry.+ ## 📋 Platform TODO (for Colby / adom-desktop): fold these into build asks  - ~~**Custom-HTML page mode**~~ **SHIPPED** (verified 2026-07-15): a repo