Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Reference editor architecture

The editor is a client of the same semantic engine used by CLI/API tooling. The shell technology is decided in ADR 0006 (accepted): a Rust-native shell on Masonry, Vello and AccessKit; the Svelte 5 shell below is retained as the browser demonstration path. The user-interface specification is UI-SPEC.md.

Rust shell (Masonry widgets, AccessKit tree) — or Svelte 5 shell over WASM for the browser demonstration
        │ typed commands/events
        ▼
Rust core (in-process; WASM boundary only in the browser build)
  ├── document store
  ├── protocol/transactions
  ├── layout evaluators
  ├── render-scene builder
  ├── query/diagnostics
  └── codecs
        │
        ▼
renderer backend (WebGPU/Vello experiment)

The UI shell may keep ephemeral selection, viewport, focus, panel and inspector draft state, but authored document state is NUIF state. The shell MUST retain this ephemeral state independently of adaptive composition. A composition change MUST NOT change the selected entity, evaluation context, viewport transform, operation-history cursor, inspector drafts, capability report or fidelity diagnostics. Canvas gestures MUST translate into semantic protocol operations before mutation.

The native shell is the reference editor surface. A later Svelte 5 shell is a browser demonstration and MUST NOT become an alternative owner of editor state or an independent user-interface contract.

Package loading has a separate capability boundary. The editor structurally verifies and preserves every package resource and declares only the tested nuif-opentype-variable-truetype-single-0 decoder capability. Those packages use the resource-aware snapshot and save paths; a package with any other unsupported required capability opens inspectable and copyable but read-only. Both the shared editor driver and package-save boundary reject semantic changes to an unsupported package, preventing an opaque resource from remaining attached to a document revision it was not validated against.

The editor must expose a local automation endpoint or in-process API that mirrors CLI semantics. MCP may be added as an adapter, never as the canonical automation contract.

Canonical source.