Advisor - deterministic policy stage

What the Advisor is

Advisor is a deliberately small policy boundary. It validates an immutable Detector candidate together with signed Provider evidence and returns one of two outcomes: ADMIT or REJECT.

It remains a separate internal service so there is one independently observable, fail-closed admission and publication boundary. It is the sole runtime publisher of the Inspector handoff.

Advisor does not analyze the market, call an AI or LLM, score confidence, create strategies, size positions, manage risk, or place orders. Those responsibilities belong to Detector, Provider, and Inspector.

Decision flow

At a high level, Advisor:

1. receives an immutable candidate produced by Detector;
2. verifies the candidate shape and signed Provider evidence;
3. applies a pinned, deterministic admission policy;
4. appends the ADMIT or REJECT decision and its immutable basis to the Provider-owned Trade Journal;
5. hands admitted candidates to Inspector through a durable outbox.

That handoff is an ADVISOR_EXECUTION_CANDIDATE, not an exchange order. Inspector alone calculates executable quantity, notional and leverage before the Provider execution path can submit an order.

Why it matters

The stage exists to preserve a narrow governance boundary and a reproducible decision basis. It cannot silently reinterpret Detector logic or take over Inspector authority.

Studio shows the lifecycle and the recorded policy reason. Final sizing, risk review, and execution truth always come from Inspector.

Integration boundary

Public clients and Studio use Provider-owned, read-only Advisor-stage routes and Provider real-time surfaces. There is no public Advisor control, strategy, analytics, or deployment API.

Next steps

• Barfinex architecture
• Advisor API reference
• Inspector overview