Signal Pipeline - Detector to Advisor to Inspector

Overview

The Barfinex signal pipeline separates trading automation into clear stages:

1. Provider receives and normalizes market data.
2. Detector evaluates strategy rules and emits signals.
3. Advisor applies a deterministic ADMIT or REJECT policy to each immutable candidate and its signed evidence.
4. Inspector owns final sizing, risk policy, and execution safety checks.
5. Provider remains the gateway for order and runtime integration surfaces.

This separation makes the pipeline observable: a signal can be generated, admitted, rejected, resized by Inspector, or sent for execution with a visible reason.

Detector

Detector focuses on signal generation. It evaluates technical, market-state, and strategy-specific conditions, then emits structured signal context for downstream decisioning.

Advisor

Advisor validates the candidate and signed Provider evidence against a pinned deterministic policy. It records an immutable decision basis and forwards only admitted candidates. It performs no AI reasoning, market analysis, sizing, or risk calculation.

Inspector

Inspector is the final authority. It calculates size and evaluates exposure, drawdown, account state, liquidity, and execution safety before any order can proceed.

Public boundary

The public website describes product behavior and integration surfaces. Exact internal event names, ports, env variables, service classes, and queue semantics are maintained in the internal trading workspace documentation.

Next steps

• Barfinex architecture
• Provider API reference
• Advisor overview