Deep Dive

Remote

Valkyrie remote is designed as an operator stack: composited capture, authenticated session control, attach/detach persistence via agent, and viewer role governance.

Topology

Valkyrie remote_server plugin
        -> remote agent daemon
          -> native viewer (SDL)
          -> web viewer (browser)

One control owner at a time, explicit claim/lease semantics, and output switching policies enforced server-side.

Security + Control

Auth Modes

token
OTP generation/revoke
identity-backed agent auth

Control Roles

Viewer can be `view-only` or `control`; control claims are visible and revocable.

Live Ops Knobs

Output switch, bitrate/latency tuning, audio codec/mute/duck, kick/kick_all, and state introspection.

Performance Philosophy

Adaptive transport is tuned for responsiveness first. When conditions degrade, server and client reduce complexity before sacrificing session continuity.