Desktop Explorer

Given an approved computer plan, how is work represented on a native desktop (apps, windows, OS-level input) independently of any provider? Structure only — the runtime dispatches no OS input and reads no screen. Approval-aware. Read-only.

Sessions

Windows

Actions

Approval barriers

Native app controlready

1 app · 1 window · 5 action · 2 control

launch_appactivate_windowclicktype_textkey_combo

Window managementready

1 app · 2 window · 4 action · 1 control

move_windowresize_windowdragset_window_state

Accessibility inspectionready

1 app · 1 window · 1 action · 2 control

read_accessibility

Untrusted app + closewaiting_approval

1 app · 1 window · 3 action · 1 control

activate_windowclipboard_transferclose_window1 untrusted1 destructive2 approval

The Universal Desktop Runtime owns native desktop semantics (applications, windows, controls, actions, expectations, artifacts) as provider-agnostic metadata. It dispatches no OS input, reads no screen, launches no process, and opens no accessibility API; expectations carry only reference tokens (nothing on-screen is captured); windows/controls are declared structure, not observations. Real desktop control is owned by the future Broker, gated on a binding Policy allow, with computer-use backend choice owned by the Provider Runtime (M38).