Skip to content

Concept → implementation map (English, Flight-focused)

Scope: how the current Flight layout (PFD · Forward · MFD) maps to code. Legacy Focus / Balanced / Power PNG concepts are archival — many rows below describe old presets, not the shipping UI.

Code anchors: Views/MainWindow.axaml, MainWindowViewModel partials, TaskCockpitView, MfdShellView, MfdShellPageStack. Full bilingual table (legacy sections): Russian version.

Legend

Status Meaning
Implemented
🟨 Partial / heuristic data
Not implemented

1) Flight — global layout (shipping)

Concept XAML / code Status Notes
Three columns PFD · Forward · MFD MainGrid ColumnDefinitions="220,4,*,4,340" Splitters; PFD/MFD can collapse per VM.
Forward = editor dock DocumentsDockView in Zone="Forward" Primary code surface today (default).
MFD = page stack MfdShellView, MfdShellPageStack Build, terminal, Git, chat page, IDE Health, …
No bottom panel across window Unlike legacy mockups; streams on MFD pages.
Single UI mode Flight UiModes/index.toml No Focus/Balanced/Power product switch.
Command palette CommandPaletteHost Complements Intercom slash commands (ADR 0119).
Intercom / chat MFD page + Skia surface See ADR 0044.
Intercom in Forward (Cursor-like) ❌ Proposed ADR 0120.
Slash commands in chat input ChatInput + slash autocomplete ADR 0119; parametric/workspace: 01240126.

2) Multi-monitor (ADR 0017)

Concept Code Status
presentation line in settings PresentationParser, VM
Secondary Mfd window MfdHostWindow
Secondary Pfd window PfdHostWindow
Hide duplicate column when host open layout VM

Details: ADR 0017.


3) Legacy Focus / Balanced / Power

PNG files under concept-generated/ and sections §2–§4 in the Russian map describe historical presets. Do not assume they match the Flight binary without checking this table and UI layout v1.


Next alignment (product backlog)

  1. Dependency mini-map (Balanced-era idea) — not in Flight scope yet.
  2. Deeper IDE Health / cockpit metrics — ongoing.
  3. Power-style visual polish on tree/editor — partial; see Russian map §4.1.

For MCP and automation, prefer UI layout v1 control names.