Interface map

A lookup for the interface. Each entry says what the surface is for and points at the page that documents its controls in depth. The shortcut table at the end is the complete set.

Three screens#

Dayside has one window and three screens. The project decides which one you land on.

The setup wizard is a route (#/setup) rather than a screen: it layers over whatever is behind it and makes the app behind it inert.

Worlds picker#

The front door. Documented in Your first world.

Globe workspace#

The whole-world screen. Documented in Working on a globe.

Top bar#

Stage and tools#

Globe tools is a three-way exclusive toolbar: Rotate orbits the sphere, Box drags a longitude and latitude box, Lasso draws a freehand polygon. The Globe and Flat toggle sits in the actions row beside About & credits and Enhance world.

The stage itself takes focus and handles G, F and Escape. The globe canvas and the flat surface each have their own key set; both are in the shortcut table.

Canvas overlays#

Side panel#

The pipeline glance on a region card is always in this order: Rough terrain, Terrain detail, Analytic colour, Learned enhance.

Job dock#

Bottom left, one card per long-running globe job: Rebuild globe, Re-compose globe, Colour globe, Enhance world terrain, Create region. Cards persist through Queued, Running, Done and Failed, so a modal you closed can never read as success.

A running card shows stage and percent, a failed card shows the reason plus a Try this: fix, and a finished card shows its duration. Cards offer Cancel, a retry (Retry, or Refresh for a region creation) and a dismiss. Every card carries a scope and subject tag so a button and its job card always agree.

Footers#

The panel footer states READY n/N and the next export size, and holds Re-compose globe (enabled only when the globe is stale) and Export globe. The globe footer is one mono line: status, region count and scale.

Section editor#

Top bar#

Most of these disable each other: nothing in the row is available while a render, a generate, an enhance or a paint commit is in flight.

Left rail#

Fifty-six pixels wide, top to bottom.

Every rail button except About & credits is disabled while a paint commit is running.

Canvas#

Pan by dragging, zoom from 0.6 to 3.0 in steps of 0.25, and a Zoom in / Zoom out / Fit cluster bottom right. The compare divider is clamped between 4 % and 96 %.

The canvas states the render's phase on itself rather than in a panel: ACQUIRING · N% with a pass and resolution readout, QUEUED with a queue position and Prioritise / Cancel, PREVIEW STALE · N CHANGED with Re-render, a failed pass with a retry, NO ACQUISITION YET, or an ACQUIRED chip. In Draw mode it instead reports LOADING HEIGHTFIELD…, CANNOT PAINT, or the coastline preview's state.

Heads-up display#

Mounted only in Draw mode with the Draw tool. There is no equivalent readout in Render mode.

Controls behind these readouts are in Painting terrain and Terrain and generation reference.

Control panel#

Three hundred and forty-four pixels wide, on the right, headed Controls. Acquire and Compare A/B are pinned to its foot in both modes.

In Draw mode it holds the paint stack:

In Render mode it holds the look stack, all of it documented in Colour and climate reference:

Every slider commits on release, and every commit marks the preview stale. Groups whose inputs are inert say so: the flow widening, green banks, river strength and every lake control grey out when Rivers is off.

Footer bar#

One mono strip: world name, EXTENT w x h km, an engine pill and the zoom level. The engine pill reads QUEUED · POSITION n, ACQUIRING N%, PREVIEW STALE, PASS FAILED or ENGINE IDLE. The extent quoted is your own selection, before the raster padding.

Global chrome#

Status strip#

Mounted above every screen, so a warning is never editor-only. Three rows, worst first:

1. Engine offline, with a message, a fix and a dismiss. Suppressed on the picker when the workspace takeover already owns that state.
2. Notice, one line per engine or API warning, each dismissible.
3. Reconnecting to the engine…, shown only after the socket has been down for more than one retry cycle, with a world open, and no offline row showing.

Edit-proxy banner#

Sits under the top bar when a section is being edited through a working-resolution proxy. It states the working resolution, the native size and the count of edits not yet baked, and offers Bake to native and Discard. On resume it instead offers Edit at 4K and Change…

The bake is always an explicit button. It never fires on its own. See Enhancing terrain.

Modals#

The acquisitions drawer is not a modal. It slides in from the top-bar inbox button, is mounted in both the editor and the globe workspace, and lists every export with its status, its files and its Gaea handoff numbers.

Words the interface uses consistently#

Action verbs are fixed. Acquire and Re-render start a section render; Render section colour produces the analytic base; Enhance section colour is the per-section learned pass; Generate terrain is section diffusion; Enhance world terrain and Colour globe are the two whole-world passes; Re-compose globe and Update globe fold edits back in; Bake to native replays proxy edits onto the master.

Every action header and job card also carries a scope and subject tag, formatted WHOLE WORLD · TERRAIN or SECTION · AI, so you can always tell what a running job will touch.

Keyboard shortcuts#

Every shortcut in the app. All of the Draw-mode keys are suppressed when focus is in a text field, a text area, a select or a contenteditable element.

The export, generate, deterrace and import modals have no Escape handler. Close them with their own close button. Deterrace additionally refuses both the close button and a backdrop click while a run is in flight.