Deployment placement
Server runs where FastSim and the selected Provider are available. Browsers, TUI, automation clients, and MCP gateways may live in other processes or machines and depend only on the public protocol.
Discover capabilities first
Clients read health, version, run state, and capabilities before presenting scene, camera, geometry, kinematics, or control features. Endpoint existence does not guarantee that every Run and Provider supports an operation.
Lifecycle and generation
Remote start, pause, reset, and stop still traverse Application lifecycle. Control requests and Operations bind to the current run/generation; clients must refresh state, targets, and subscriptions after reset.
Security boundary
- Listen addresses, authentication, and reverse proxy configuration belong to deployment.
- External writes require explicit authorization; read-only discovery does not imply control.
- Browsers do not load backend objects or unrestricted asset trees.
- Production deployments constrain trusted output roots, upload sizes, sessions, and operation budgets.
Server REST API is generated from the current plugin source. Runnable cases live in Examples and tutorials, but protocol contracts follow the reference and package version.