Window Explorer

Given an approved computer plan, how is work represented across native windows, displays, workspaces, focus, and dialogs independently of any OS or provider? Topology only — the runtime manages no real windows and queries no display server. Approval-aware. Read-only.

Sessions

Displays

Ops

Approval barriers

Multi-display arrangementready

2 display · 3 workspace · 3 window · 5 op

move_to_displayarrange_windowsnap_windowtile_layoutmove_to_workspace

Focus & stackingready

1 display · 1 workspace · 3 window · 4 op

focus_windowcycle_focusraise_windowlower_window

Topology inspectionready

1 display · 1 workspace · 1 window · 1 op

query_topology

Dialog modalitywaiting_approval

1 display · 1 workspace · 1 window · 3 op

open_dialogdismiss_dialog1 system-modal1 destructive2 approval

The Universal Window Runtime owns windowing-system semantics (displays, workspaces, managed windows, dialogs, focus chains, z-order) as OS-agnostic metadata. It manages no real windows, moves no focus, opens no dialog, and queries no display server (no X11/Wayland/Quartz/Win32); topology is declared structure, expectations carry only reference tokens. The seam vs the Desktop Runtime (M48): Desktop owns the input act, Window owns the windowing-system state. Real windowing is owned by the future Broker, gated on a binding Policy allow, with backend choice owned by the Provider Runtime (M38).