Skip to content

Glossary

Terms are normative: code, docs, and protocol fields use these words with exactly these meanings. Add here first; then use.

TermMeaning
AgentThe Fjarr process on the robot: libfjarr embedded in the customer’s software, or the fjarr-agent reference daemon.
CapabilityA pluggable unit of functionality (camera video, remote desktop, file transfer…). Owns media tracks and/or DataChannel message namespaces. See docs/05.
Capability consumerWhoever the capability serves: a peer consumer (a dashboard connected P2P) or the backend consumer (observability ingest, OTA orchestration).
SessionOne WebRTC peer connection between an agent and one operator client, carrying whatever capabilities were granted. Identified by session_id.
Session grantThe short-lived signed token (JWT) minted by the customer’s backend that authorizes creating a session with specific capabilities. See docs/09.
SignalingThe message exchange (offer/answer/ICE) that establishes sessions, relayed by fjarr-server. Never carries media.
Sidecarfjarr-server deployed next to the customer’s backend, per ADR-0015.
Fjarr CloudThe managed, multi-tenant implementation of the same contract as the sidecar.
EnvelopeThe single tagged-union message format used on control channels; every message has type, event_id, and a payload. See docs/08.
Correlation (event_id)Requests carry a unique id; responses echo it. Long operations reply accept → feedback* → result, all with the same id.
TrackOne WebRTC media stream (e.g. one camera, one monitor). Announced in the track manifest before media flows.
Track manifestMetadata listing every track in an offer (track_id, label, kind, codec, payload type) so UIs can label streams before frames arrive.
Producer pipelineThe persistent GStreamer pipeline owning capture + encode. Survives peer churn.
Consumer pipelineThe disposable per-session pipeline feeding one webrtcbin.
FrameHubThe fan-out between producer and consumer pipelines: encode once, serve N sessions.
DCWebRTC DataChannel. Fjarr defines reliability classes per channel (docs/08).
Robot IDThe customer’s canonical identifier for a device. Fjarr never invents its own device identity; it authenticates the customer’s.
TenantOne customer organization in a multi-tenant fjarr-server/Cloud deployment.
Relay / TURNMedia forwarded through coturn when direct P2P fails. Ephemeral HMAC credentials only (docs/10).
PortalXDG Desktop Portal — the D-Bus permission layer for Wayland screen capture and input.
EIS / libeiEmulated Input (server/library) — the Wayland-native input injection path.
uinputLinux kernel interface for creating virtual input devices below the display server.
Backend consumer flowsRobot↔backend traffic that is not P2P: observability ingest, OTA campaign control.
Store-and-forwardThe agent’s bounded offline buffer for durable events, replayed on reconnect (whitelisted types only).
DeadmanA safety timeout that stops actuation when control input goes silent. Spec’d and tested, never incidental (docs/15).
ADRArchitecture Decision Record — docs/adr/.