Nexus Engine

An operating system
for trading decisions

Every closed candle takes the same path, in the same order: data, context, strategy, quality score, sizing, risk checks, a paper fill and the record. It leaves as a paper order or a written reason there wasn’t one — and the reason is kept.

8

steps, one path

7

production strategies

Every

candle written down

nexus-engine · how it runspaper
dataBinance USDⓈ-M
decides.onclosed candles
strategies7 prod · 4 research
qualityscore 0–100
riskevery order
live.routinglocked

▸ paper mode · 8-step path · every candle written down

The pipeline

Close to order, one path only

stage 01

Data

Binance USDⓈ-M candles arrive over one shared websocket hub, with REST history to warm indicators up. A candle is only used once it has closed, and a stale or out-of-order feed pauses new entries rather than trading on it.

inBinance stream + history
outclosed, verified candles
recordsmarket state · freshness
Decision engine

One quality score. Every factor written down.

The strategy decides where a trade could be; the Decision Brain decides whether it is worth taking. It scores the setup out of 100 from eight weighted factors, keeps the list of rules it passed and failed, and refuses some setups outright whatever they score.

Quality scoreweights sum to 100
  • Higher-timeframe alignment22

    the bigger trend agrees with the side

  • Regime fit18

    the regime suits the setup

  • Reward : risk14

    ≥ 2 scores best; below 1 is blocked

  • Momentum12

    RSI supports the side, not exhausted

  • Stop safety10

    neither absurdly tight nor wide

  • Volatility10

    ATR% in a tradeable band

  • Structure8

    price on the right side of the structural EMA

  • Volume6

    participation confirms the move

Grades
80 – 100High
60 – 79Acceptable
0 – 59Weak
Blocked whatever the score
  • Reward : risk below 1.0
  • Stop too tight or too wide
  • Volatility far too low to trade
  • Strong higher-timeframe trend against a non-reversal trade
  • Choppy or unclear regime for a non-reversal trade
  • Losing-streak cooldown
Data flow

Always on, and always narrow

Every closed candle on every running instance is read and judged. Most end as WAIT with a written reason; a signal must then clear the quality score and every risk check before it becomes a paper order. The funnel narrows by design — the engine's job is mostly to decide against doing something.

closed candles
every candle
signals
some candles
approved
fewer
paper fills
fewest
Architecture

One path to an order

Nexus runs as one application with a worker per Trading Instance, all fed by a single shared Binance hub. The consequence that matters is the one on the right: nothing reaches the broker without passing the risk checks, and the broker is paper — live order routing is locked.

loss streakapproved onlyBinance hubws · rest warm-upWorkerone per instanceStrategy + Brainsignal · scoreLedgertrades · decisionsRisk checksevery orderPaper brokersimulated fillsno bypass path exists
data in · fills outdecisionguardstorage