Definitions

@@ -13,7 +13,6 @@ Canonical glossary of Adom platform terms. Use these definitions consistently in | **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. |-| **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. | | **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)