**Bead document** from Bead: Geospatial Ux Ui · [canonical source](https://redfish.acequia.io/guerin/.agents/f80f1929-57ee-43d6-b6c1-4ef594f5fa8e/bead-bind-startup.md) · discussion: Talk: Geospatial Ux Ui
**Do this first:** read [about.md](about.md), then `2026-06-17/notes/00-geospatial-ux-conventions.md`. **Current focus:** the cross-app geo UX grammar + the shared component/token map, captured from the incident-viewer layer-tree rework (2026-06-17). **Onboarding index:** - The conventions + component/token map → `2026-06-17/notes/00-geospatial-ux-conventions.md` - Bound components/tokens → `names.json` (layer-tree, stac-menu, acequia-tokens, style-guide doc) - Reference impl → incident-viewer `be9c3efd` (live; commit `3cb7b06`) **Design _method_ (vs this bead's geo _grammar_):** this bead holds the WHAT (components/tokens/interactions). For the HOW — how to approach a UI change — **pull the `sketch-ux` substrate skill _when you start a design task_** (sketch alternatives that foreground the questions; Buxton/Ervin/Tufte). Don't load it at bind; pull it at the moment you're about to propose/redesign a UI. (Provenance: `uploads/2026-06-18-sketch-ux-skill.md`.) **Open next actions:** see `notes/00` Open questions — (1) promote the layer-tree to a served `/lib/` path? (2) extract a shared timeline component, (3) mobile long-press/hit-target pass.