Adom Definitions

Canonical glossary of Adom platform terms. Use these consistently in conversation, code, documentation and wiki content.

Read this before guessing what a short form means. Adom shorthand is real vocabulary, not typos: wv is webview, nb is the user's native browser, aw is the wiki. Resolving one by guesswork (or "testing" whether it is a CLI subcommand) produces confidently wrong answers.

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 users see and what we say externally ("open Hydrogen", "is Bridge running?"). Internal Name is the disambiguating phrase the team uses when the bare Name is ambiguous: Hydrogen is the UMBRELLA for both faces of the product, so when you must distinguish the desktop app from the cloud one you can say the phrase "Hydrogen Desktop" (desktop) vs "Hydrogen Cloud" (cloud). But prefer the shorthands: ah for the desktop app, hc for cloud, and reach for the "Hydrogen Desktop" phrase only when it genuinely reads clearer. External copy never says "Hydrogen Desktop". The hd shorthand is DEAD (see the directive below) — say ah, never hd, internal or external. Formal 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 (ah win, ah mac, ah ubuntu) when you need to name a specific build.

DIRECTIVE (John, 2026-08-09, verbatim): "ad is now called ab (Adom Bridge) and hd is now called ah (Adom Hydrogen). ONLY use that naming now. I just saw you calling it HD and AD again and we have to break away from that." Write ah / ab (or Hydrogen / Bridge) EVERYWHERE, including internal notes and agent-to-agent chatter. hd and ad as spoken shorthands are retired; only frozen CODE identifiers (hd_* verbs, hd-bootstrap, hd-browse-* labels) keep the letters until their own cutover rows land.

Standard default bridges (they ride Bridge, always lowercase):

Rules of thumb:

• Say the bare Name (Hydrogen, Bridge) in everyday speech and UI; reach for the Formal Name (Adom Hydrogen, Adom Bridge) when the Adom association matters: executables, app-store listings, marketing, or the first mention in a public doc.
• THE SHORTHAND RULE (final form, 2026-08-08): NO single-letter shorthands, every shorthand is at least two letters. When a product's natural shorthand would be ONE letter, prepend the Adom "a": w becomes aw, h becomes ah, b becomes ab. A shorthand that is already 2+ letters never takes the a; two letters are unique enough for the AI (nb not anb, hc not ahc, nbe not anbe). aw was the proof: bare "w" would be useless, aw is instantly unique.
• abe is DEPRECATED (2026-08-08): the products are Adom Native Browser (nb) and Adom Native Browser Extension (nbe). The bare single letters h and b were a brief same-day experiment, also dead: say ah and ab.
• Legacy short forms you will still hear and see, but must NOT write: ad (now ab, the Bridge), hd (now ah, Hydrogen), hw (now hc), hdbw (now hbw, the Hydrogen Browser Window), and abe (now nbe, the Adom Native Browser Extension). Frozen CODE identifiers keep their letters until their own cutover rows land (hd_* verbs, hd-bootstrap, hd-browse-* labels, _ad_* fields) — resolve them, don't coin new ones.

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:

Why the naming works the way it does:

• Every product has a short punchy Name and an Adom-prefixed Formal Name. The Formal 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.
• ai shorthands are minimum TWO letters. A natural one-letter form takes the Adom "a" (ah, ab, aw); anything already 2+ letters never does (hc, nb, nbe, hbw).
• Native apps ship per-OS builds, so the shorthand takes an OS suffix when the build matters: ah win, ah mac, ah ubuntu, and likewise ab win, ab mac, ab ubuntu.

Wiki repo renames (the tracking list)

The renames above ripple into the wiki: page slugs, titles, and URLs still carry the old names. This is the working list so the campaign stays trackable. ONE PRODUCT = ONE PAGE: satellite pages (-dev, -control, and friends) are wiki bloat, because a wiki page already supports private source alongside public pkgs and releases, and even split private/public readmes. Source lives IN the product's page; skills ship IN the product's package. THE EXECUTION RULE: renames are carried out by each repo's OWN build thread, never by the definitions thread (this page only defines names and tracks status), and "proposed" rows need John's go before any build thread renames.

THE RENAME POLICY (John, 2026-08-08): hard cutover, break loudly. We have never released to the public, so now is the moment to rename completely. No deprecation shims, no aliases, no dual-name support, no legacy triggers, no old names left working "for compatibility". We WANT things that still reference an old name to break visibly, because every real error is a real call site to find and fix; a compat layer just covers the error up and makes it worse. (The wiki's own slug 301s exist as platform behavior, but do not lean on them: fix every reference to the new name.) The "legacy" notes in the glossary above are about resolving what HUMANS still say out loud, not permission to keep old names in code, packages, triggers, or UI. Bootstrap slug renames will break dependency trees; that breakage is accepted under this policy, but sequence it with John so the fleet break is a planned, observed one.

RENAME EXECUTION TRAPS (from the nb build thread's cutover, definitions#3) — each was a SILENT break, not an error, so a naive find-and-replace ships them undetected. Any thread doing a rename must check all three:

1. A blanket "Adom Desktop" → "Bridge" rewrite corrupts real filesystem paths. The productName dir is %LOCALAPPDATA%\Adom Bridge\ (and %TEMP%\adom-bridge-recordings\), NOT \Bridge\. The correct replacement string is the FORMAL NAME "Adom Bridge", never the bare Name. Verify every path literal against the app's actual source, not against the sweep. (Generalizes: renaming any product, swap to its Formal Name in path/dir/AUMID literals, not the short Name.)
2. Package pins break invisibly across a major. A pin like adom/adom-desktop ^1.9.47 becomes adom/adom-bridge ^1.9.47 on rename, but adom-bridge publishes 2.x, so the caret range can NEVER resolve. A slug rename alone does not surface this. Every ^1.9.x pin on a renamed-and- major-bumped package needs ^2.x. This is a prime cause of the fleet DEPENDENCY_CONFLICT.
3. Old API paths do NOT 301 — only human page URLs redirect. /api/pages/<old-slug>/... 404s, so every installed bridge's auto-update dies SILENTLY (latest:null, updateAvailable:false) until the owning thread republishes its manifest under the new slug. No user-side error; it just stops updating. (This is why a renamed bridge must republish, and why a cached docs pointing at the old slug needs the rename-follow lookup.)

Bridge family (formerly Adom Desktop):

Third-party bridge pages exist too (barrett-land/adom-desktop-altium-bridge, barrett-land/adom-desktop-ffpup-bridge); we don't rename other owners' pages, but the naming guidance for new bridges becomes <name>-bridge without the adom-desktop prefix.

nb family (formerly the browser extension):

Hydrogen family:

Core Platform

Display Surfaces (how the AI shows an app or page)

Browser Control (nb vs nbe vs pup vs wv)

There are several ways the AI can touch a browser, and picking the wrong one is the most common surface mistake. The mental model, from "just show a page" to "fully drive a browser":

Rules of thumb:

• nb is the PARENT name, nbe is its CHILD. Layer 1 (open a URL in the user's browser) needs no install and ships value on day one; layer 2 (nbe) is the opt-in extension that unlocks deep driving. If the user hasn't installed nbe, nb layer 1 still works.
• Need the user's real logins? nb/nbe. Don't? pup. Just displaying? wv (or hbw under ah).
• The Browser Picker is how Hydrogen routes any URL to one of these surfaces; per-domain memory learns the user's preference.

Skills & Distribution

The Wiki — pillars

Every wiki page is built from these pillars (each is a tab on the page and a verb family in aw):

CLI Tools

AI-First Rules

EDA Tools & Apps (the daily vocabulary)

Chip Vendors & CAD Sources (spoken shorthand)

Hydrogen (ah) terms

URLs

Naming & Brand Rules

Coordinate System

Adom Hardware

Workcell Types