Barfinex architecture - how the system is built

Overview

Barfinex is built as a set of specialized services connected through Provider. Each service owns one part of the trading lifecycle, which keeps market data, signal generation, deterministic policy admission, risk control, and operations UI separate but auditable.

Service roles

Provider

Provider is the single gateway for runtime data. It normalizes exchange data, serves REST and real-time APIs, and exposes the public integration boundary for Studio and external clients.

Detector

Detector evaluates strategy rules and produces trading signals. Multiple detector configurations can run for different symbols, intervals, or market regimes.

Advisor

Advisor validates an immutable Detector candidate and signed Provider evidence against a pinned deterministic policy. It records ADMIT or REJECT with an immutable basis. It performs no AI reasoning, market analysis, sizing, or risk calculation.

Inspector

Inspector applies risk policy before any intent can become an order. It manages position safety, exposure checks, protective behavior, and post-trade audit.

Studio

Studio is the operations terminal. It observes the system through Provider, showing charts, candidate lifecycles, Advisor policy decisions, and Inspector risk dashboards.

Integration rule

Public clients and Studio use Provider as the gateway. Direct service ports, private events, internal queue names, and secret configuration belong to the internal trading workspace documentation.

Next steps

• Provider API reference
• Building with the API
• Signal pipeline