← Commit history

restructure: top level = ecosystem-wide; HD-specific terms (golden image, setup cascade, virgin reset, ESM) in their own lower section

John Lauer ·b733e59eba ·3mo ago ·parent 4c1367c
1 file changed +10−3
README.md+10−3
@@ -9,10 +9,9 @@ Canonical glossary of Adom platform terms. Use these definitions consistently in | **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, components, 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. | | **Adom App** (aka **Workspace**; team shorthand **hw** = "Hydrogen Web") | The full web app: toolbar, panels, VS Code, profile. Internal codename "Hydrogen" — the team says "hydrogen web"/"hw" to distinguish it from hd. "Workspace" also names the persistent environment itself (cloud: a Docker container; under hd: the local WSL2 `Adom-Workspace` distro). Public-facing name stays "Adom App". |-| **Hydrogen Desktop (HD)** (casual: **hd**) | The Windows/macOS desktop app — the flagship Adom experience. Runs the workspace LOCALLY (Windows: WSL2 `Adom-Workspace` distro; macOS: Lima). Bundles Adom Desktop. Signed installer; a 27-step first-run cascade builds the workspace from the golden image. |+| **Hydrogen Desktop (HD)** (casual: **hd**) | The Windows/macOS desktop app — the flagship Adom experience. Runs the workspace locally and bundles AD. HD-specific terms: see the Hydrogen Desktop 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. | | **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. |-| **Golden image** | The pre-baked workspace rootfs (`adom-golden-vN.tar.gz`) that HD imports on first run — code-server, the Adom CLIs, extensions, settings, and all bundled skills, pre-converged via one `adom-wiki pkg install` of the platform bootstrap at bake time. The bake is an optimization of the runtime flow, not a different mechanism. | | **Panel** | A rectangular area of the Adom App layout — 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)@@ -68,7 +67,6 @@ Canonical glossary of Adom platform terms. Use these definitions consistently in | **fake-view** | Any static SVG/HTML/screenshot that approximates a real app without running it. BANNED. If you're about to fake it, stop and run the real thing with sample data. | | **AI-drivable** | Every Adom app exposes state + control to the AI (GET /state, GET /console, a live SSE/WebSocket channel, CLI verbs) so the AI can drive, verify, and ralph-test it. See the ai-driven-apps skill. | | **Ralph loop** | The AI's visual QA loop: drive a step, screenshot, read, fix, repeat until the UI is right — no human in the loop. |-| **ESM** | The Editor State Machine — HD's authoritative editor-state read (`GET /editor/state`): lifecycle, layout/bars, tab census, disk-backed conversation truth, and the typing cardinality gates (exactly one compose box, stray audits, disk-verified delivery). |  ## EDA Tools & Apps (the daily vocabulary) @@ -100,6 +98,15 @@ Canonical glossary of Adom platform terms. Use these definitions consistently in | **ul** | Ultra Librarian — CAD-model source | | **cse** | Component Search Engine (SamacSys) — CAD-model source | +## Hydrogen Desktop (hd) terms++| Term | Definition |+|------|-----------|+| **Golden image** | The pre-baked workspace rootfs (`adom-golden-vN.tar.gz`) HD imports on first run — code-server, the Adom CLIs, extensions, settings, and all bundled skills, pre-converged via one `pkg install` of the platform bootstrap at bake time. The bake is an optimization of the runtime flow, not a different mechanism. |+| **Setup cascade** | HD's gated first-run steps (currently 27): import the golden image, inject identity, wire the relay, install the `claude` CLI (the one runtime install), walk Claude auth, then open the welcome + named AI-thread conversations. Every step is a hard gate — it verifies its artifact or halts. |+| **Virgin reset** | Wiping the workspace back to first-run through HD's own visible reset panel (never out-of-band). Rebuilds from the golden image. |+| **ESM** | The Editor State Machine — HD's authoritative editor-state read (`GET /editor/state`): lifecycle, layout/bars, tab census, disk-backed conversation truth, and the typing cardinality gates (exactly one compose box, stray audits, disk-verified delivery). |+ ## URLs  | URL Pattern | What it is |