Glossary

  • Action — a control's outbound behavior (device → server). Declared as action on the control; rides broadcast_request or route_msg. See Data Flow — sync & actions.
  • Broadcast — fan-out delivery. A client sends broadcast_request; the relay re-emits a broadcast frame to the channel. The backbone of telemetry.
  • Channel — a namespace on the relay. Members see each other's broadcasts and can route to each other. On the gateway, channels are namespaced per account.
  • Connect+ gateway — the hosted, authenticated, slot-metered service wrapping the relay; uses wss:// and a token. See Connection & Pairing.
  • Control — a single UI element (gauge, button, …). See Control Catalog.
  • Device — a phone/iPad running the CAR-TER app; a thin client that renders a layout and speaks MeshSocket.
  • E2EE key — an optional shared base64 symmetric key for end-to-end-encrypted forwarding (e2eeKey / QR k); the relay forwards ciphertext it can't read.
  • Editor / live-edit — a transient authoring session (started by scanning an editor QR) where the device renders editor-pushed layouts and exposes read-back responders. See Live Editing & the MCP Authoring Loop.
  • Filter — a sync field; shallow key/value match used to select which broadcast frames a control consumes (usually keyed on msg_type).
  • Frame — one MeshSocket message: { id, type, payload, reply_to }.
  • Group — a container control with its own grid of children; can be dynamic.
  • Identify — the first frame a client sends, announcing name/channel/role/ capabilities. See Message Reference.
  • Layout — the JSON document the app renders: tabs → grid → controls/groups. See Layouts / Layout Schema.
  • MCP server (carter-mcp) — lets an LLM read control docs and build/push layouts to a paired device live. See Live Editing & the MCP Authoring Loop.
  • MeshSocket — the WebSocket message protocol/relay CAR-TER uses. See The MeshSocket Protocol.
  • msg_type — by-convention discriminator inside a broadcast payload; how controls and servers tell traffic apart.
  • Pro / premium — the gated controls/features (theming, pulse, and 11 controls). See Control Catalog.
  • Relay — the MeshSocket message router. Self-hosted (ws://) or via the Connect+ gateway (wss://).
  • Role — a member's label (viewer, controller, hub, editor, node); also sets capability defaults at the relay.
  • Roster — the channel's member list; fetch reliably with get_nodes.
  • Routed RPC (route_msg) — point-to-point request/reply between two members.
  • sync — a control's inbound subscription (server → device). Declares event, filter, valuePath. See Data Flow — sync & actions.
  • valuePath — dot path into a payload to extract a control's value.
  • {{value}} — token in an action payload, replaced with the control's current value (native type when the whole string is exactly "{{value}}").