Client Operations

Entry Gate

Operate a named desktop client only after confirming target process/window/build, adapter capability, screen-session state, foreground constraints, allowed side effects, and evidence boundary. Installation, process, window, menu, and runtime behavior are separate claims. For an app-owned session protocol, bind the executable/protocol/workspace/session instead of requiring a native window; keep backend state and desktop presentation separate. Task delegation, submission, progress queries, waiting and result readback preserve the user's foreground and input state by default. Naming a client as the worker does not authorize GUI interaction; use the background and session routes below.

Reuse existing task authority for requested local client acceptance. An implementation handoff does not require renewed approval; installs, account changes, external writes, and destructive actions still require their own applicable authority.

Route Map