Definitions

@@ -13,6 +13,63 @@ guesswork (or "testing" whether it is a CLI subcommand) produces confidently wro  If a term isn't here, propose it -- this page is the vocabulary every Adom AI and human shares. +## The Name Table (start here)++Our core brand names, one row per product. **Name** is what we say and write day to day ("open+Hydrogen", "is Bridge running?"). **Full name** is the formal form: it is the installed+executable's name on Windows and macOS, so a taskbar or Spotlight search for "adom" finds the app;+use it in marketing, legal, and first mentions in public docs. **ai** is the shorthand every Adom+AI resolves. Native apps get per-OS variants (h win, h mac, h ubuntu) when you need to name a+specific build.++| Product | Name | Full name | ai | OS variants | CLI (ai short) |+|---------|------|-----------|----|-------------|----------------|+| The desktop app, our flagship going to market | **Hydrogen** | Adom Hydrogen | **h** | h win, h mac, h ubuntu (planned) | `adom-cli hydrogen ...` |+| The web app, the future launch of today's cloud-container experience (hydrogen.adom.inc) | **Hydrogen Cloud** | Adom Hydrogen Cloud | **hc** | none, it runs in your browser | `adom-cli` |+| The desktop bridge/relay, formerly "Adom Desktop" | **Bridge** | Adom Bridge | **b** | b win, b mac, b ubuntu (planned) | `adom-desktop` (rename pending to match the brand) |+| The wiki | **the wiki** | Adom Wiki | **aw** | none | `adom-wiki` (aw) |+| The forum | **the forum** | Adom Forum | **forum** | none | none yet |++Standard default bridges (they ride Bridge, always lowercase):++| Bridge | Full name | ai | Verb family |+|--------|-----------|----|-------------|+| **pup** | the Puppeteer bridge | pup | `browser_*` |+| **abe** | the Adom browser extension | abe | `nbrowser_*` |+| **kicad** | the KiCad bridge | kicad | `kicad_*` |+| **fusion** | the Fusion 360 bridge | fusion | `fusion_*` |++Rules of thumb:++- Say the bare **Name** (Hydrogen, Bridge) in everyday speech and UI; reach for the **Full name**+  (Adom Hydrogen, Adom Bridge) when the Adom association matters: executables, app-store listings,+  marketing, or the first mention in a public doc.+- The single-letter shorthands **h** and **b** are deliberate experiments. If a single letter+  proves too short or ambiguous in AI conversation, the fallbacks are **ah** and **ab**. **hc**+  needs no fallback.+- Legacy short forms you will still hear and see: **ad** (now b, the Bridge), **hw** (now hc),+  **hd** (survives only inside frozen identifiers like `hd_*` verbs and `hdbw`).++## The 2026-08 renames (what changed, and why)++We are going to market with the desktop app, so the naming got a deliberate overhaul. What moved:++| Old name | New name | Why |+|----------|----------|-----|+| Adom Hydrogen (as the everyday name) | **Hydrogen** (full name Adom Hydrogen) | The everyday name is now just Hydrogen. The installed executable keeps the full name "Adom Hydrogen" so a Windows taskbar or macOS Spotlight search for "adom" finds the app. Same app, two registers: say Hydrogen; install Adom Hydrogen. |+| Hydrogen Web (hw) | **Hydrogen Cloud** (hc, full name Adom Hydrogen Cloud) | The web twin of Hydrogen launches later under the Cloud name, matching how people think of the hosted version of a desktop product. Today's cloud-container experience at hydrogen.adom.inc is the pre-launch hc. |+| Adom Desktop (AD/ad) | **Bridge** (b, full name Adom Bridge) | "Desktop" said where it ran, not what it does. The app IS the bridge between AIs and your real machine, and it hosts the bridges (pup, abe, kicad, fusion), so the product takes that name. It also gives Hydrogen and Bridge parallel app-style names. The `adom-desktop` CLI binary keeps its name until the CLI rename lands. |++Why the naming works the way it does:++- Every product has a short punchy **Name** and an Adom-prefixed **Full name**. The Full name exists+  for OS search, app listings, and marketing, where the Adom association has to be explicit. The+  Name exists for everything else, because nobody says "Adobe Photoshop" twice in one conversation.+- The ai shorthands go as short as they can: **h**, **hc**, **b**. Single letters are an+  experiment; if they collide or confuse in practice, the fallbacks are **ah** and **ab**.+- Native apps ship per-OS builds, so the shorthand takes an OS suffix when the build matters:+  **h win**, **h mac**, **h ubuntu**, and likewise **b win**, **b mac**, **b ubuntu**.+ ## Core Platform  | Term | Definition |@@ -20,12 +77,12 @@ If a term isn't here, propose it -- this page is the vocabulary every Adom AI an | **Adom** | The platform and company. Never surface internal codenames to users. | | **The wiki** / **adom-wiki** (short: **aw**) | One product, two faces: the site (https://wiki.adom.inc — the shared electronics wiki for the AI age: apps, skills, hardware, bootstraps, packages; THE distribution channel for everything Adom) and its CLI (`adom-wiki`). "The wiki", "adom-wiki", and "aw" all refer to it — context says whether you mean the site or the CLI. | | **Hardware** (wiki page type) | The wiki's page type for physical things, renamed from `component` at the 2026-08 taxonomy launch (the old spelling stays accepted on input forever, and survives as a kind). Every hardware page carries a `kind`: **component** (a purchasable part with an MPN), **molecule** (an Adom-built module), **project** (a factory scaffold layout designed in the 3D editor; `board` is an accepted alias, and projects are CLONED, not installed), or **equipment** (factory gear). |-| **Hydrogen Web (HW)** (casual: **hw**) | The web app at hydrogen.adom.inc: toolbar, panels, VS Code, profile — the browser twin of Adom Hydrogen. Parallel naming: hw (web) and h (desktop) are the two faces of Hydrogen. ("Adom App" and "Workspace" are NOT Adom terms.) |-| **Container** | The persistent environment your work lives in — files, tooling, panels layout. Specify with the product: an **hw container** (cloud Docker) or an **h container** (local: the WSL2 `Adom-Workspace` distro on Windows, Lima on macOS). We say "container", NOT "workspace" — the word workspace survives only inside frozen identifiers (`Adom-Workspace`, `adom-cli hydrogen workspace …`, adom-workspace-control). |-| **Adom Hydrogen (H)** (casual: **h**) | The Windows/macOS desktop app — the flagship, publicly released face of Hydrogen. Runs its container locally and bundles AD. Sibling of hw. The old short form "hd" survives only inside frozen identifiers (`hd_*` verbs, `hdbw`, `hd-bootstrap`, window labels). H-specific terms: see the Adom Hydrogen section below. |-| **Adom Desktop (AD)** | The desktop bridge/relay: gives AIs hands on the user's real machine — shell, files, screenshots, KiCad/Fusion bridges, pup, the browser extension, window control. CLI surface: `adom-desktop <verb>`. Everyday short form: **AD** / "ad" ("is ad running?", "ask ad", "ad is back") — when a user says "ad" they mean this bridge. |+| **Hydrogen Cloud** (ai: **hc**) | The web app: the browser twin of Hydrogen, launching later under this name. Today's cloud-container experience at hydrogen.adom.inc (toolbar, panels, VS Code, profile) IS the pre-launch hc. Full name when the Adom association matters: **Adom Hydrogen Cloud**. Parallel naming: hc (web) and h (desktop) are the two faces of Hydrogen. Legacy names you'll still see: "Hydrogen Web" / **hw**. ("Adom App" and "Workspace" are NOT Adom terms.) |+| **Container** | The persistent environment your work lives in — files, tooling, panels layout. Specify with the product: an **hc container** (cloud Docker) or an **h container** (local: the WSL2 `Adom-Workspace` distro on Windows, Lima on macOS). We say "container", NOT "workspace" — the word workspace survives only inside frozen identifiers (`Adom-Workspace`, `adom-cli hydrogen workspace …`, adom-workspace-control). |+| **Hydrogen** (ai: **h**) | The desktop app, our flagship going to market: Windows and macOS native today, Ubuntu native planned (**h win**, **h mac**, **h ubuntu**). Runs its container locally and bundles Bridge. Sibling of hc. The installed executable is named **Adom Hydrogen** so a taskbar/Spotlight search for "adom" finds it; in speech and docs just say Hydrogen. The old short form "hd" survives only inside frozen identifiers (`hd_*` verbs, `hdbw`, `hd-bootstrap`, window labels). H-specific terms: see the Hydrogen (h) section below. |+| **Bridge** (ai: **b**) | The desktop bridge/relay, formerly "Adom Desktop": gives AIs hands on the user's real machine — shell, files, screenshots, KiCad/Fusion bridges, pup, the browser extension, window control. Full name: **Adom Bridge**. Native per-OS builds: **b win**, **b mac**, **b ubuntu** (planned). CLI surface is still `adom-desktop <verb>` (rename pending). Legacy short form you'll still hear: **AD** / "ad" ("is ad running?") — when a user says "ad" or "b" they mean this bridge. | | **abe** | The Adom browser extension — lets the AI drive the user's REAL signed-in Chrome/Edge (`nbrowser_*` verbs): logged-in sites, real credentials, human trust. |-| **Panel** | A rectangular area of the Hydrogen layout (hw or h) — VS Code, webview, 3D viewer, cameras, sensors. Panels split, resize, move, close; each has a tab with name + icon. |+| **Panel** | A rectangular area of the Hydrogen layout (hc or h) — VS Code, webview, 3D viewer, cameras, sensors. Panels split, resize, move, close; each has a tab with name + icon. |  ## Display Surfaces (how the AI shows an app or page) @@ -33,10 +90,10 @@ If a term isn't here, propose it -- this page is the vocabulary every Adom AI an |------|-----------| | **webview** (short: **wv**) | THE workhorse display surface: a native Hydrogen webview tab — a first-class panel next to the editor. ONE word, always ("Web View" is not an Adom term); on every platform "show me in webview"/"wv" means THIS, never VS Code's Simple Browser. Open idempotently: `adom-cli hydrogen webview open-or-refresh --name "<Tab>" --url "<URL>" --panel-id <id>` (re-running with the same `--name` just navigates — a stable handle). THE PLATFORM TRAP is the URL: in a CLOUD container the tab renders in the user's browser, so `localhost` is WRONG — use the slug proxy URL (`https://{slug}.adom.cloud/proxy/{port}/`); under Hydrogen the tab renders on the same machine, so `http://localhost:{port}` is correct. Verify the tab exists (`adom-cli hydrogen workspace tabs`) before claiming it opened. Under Hydrogen, a site that refuses framing shows a handoff card offering the External Webview (extwv) or hdbw. | | **External Webview** (short: **extwv**) | An Hydrogen panel tab backed by a REAL browser surface (native WebView2) instead of the default wv iframe: the opt-in escape hatch for sites that refuse to be embedded, like Google and Amazon (X-Frame-Options / CSP frame-ancestors). Same tab ergonomics as wv (URL bar, back/forward, reload, rename, rich tab tooltip), but heavier, and Hydrogen's own HTML cannot draw over a native surface, so it is opt-in rather than the default. Open it from the + panel menu ("External Webview"), or take the handoff card a blocked wv shows. Only exists under Hydrogen. "Open it in extwv" == this. |-| **pup** | The AI's own Chrome on the user's desktop (Puppeteer bridge via AD, `browser_*` verbs). A real, full browser window the AI fully controls: sessions (`sessionId` is the handle — task-prefix it and set `owner` so threads never steal each other's windows), many TABS in one window (preferred over window sprawl), screenshots, JS eval, taskbar flash. Opens BACKGROUND by default — `foreground:true` is the only thing that raises it; signal with a flash instead of stealing focus. Cold profiles = LOGGED OUT by design: the safe automation surface (fresh-user testing, scraping public pages, showing wiki pages). For logged-in sites use nb instead. Windows never auto-close — clean up when a task ends. Always lowercase. |+| **pup** | The AI's own Chrome on the user's desktop (Puppeteer bridge via Bridge, `browser_*` verbs). A real, full browser window the AI fully controls: sessions (`sessionId` is the handle — task-prefix it and set `owner` so threads never steal each other's windows), many TABS in one window (preferred over window sprawl), screenshots, JS eval, taskbar flash. Opens BACKGROUND by default — `foreground:true` is the only thing that raises it; signal with a flash instead of stealing focus. Cold profiles = LOGGED OUT by design: the safe automation surface (fresh-user testing, scraping public pages, showing wiki pages). For logged-in sites use nb instead. Windows never auto-close — clean up when a task ends. Always lowercase. | | **native browser** (short: **nb**) | The user's own signed-in Chrome/Edge, driven via abe (`nbrowser_*`). For logged-in sites. "Show it in nb" == open in the user's real browser. | | **nb chrome / nb chrome work / nb edge** | The `nb [browser] [profile]` pattern names a specific browser/profile: "nb chrome", "nb edge", "nb chrome work", "nb chrome personal". Maps to the Browser Picker's native destination ids (`browser:<browser>:<profileDir>`) and the profiles abe reports. The AI resolves the profile from the user's words + `GET /browser-profiles`. |-| **hdbw** | Hydrogen Browser Window — Adom Hydrogen's standalone built-in Tauri browser window: a separate OS window Hydrogen manages directly (1200x800, centered, its own webview badge icon; window label `hd-browse-*`). Bigger canvas than a wv pane tab, still Hydrogen-native — NOT a webview panel, NOT pup. Open first-class via `POST /hdbw/open {url}` on Hydrogen's control API, or pick "Hydrogen Browser Window (hdbw)" in the Browser Picker (destination id `webview-window`). Only exists under Hydrogen. Now a full mini-browser: URL bar, back/forward, TABS (favicons + rich hover tooltip cards), and a move-this-tab-to-another-surface action powered by the Browser Picker. |+| **hdbw** | Hydrogen Browser Window — Hydrogen's standalone built-in Tauri browser window: a separate OS window Hydrogen manages directly (1200x800, centered, its own webview badge icon; window label `hd-browse-*`). Bigger canvas than a wv pane tab, still Hydrogen-native — NOT a webview panel, NOT pup. Open first-class via `POST /hdbw/open {url}` on Hydrogen's control API, or pick "Hydrogen Browser Window (hdbw)" in the Browser Picker (destination id `webview-window`). Only exists under Hydrogen. Now a full mini-browser: URL bar, back/forward, TABS (favicons + rich hover tooltip cards), and a move-this-tab-to-another-surface action powered by the Browser Picker. | | **Browser Picker** | Hydrogen's canonical URL router: every link opened inside Hydrogen goes through it. Offers the surfaces above + native profiles from abe, a fresh-window toggle, a 5s auto-countdown, and per-domain memory of the user's past choice (incl. localhost:port domains). | | **Simple Browser** | VS Code's built-in browser page. NEVER an Adom surface — showing an app there is a bug on every platform. | @@ -71,7 +128,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **adom-cli** | Platform CLI — containers, repos, orgs, SSH keys, Hydrogen control (`adom-cli hydrogen …` drives panels/webviews). | | **adom-wiki** (short: **aw**) | The wiki's CLI — pkg publish/install/update, page repos, releases, issues, PRs. Same product as "the wiki" above; aw covers both. (`adompkg` is dead; never use it.) | | **pkg** | Bare "pkg" means `adom-wiki pkg` — "pkg install it", "pkg update", "did you pkg publish?" all refer to the wiki package manager. |-| **adom-desktop** | AD's verb surface from any container — shell, files, screenshots, bridges, pup (`browser_*`), windows (`desktop_*`), Hydrogen control (`hd_*`). |+| **adom-desktop** | Bridge's verb surface from any container: shell, files, screenshots, bridges, pup (`browser_*`), windows (`desktop_*`), Hydrogen control (`hd_*`). The binary still carries the old "Adom Desktop" name; a rename to match the Bridge brand is pending. | | **adom-vscode** | CLI + VS Code extension controlling code-server (port 8821): open files, run editor commands, drive Claude Code panels. | | **shotlog** | THE show-your-work channel: a screenshot log server + CLI (port 8820). The AI cannot display images in chat — shotlog is how the human actually SEES: inject/paste shots into named CHANNELS (per task/topic), watched live in a skinny wv panel, a pup window, or on the phone. `shotlog viewers -c <channel>` verifies a HUMAN is genuinely watching (on-screen vs backgrounded vs nobody) so the AI never claims "shown" unwatched. `shotlog channels` shows what every AI thread is sharing. Ralph loops and demos log every frame here. Always lowercase. | | **claude** | The Claude Code CLI. The ONE tool installed at runtime by Hydrogen's cascade (its self-setup needs a live session) — everything else is baked or package-delivered. |@@ -90,7 +147,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver  | Term | Definition | |------|-----------|-| **adom-symbol** | Creates schematic symbols — KiCad `.kicad_sym` and Fusion/EAGLE `.lbr` — from a part number or datasheet, previews them in a webview, and sends them to KiCad or Fusion 360 Electronics via AD. |+| **adom-symbol** | Creates schematic symbols — KiCad `.kicad_sym` and Fusion/EAGLE `.lbr` — from a part number or datasheet, previews them in a webview, and sends them to KiCad or Fusion 360 Electronics via Bridge. | | **adom-footprint** | Creates KiCad `.kicad_mod` footprints (and the 3D pad preview) the same way — generate, preview in wv, deliver to the EDA tool. | | **adom-lbr** | The Adom Library management tool — organizes symbols/footprints/3D models into libraries, browses and exports them (incl. Fusion export). | | **chip-fetcher** (short: **cf**) | Fetches EVERYTHING about a chip — datasheet, symbol, footprint, 3D model — from vendor sites (SnapEDA, Ultra Librarian, Mouser, DigiKey) into a live dashboard, with per-site scraping playbooks. Scrapes via nb by preference (real logins beat bot-walls), pup as fallback. |@@ -100,8 +157,8 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **mouser / digikey / jlcpcb** (or **jlc**) | When a user says a vendor name bare — "search mouser", "check digikey", "jlc has it?" — they usually mean OUR per-vendor parts-search app for that vendor (**adom-mouser**, **adom-digikey**, **adom-jlcpcb**), not the vendor website. Each searches that vendor's catalog/API and shows results in wv. adom-parts-search queries all three at once. | | **adom-parts-search** | One search across Mouser + DigiKey + JLCPCB with a Mouser-preferred recommendation (40-min drone delivery to Fort Worth). `adom-parts-search show` opens the wv app + prints the data. | | **adom-tsci** | tscircuit-powered build-a-board-in-one-prompt: describe a board ("rp2040 dev board with usb-c"), get schematic/PCB/3D in the interactive Board Viewer (wv), with inspect/measure tools and a re-runnable autorouter. |-| **fusion** | When a user says "fusion" in an Adom context they mean the AD **Fusion 360 bridge** (`fusion_*` verbs) driving desktop Fusion 360 Electronics — open projects, place parts, screenshot, drive the schematic/board/3D. (The Autodesk product itself is "Fusion 360".) |-| **kicad** | When a user says "kicad" they TYPICALLY mean AD's **KiCad bridge** (`kicad_*` verbs): open sch/pcb, symbol/footprint editors, 3D viewer — driving the real desktop KiCad. Disambiguate from the other KiCad tools below by context. |+| **fusion** | When a user says "fusion" in an Adom context they mean Bridge's **Fusion 360 bridge** (`fusion_*` verbs) driving desktop Fusion 360 Electronics — open projects, place parts, screenshot, drive the schematic/board/3D. (The Autodesk product itself is "Fusion 360".) |+| **kicad** | When a user says "kicad" they TYPICALLY mean Bridge's **KiCad bridge** (`kicad_*` verbs): open sch/pcb, symbol/footprint editors, 3D viewer — driving the real desktop KiCad. Disambiguate from the other KiCad tools below by context. | | **service-kicad** | The SHARED headless KiCad service container — DRC/ERC, gerber/STEP/GLB export, symbol/footprint/3D lookups via the `service-kicad` CLI. No desktop KiCad needed; every container can use it. "Run DRC" / "export gerbers" usually means this. |  ### Chip Vendors & CAD Sources (spoken shorthand)@@ -116,7 +173,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **ul** | Ultra Librarian — CAD-model source | | **cse** | Component Search Engine (SamacSys) — CAD-model source | -## Adom Hydrogen (h) terms+## Hydrogen (h) terms  | Term | Definition | |------|-----------|@@ -130,7 +187,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | URL Pattern | What it is | |-------------|-----------| | `https://hydrogen.adom.inc/{owner}/{repo}` | Repo page (info, container status, README) — not the editor. |-| `https://hydrogen.adom.inc/{owner}/{repo}/edit` | The editor — full Hydrogen Web. Always add `/edit` to work in a container. |+| `https://hydrogen.adom.inc/{owner}/{repo}/edit` | The editor — full Hydrogen Cloud. Always add `/edit` to work in a container. | | `https://{slug}.adom.cloud/` | Direct container URL (raw VS Code). App ports proxy at `https://{slug}.adom.cloud/proxy/{port}/`. | | `https://wiki.adom.inc/{org}/{page}` | A wiki page (Overview, Files, Skills, Packages, Releases, Issues tabs). | @@ -139,9 +196,10 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | Rule | Detail | |------|--------| | **webview is one word** | Never "Web View". Short form: wv. |-| **lowercase tools** | pup, shotlog, abe, wv, nb, hdbw, ad, h, hw, aw, cf — always lowercase in casual prose (AD/H/HW in formal docs). |-| **vscode** (formal: **VS Code**) | The IDE inside the container (powered by code-server). We say/type "vscode" ("open it in vscode", "the vscode iframe"); "VS Code" is the formal spelling for docs/UI. Never call it "the editor" — the Editor is Hydrogen (hw/h) around it. Avoid "code-server"/"Coder" in user-facing text. |-| **No internal codenames to users** | "Carbon" (the backend registry) is internal — code/URLs only. "Hydrogen" is PUBLIC brand (Hydrogen Web / Adom Hydrogen). |+| **lowercase tools** | pup, shotlog, abe, wv, nb, hdbw, b, h, hc, aw, cf — always lowercase in casual prose (the Name or Full name in formal docs: Hydrogen, Bridge, Adom Hydrogen Cloud). |+| **Name vs Full name** | Bare Name in everyday speech and UI (Hydrogen, Bridge, Hydrogen Cloud); Full name (Adom Hydrogen, Adom Bridge, Adom Hydrogen Cloud) for executables, listings, marketing, and first mentions in public docs. See The Name Table at the top. |+| **vscode** (formal: **VS Code**) | The IDE inside the container (powered by code-server). We say/type "vscode" ("open it in vscode", "the vscode iframe"); "VS Code" is the formal spelling for docs/UI. Never call it "the editor" — the Editor is Hydrogen (hc/h) around it. Avoid "code-server"/"Coder" in user-facing text. |+| **No internal codenames to users** | "Carbon" (the backend registry) is internal — code/URLs only. "Hydrogen" and "Bridge" are PUBLIC brand (Adom Hydrogen, Adom Hydrogen Cloud, Adom Bridge). |  ## Coordinate System 

@@ -3,7 +3,8 @@ name: definitions description: >   Canonical Adom glossary. Use when the user asks "what is [term]", "define [term]", "what does   [term] mean", "glossary", "definitions", or uses Adom shorthand that must resolve correctly ---  wv, extwv, nb, pup, abe, hdbw, ad, h, hw, aw, cf, shotlog, jlc -- or when writing user-facing copy+  wv, extwv, nb, pup, abe, hdbw, b, h, hc, aw, cf, shotlog, jlc (legacy: ad, hw) -- or when writing+  user-facing copy   that must use Adom vocabulary consistently. --- # Adom Definitions@@ -17,6 +18,63 @@ guesswork (or "testing" whether it is a CLI subcommand) produces confidently wro  If a term isn't here, propose it -- this page is the vocabulary every Adom AI and human shares. +## The Name Table (start here)++Our core brand names, one row per product. **Name** is what we say and write day to day ("open+Hydrogen", "is Bridge running?"). **Full name** is the formal form: it is the installed+executable's name on Windows and macOS, so a taskbar or Spotlight search for "adom" finds the app;+use it in marketing, legal, and first mentions in public docs. **ai** is the shorthand every Adom+AI resolves. Native apps get per-OS variants (h win, h mac, h ubuntu) when you need to name a+specific build.++| Product | Name | Full name | ai | OS variants | CLI (ai short) |+|---------|------|-----------|----|-------------|----------------|+| The desktop app, our flagship going to market | **Hydrogen** | Adom Hydrogen | **h** | h win, h mac, h ubuntu (planned) | `adom-cli hydrogen ...` |+| The web app, the future launch of today's cloud-container experience (hydrogen.adom.inc) | **Hydrogen Cloud** | Adom Hydrogen Cloud | **hc** | none, it runs in your browser | `adom-cli` |+| The desktop bridge/relay, formerly "Adom Desktop" | **Bridge** | Adom Bridge | **b** | b win, b mac, b ubuntu (planned) | `adom-desktop` (rename pending to match the brand) |+| The wiki | **the wiki** | Adom Wiki | **aw** | none | `adom-wiki` (aw) |+| The forum | **the forum** | Adom Forum | **forum** | none | none yet |++Standard default bridges (they ride Bridge, always lowercase):++| Bridge | Full name | ai | Verb family |+|--------|-----------|----|-------------|+| **pup** | the Puppeteer bridge | pup | `browser_*` |+| **abe** | the Adom browser extension | abe | `nbrowser_*` |+| **kicad** | the KiCad bridge | kicad | `kicad_*` |+| **fusion** | the Fusion 360 bridge | fusion | `fusion_*` |++Rules of thumb:++- Say the bare **Name** (Hydrogen, Bridge) in everyday speech and UI; reach for the **Full name**+  (Adom Hydrogen, Adom Bridge) when the Adom association matters: executables, app-store listings,+  marketing, or the first mention in a public doc.+- The single-letter shorthands **h** and **b** are deliberate experiments. If a single letter+  proves too short or ambiguous in AI conversation, the fallbacks are **ah** and **ab**. **hc**+  needs no fallback.+- Legacy short forms you will still hear and see: **ad** (now b, the Bridge), **hw** (now hc),+  **hd** (survives only inside frozen identifiers like `hd_*` verbs and `hdbw`).++## The 2026-08 renames (what changed, and why)++We are going to market with the desktop app, so the naming got a deliberate overhaul. What moved:++| Old name | New name | Why |+|----------|----------|-----|+| Adom Hydrogen (as the everyday name) | **Hydrogen** (full name Adom Hydrogen) | The everyday name is now just Hydrogen. The installed executable keeps the full name "Adom Hydrogen" so a Windows taskbar or macOS Spotlight search for "adom" finds the app. Same app, two registers: say Hydrogen; install Adom Hydrogen. |+| Hydrogen Web (hw) | **Hydrogen Cloud** (hc, full name Adom Hydrogen Cloud) | The web twin of Hydrogen launches later under the Cloud name, matching how people think of the hosted version of a desktop product. Today's cloud-container experience at hydrogen.adom.inc is the pre-launch hc. |+| Adom Desktop (AD/ad) | **Bridge** (b, full name Adom Bridge) | "Desktop" said where it ran, not what it does. The app IS the bridge between AIs and your real machine, and it hosts the bridges (pup, abe, kicad, fusion), so the product takes that name. It also gives Hydrogen and Bridge parallel app-style names. The `adom-desktop` CLI binary keeps its name until the CLI rename lands. |++Why the naming works the way it does:++- Every product has a short punchy **Name** and an Adom-prefixed **Full name**. The Full name exists+  for OS search, app listings, and marketing, where the Adom association has to be explicit. The+  Name exists for everything else, because nobody says "Adobe Photoshop" twice in one conversation.+- The ai shorthands go as short as they can: **h**, **hc**, **b**. Single letters are an+  experiment; if they collide or confuse in practice, the fallbacks are **ah** and **ab**.+- Native apps ship per-OS builds, so the shorthand takes an OS suffix when the build matters:+  **h win**, **h mac**, **h ubuntu**, and likewise **b win**, **b mac**, **b ubuntu**.+ ## Core Platform  | Term | Definition |@@ -24,12 +82,12 @@ If a term isn't here, propose it -- this page is the vocabulary every Adom AI an | **Adom** | The platform and company. Never surface internal codenames to users. | | **The wiki** / **adom-wiki** (short: **aw**) | One product, two faces: the site (https://wiki.adom.inc — the shared electronics wiki for the AI age: apps, skills, hardware, bootstraps, packages; THE distribution channel for everything Adom) and its CLI (`adom-wiki`). "The wiki", "adom-wiki", and "aw" all refer to it — context says whether you mean the site or the CLI. | | **Hardware** (wiki page type) | The wiki's page type for physical things, renamed from `component` at the 2026-08 taxonomy launch (the old spelling stays accepted on input forever, and survives as a kind). Every hardware page carries a `kind`: **component** (a purchasable part with an MPN), **molecule** (an Adom-built module), **project** (a factory scaffold layout designed in the 3D editor; `board` is an accepted alias, and projects are CLONED, not installed), or **equipment** (factory gear). |-| **Hydrogen Web (HW)** (casual: **hw**) | The web app at hydrogen.adom.inc: toolbar, panels, VS Code, profile — the browser twin of Adom Hydrogen. Parallel naming: hw (web) and h (desktop) are the two faces of Hydrogen. ("Adom App" and "Workspace" are NOT Adom terms.) |-| **Container** | The persistent environment your work lives in — files, tooling, panels layout. Specify with the product: an **hw container** (cloud Docker) or an **h container** (local: the WSL2 `Adom-Workspace` distro on Windows, Lima on macOS). We say "container", NOT "workspace" — the word workspace survives only inside frozen identifiers (`Adom-Workspace`, `adom-cli hydrogen workspace …`, adom-workspace-control). |-| **Adom Hydrogen (H)** (casual: **h**) | The Windows/macOS desktop app — the flagship, publicly released face of Hydrogen. Runs its container locally and bundles AD. Sibling of hw. The old short form "hd" survives only inside frozen identifiers (`hd_*` verbs, `hdbw`, `hd-bootstrap`, window labels). H-specific terms: see the Adom Hydrogen section below. |-| **Adom Desktop (AD)** | The desktop bridge/relay: gives AIs hands on the user's real machine — shell, files, screenshots, KiCad/Fusion bridges, pup, the browser extension, window control. CLI surface: `adom-desktop <verb>`. Everyday short form: **AD** / "ad" ("is ad running?", "ask ad", "ad is back") — when a user says "ad" they mean this bridge. |+| **Hydrogen Cloud** (ai: **hc**) | The web app: the browser twin of Hydrogen, launching later under this name. Today's cloud-container experience at hydrogen.adom.inc (toolbar, panels, VS Code, profile) IS the pre-launch hc. Full name when the Adom association matters: **Adom Hydrogen Cloud**. Parallel naming: hc (web) and h (desktop) are the two faces of Hydrogen. Legacy names you'll still see: "Hydrogen Web" / **hw**. ("Adom App" and "Workspace" are NOT Adom terms.) |+| **Container** | The persistent environment your work lives in — files, tooling, panels layout. Specify with the product: an **hc container** (cloud Docker) or an **h container** (local: the WSL2 `Adom-Workspace` distro on Windows, Lima on macOS). We say "container", NOT "workspace" — the word workspace survives only inside frozen identifiers (`Adom-Workspace`, `adom-cli hydrogen workspace …`, adom-workspace-control). |+| **Hydrogen** (ai: **h**) | The desktop app, our flagship going to market: Windows and macOS native today, Ubuntu native planned (**h win**, **h mac**, **h ubuntu**). Runs its container locally and bundles Bridge. Sibling of hc. The installed executable is named **Adom Hydrogen** so a taskbar/Spotlight search for "adom" finds it; in speech and docs just say Hydrogen. The old short form "hd" survives only inside frozen identifiers (`hd_*` verbs, `hdbw`, `hd-bootstrap`, window labels). H-specific terms: see the Hydrogen (h) section below. |+| **Bridge** (ai: **b**) | The desktop bridge/relay, formerly "Adom Desktop": gives AIs hands on the user's real machine — shell, files, screenshots, KiCad/Fusion bridges, pup, the browser extension, window control. Full name: **Adom Bridge**. Native per-OS builds: **b win**, **b mac**, **b ubuntu** (planned). CLI surface is still `adom-desktop <verb>` (rename pending). Legacy short form you'll still hear: **AD** / "ad" ("is ad running?") — when a user says "ad" or "b" they mean this bridge. | | **abe** | The Adom browser extension — lets the AI drive the user's REAL signed-in Chrome/Edge (`nbrowser_*` verbs): logged-in sites, real credentials, human trust. |-| **Panel** | A rectangular area of the Hydrogen layout (hw or h) — VS Code, webview, 3D viewer, cameras, sensors. Panels split, resize, move, close; each has a tab with name + icon. |+| **Panel** | A rectangular area of the Hydrogen layout (hc or h) — VS Code, webview, 3D viewer, cameras, sensors. Panels split, resize, move, close; each has a tab with name + icon. |  ## Display Surfaces (how the AI shows an app or page) @@ -37,10 +95,10 @@ If a term isn't here, propose it -- this page is the vocabulary every Adom AI an |------|-----------| | **webview** (short: **wv**) | THE workhorse display surface: a native Hydrogen webview tab — a first-class panel next to the editor. ONE word, always ("Web View" is not an Adom term); on every platform "show me in webview"/"wv" means THIS, never VS Code's Simple Browser. Open idempotently: `adom-cli hydrogen webview open-or-refresh --name "<Tab>" --url "<URL>" --panel-id <id>` (re-running with the same `--name` just navigates — a stable handle). THE PLATFORM TRAP is the URL: in a CLOUD container the tab renders in the user's browser, so `localhost` is WRONG — use the slug proxy URL (`https://{slug}.adom.cloud/proxy/{port}/`); under Hydrogen the tab renders on the same machine, so `http://localhost:{port}` is correct. Verify the tab exists (`adom-cli hydrogen workspace tabs`) before claiming it opened. Under Hydrogen, a site that refuses framing shows a handoff card offering the External Webview (extwv) or hdbw. | | **External Webview** (short: **extwv**) | An Hydrogen panel tab backed by a REAL browser surface (native WebView2) instead of the default wv iframe: the opt-in escape hatch for sites that refuse to be embedded, like Google and Amazon (X-Frame-Options / CSP frame-ancestors). Same tab ergonomics as wv (URL bar, back/forward, reload, rename, rich tab tooltip), but heavier, and Hydrogen's own HTML cannot draw over a native surface, so it is opt-in rather than the default. Open it from the + panel menu ("External Webview"), or take the handoff card a blocked wv shows. Only exists under Hydrogen. "Open it in extwv" == this. |-| **pup** | The AI's own Chrome on the user's desktop (Puppeteer bridge via AD, `browser_*` verbs). A real, full browser window the AI fully controls: sessions (`sessionId` is the handle — task-prefix it and set `owner` so threads never steal each other's windows), many TABS in one window (preferred over window sprawl), screenshots, JS eval, taskbar flash. Opens BACKGROUND by default — `foreground:true` is the only thing that raises it; signal with a flash instead of stealing focus. Cold profiles = LOGGED OUT by design: the safe automation surface (fresh-user testing, scraping public pages, showing wiki pages). For logged-in sites use nb instead. Windows never auto-close — clean up when a task ends. Always lowercase. |+| **pup** | The AI's own Chrome on the user's desktop (Puppeteer bridge via Bridge, `browser_*` verbs). A real, full browser window the AI fully controls: sessions (`sessionId` is the handle — task-prefix it and set `owner` so threads never steal each other's windows), many TABS in one window (preferred over window sprawl), screenshots, JS eval, taskbar flash. Opens BACKGROUND by default — `foreground:true` is the only thing that raises it; signal with a flash instead of stealing focus. Cold profiles = LOGGED OUT by design: the safe automation surface (fresh-user testing, scraping public pages, showing wiki pages). For logged-in sites use nb instead. Windows never auto-close — clean up when a task ends. Always lowercase. | | **native browser** (short: **nb**) | The user's own signed-in Chrome/Edge, driven via abe (`nbrowser_*`). For logged-in sites. "Show it in nb" == open in the user's real browser. | | **nb chrome / nb chrome work / nb edge** | The `nb [browser] [profile]` pattern names a specific browser/profile: "nb chrome", "nb edge", "nb chrome work", "nb chrome personal". Maps to the Browser Picker's native destination ids (`browser:<browser>:<profileDir>`) and the profiles abe reports. The AI resolves the profile from the user's words + `GET /browser-profiles`. |-| **hdbw** | Hydrogen Browser Window — Adom Hydrogen's standalone built-in Tauri browser window: a separate OS window Hydrogen manages directly (1200x800, centered, its own webview badge icon; window label `hd-browse-*`). Bigger canvas than a wv pane tab, still Hydrogen-native — NOT a webview panel, NOT pup. Open first-class via `POST /hdbw/open {url}` on Hydrogen's control API, or pick "Hydrogen Browser Window (hdbw)" in the Browser Picker (destination id `webview-window`). Only exists under Hydrogen. Now a full mini-browser: URL bar, back/forward, TABS (favicons + rich hover tooltip cards), and a move-this-tab-to-another-surface action powered by the Browser Picker. |+| **hdbw** | Hydrogen Browser Window — Hydrogen's standalone built-in Tauri browser window: a separate OS window Hydrogen manages directly (1200x800, centered, its own webview badge icon; window label `hd-browse-*`). Bigger canvas than a wv pane tab, still Hydrogen-native — NOT a webview panel, NOT pup. Open first-class via `POST /hdbw/open {url}` on Hydrogen's control API, or pick "Hydrogen Browser Window (hdbw)" in the Browser Picker (destination id `webview-window`). Only exists under Hydrogen. Now a full mini-browser: URL bar, back/forward, TABS (favicons + rich hover tooltip cards), and a move-this-tab-to-another-surface action powered by the Browser Picker. | | **Browser Picker** | Hydrogen's canonical URL router: every link opened inside Hydrogen goes through it. Offers the surfaces above + native profiles from abe, a fresh-window toggle, a 5s auto-countdown, and per-domain memory of the user's past choice (incl. localhost:port domains). | | **Simple Browser** | VS Code's built-in browser page. NEVER an Adom surface — showing an app there is a bug on every platform. | @@ -75,7 +133,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **adom-cli** | Platform CLI — containers, repos, orgs, SSH keys, Hydrogen control (`adom-cli hydrogen …` drives panels/webviews). | | **adom-wiki** (short: **aw**) | The wiki's CLI — pkg publish/install/update, page repos, releases, issues, PRs. Same product as "the wiki" above; aw covers both. (`adompkg` is dead; never use it.) | | **pkg** | Bare "pkg" means `adom-wiki pkg` — "pkg install it", "pkg update", "did you pkg publish?" all refer to the wiki package manager. |-| **adom-desktop** | AD's verb surface from any container — shell, files, screenshots, bridges, pup (`browser_*`), windows (`desktop_*`), Hydrogen control (`hd_*`). |+| **adom-desktop** | Bridge's verb surface from any container: shell, files, screenshots, bridges, pup (`browser_*`), windows (`desktop_*`), Hydrogen control (`hd_*`). The binary still carries the old "Adom Desktop" name; a rename to match the Bridge brand is pending. | | **adom-vscode** | CLI + VS Code extension controlling code-server (port 8821): open files, run editor commands, drive Claude Code panels. | | **shotlog** | THE show-your-work channel: a screenshot log server + CLI (port 8820). The AI cannot display images in chat — shotlog is how the human actually SEES: inject/paste shots into named CHANNELS (per task/topic), watched live in a skinny wv panel, a pup window, or on the phone. `shotlog viewers -c <channel>` verifies a HUMAN is genuinely watching (on-screen vs backgrounded vs nobody) so the AI never claims "shown" unwatched. `shotlog channels` shows what every AI thread is sharing. Ralph loops and demos log every frame here. Always lowercase. | | **claude** | The Claude Code CLI. The ONE tool installed at runtime by Hydrogen's cascade (its self-setup needs a live session) — everything else is baked or package-delivered. |@@ -94,7 +152,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver  | Term | Definition | |------|-----------|-| **adom-symbol** | Creates schematic symbols — KiCad `.kicad_sym` and Fusion/EAGLE `.lbr` — from a part number or datasheet, previews them in a webview, and sends them to KiCad or Fusion 360 Electronics via AD. |+| **adom-symbol** | Creates schematic symbols — KiCad `.kicad_sym` and Fusion/EAGLE `.lbr` — from a part number or datasheet, previews them in a webview, and sends them to KiCad or Fusion 360 Electronics via Bridge. | | **adom-footprint** | Creates KiCad `.kicad_mod` footprints (and the 3D pad preview) the same way — generate, preview in wv, deliver to the EDA tool. | | **adom-lbr** | The Adom Library management tool — organizes symbols/footprints/3D models into libraries, browses and exports them (incl. Fusion export). | | **chip-fetcher** (short: **cf**) | Fetches EVERYTHING about a chip — datasheet, symbol, footprint, 3D model — from vendor sites (SnapEDA, Ultra Librarian, Mouser, DigiKey) into a live dashboard, with per-site scraping playbooks. Scrapes via nb by preference (real logins beat bot-walls), pup as fallback. |@@ -104,8 +162,8 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **mouser / digikey / jlcpcb** (or **jlc**) | When a user says a vendor name bare — "search mouser", "check digikey", "jlc has it?" — they usually mean OUR per-vendor parts-search app for that vendor (**adom-mouser**, **adom-digikey**, **adom-jlcpcb**), not the vendor website. Each searches that vendor's catalog/API and shows results in wv. adom-parts-search queries all three at once. | | **adom-parts-search** | One search across Mouser + DigiKey + JLCPCB with a Mouser-preferred recommendation (40-min drone delivery to Fort Worth). `adom-parts-search show` opens the wv app + prints the data. | | **adom-tsci** | tscircuit-powered build-a-board-in-one-prompt: describe a board ("rp2040 dev board with usb-c"), get schematic/PCB/3D in the interactive Board Viewer (wv), with inspect/measure tools and a re-runnable autorouter. |-| **fusion** | When a user says "fusion" in an Adom context they mean the AD **Fusion 360 bridge** (`fusion_*` verbs) driving desktop Fusion 360 Electronics — open projects, place parts, screenshot, drive the schematic/board/3D. (The Autodesk product itself is "Fusion 360".) |-| **kicad** | When a user says "kicad" they TYPICALLY mean AD's **KiCad bridge** (`kicad_*` verbs): open sch/pcb, symbol/footprint editors, 3D viewer — driving the real desktop KiCad. Disambiguate from the other KiCad tools below by context. |+| **fusion** | When a user says "fusion" in an Adom context they mean Bridge's **Fusion 360 bridge** (`fusion_*` verbs) driving desktop Fusion 360 Electronics — open projects, place parts, screenshot, drive the schematic/board/3D. (The Autodesk product itself is "Fusion 360".) |+| **kicad** | When a user says "kicad" they TYPICALLY mean Bridge's **KiCad bridge** (`kicad_*` verbs): open sch/pcb, symbol/footprint editors, 3D viewer — driving the real desktop KiCad. Disambiguate from the other KiCad tools below by context. | | **service-kicad** | The SHARED headless KiCad service container — DRC/ERC, gerber/STEP/GLB export, symbol/footprint/3D lookups via the `service-kicad` CLI. No desktop KiCad needed; every container can use it. "Run DRC" / "export gerbers" usually means this. |  ### Chip Vendors & CAD Sources (spoken shorthand)@@ -120,7 +178,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | **ul** | Ultra Librarian — CAD-model source | | **cse** | Component Search Engine (SamacSys) — CAD-model source | -## Adom Hydrogen (h) terms+## Hydrogen (h) terms  | Term | Definition | |------|-----------|@@ -134,7 +192,7 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | URL Pattern | What it is | |-------------|-----------| | `https://hydrogen.adom.inc/{owner}/{repo}` | Repo page (info, container status, README) — not the editor. |-| `https://hydrogen.adom.inc/{owner}/{repo}/edit` | The editor — full Hydrogen Web. Always add `/edit` to work in a container. |+| `https://hydrogen.adom.inc/{owner}/{repo}/edit` | The editor — full Hydrogen Cloud. Always add `/edit` to work in a container. | | `https://{slug}.adom.cloud/` | Direct container URL (raw VS Code). App ports proxy at `https://{slug}.adom.cloud/proxy/{port}/`. | | `https://wiki.adom.inc/{org}/{page}` | A wiki page (Overview, Files, Skills, Packages, Releases, Issues tabs). | @@ -143,9 +201,10 @@ Every wiki page is built from these pillars (each is a tab on the page and a ver | Rule | Detail | |------|--------| | **webview is one word** | Never "Web View". Short form: wv. |-| **lowercase tools** | pup, shotlog, abe, wv, nb, hdbw, ad, h, hw, aw, cf — always lowercase in casual prose (AD/H/HW in formal docs). |-| **vscode** (formal: **VS Code**) | The IDE inside the container (powered by code-server). We say/type "vscode" ("open it in vscode", "the vscode iframe"); "VS Code" is the formal spelling for docs/UI. Never call it "the editor" — the Editor is Hydrogen (hw/h) around it. Avoid "code-server"/"Coder" in user-facing text. |-| **No internal codenames to users** | "Carbon" (the backend registry) is internal — code/URLs only. "Hydrogen" is PUBLIC brand (Hydrogen Web / Adom Hydrogen). |+| **lowercase tools** | pup, shotlog, abe, wv, nb, hdbw, b, h, hc, aw, cf — always lowercase in casual prose (the Name or Full name in formal docs: Hydrogen, Bridge, Adom Hydrogen Cloud). |+| **Name vs Full name** | Bare Name in everyday speech and UI (Hydrogen, Bridge, Hydrogen Cloud); Full name (Adom Hydrogen, Adom Bridge, Adom Hydrogen Cloud) for executables, listings, marketing, and first mentions in public docs. See The Name Table at the top. |+| **vscode** (formal: **VS Code**) | The IDE inside the container (powered by code-server). We say/type "vscode" ("open it in vscode", "the vscode iframe"); "VS Code" is the formal spelling for docs/UI. Never call it "the editor" — the Editor is Hydrogen (hc/h) around it. Avoid "code-server"/"Coder" in user-facing text. |+| **No internal codenames to users** | "Carbon" (the backend registry) is internal — code/URLs only. "Hydrogen" and "Bridge" are PUBLIC brand (Adom Hydrogen, Adom Hydrogen Cloud, Adom Bridge). |  ## Coordinate System