# Editor Capabilities Map This file is a shorthand capability matrix for request analysis. It is intentionally less detailed than the source code, but more concrete than the original scaffold summaries. ## Tile Canvas Editing - Owned primarily by `Layers And Tile Editing` - Supports: - freehand tile painting - rectangle and circle outline strokes - line strokes with axis lock - erasing on the active layer - sparse height-layer paint and erase workflows - background-cell modes for explicit tile, transparent hole, and inherit - Depends on: - `Chunk Storage And Streaming` - `Content Catalog And Records` - `Persistence And Save Pipeline` - `Rendering And Viewport` ## Graphics Painter - Owned primarily by `Graphics Painter` - Supports: - rectangle, circle, triangle, and line tools - outline, fill, and outline + fill variants - shape erasers - animation timeline editing and preview - transform-oriented tool menus - Depends on: - `Content Catalog And Records` - `Floating Window Shell` - `Rendering And Viewport` ## Chunk Operations - Shared by `Chunk Storage And Streaming` and `World Overview` - Supports: - neighborhood chunk loading - chunk composition into the current world edit surface - chunk move, duplicate, rotate, flip, and delete - chunk background tile paint and restore - bookmark and POI workflows - Depends on: - `Persistence And Save Pipeline` - `Worlds` - `Windows` ## Request Review - Owned primarily by `Request Board` - Supports: - public submission intake - standardized tag assignment - structured review rationale - possible options for manual triage - admin-side edits and approval - queue worker invocation - Depends on: - `Launcher` - `Wiki` - request-analysis worker and KB files ## Relationship Rules For Triage - If a request asks for how a brush or rectangle tool behaves on the map canvas, start with `Layers And Tile Editing`. - If a request asks for how a rectangle or shape tool behaves inside the art editor, start with `Graphics Painter`. - If a request asks about chunk movement, chunk duplication, or world-scale operations, start with `World Overview`, then confirm any storage implications in `Chunk Storage And Streaming`. - If a request is mostly about presentation, launch flow, repo links, or public site layout, start with `Launcher Home`.