Architecture

The current architecture has a clear vertical path:

Warp project
  ├─ Cargo code: a Renderer implementation
  └─ warp_app.toml: app, window, assets, and build data
          ↓
Warp Editor or a native project host
          ↓
warp_core runtime
          ↓
RenderContext and scene/render passes
          ↓
wgpu
          ↓
platform graphics backend

warp_core exposes the engine-side contracts. warp_editor is a separate application that can start without a project, open a project manifest, and drive a project through its renderer contract. The source also contains an out-of-process hostlink design; the source comments describe that path as written but not the default project-selection route.

The renderer stays content-agnostic. A project decides what its world means; Warp provides the GPU resources, frame lifecycle, panels, input forwarding, and platform adapters around it.