Barfinex glossary

Short definitions of Barfinex terms (Provider, Detector, Advisor, Inspector, Studio, event bus, and more).

Applications

Provider — Central service: connects to exchanges (REST + WebSocket), publishes market data and order events to the event bus, exposes REST API (accounts, orders, candles, connectors, app registry), proxies to Advisor/Inspector/Detector, and provides WebSocket /ws for Studio.
Detector — Signal engine: subscribes to Provider and Inspector events on the bus, runs strategies/plugins, and publishes signals and position requests.
Advisor — Decision layer: subscribes to new signals from Detector, optionally enriches with context (e.g. LLM, risk), and publishes decisions and context snapshots.
Inspector — Risk management: subscribes to Provider and Detector events, monitors positions, manages stops, and publishes risk events when limits are breached.
Studio — Web front-end for monitoring and control: talks only to Provider (REST + WebSocket); reaches Advisor/Inspector/Detector through Provider proxy.

Event bus — Message backbone: all apps publish and subscribe to channels (e.g. market data, signals, risk, decisions). One host/port for the whole ecosystem.
Channels — In Barfinex, a channel is an event name. Messages typically include fields like event type, source, timestamp, and payload.
App Registry — Registry in Provider where Advisor, Inspector, and Detector register via heartbeat; Provider uses it for proxy routing and to show apps in Studio.

Testnet — Exchange test environment (e.g. Binance Testnet). Keys and URLs differ from production; configured separately.
Production — Live environment: real exchange keys and real funds. Requires care over secrets, HTTPS, and network access.

Event types — All event/channel names used on the bus; common prefixes: market data, risk, detector signals, advisor decisions.
Event source — Who emitted the event: Provider, Inspector, Detector, or Advisor; used in event payloads for tracing.

For architecture and data flow, see Barfinex architecture. For API details, see Provider API reference.