Nexus Engine

An operating system
for trading decisions

Eight stages run on every candle close, in the same order, every time. Data comes in raw and leaves as an order or a written reason there wasn’t one — and every intermediate state is kept, so any decision can be replayed exactly as it was made.

8

pipeline stages

< 80 ms

close to order

100%

decisions recorded

nexus-engine · telemetrynominal
feed.frames1840/s
vector.build2.8 ms
ensemble.p9541 ms
risk.checks13 / 13
decisions.h404
routed.h11

pipeline online · 8 stages · deterministic replay enabled

The pipeline

Close to order, one path only

stage 01

Ingest

Websocket and REST feeds from every connected venue are normalised into one internal candle and book representation, checked for gaps and duplicates, and stamped with the venue clock alongside ours. A strategy never sees a venue's quirks.

inraw venue frames
outnormalised OHLCV + book
budget< 4 ms
Decision engine

Three models. One arbiter. No averaging.

Averaging disagreement produces a number that no model would have chosen. The arbiter instead weighs each model by how well calibrated it has been in the regime the market is currently in — so a momentum model that is unreliable in compression is quietly demoted rather than allowed to vote.

SOL/USDTtrend · expanding
Structure88

market geometry

weight
0.42
Momentum84

regime-conditioned

weight
0.40
Analogue71

memory recall

weight
0.18
83convictionROUTEbar · 72

arbiter rationale

All three agree; momentum is well calibrated in expanding trend, so it carries near-equal weight.

weighted score83
threshold72
risk envelopeclear

representative decisions · not live market data · hover to pause

Data flow

Always on, and always narrow

Roughly eighteen hundred frames a second come in. Four hundred decisions an hour come out of the arbiter. Nine of them become orders. The funnel narrows by design — the engine's job is mostly to decide against doing something.

market data
1.8k/s
feature vectors
1.8k/s
decisions
412/h
fills
9/h
Architecture

Services, not a script

Each box is a separately deployed service communicating over an event bus with replayable envelopes. The consequence that matters is the one on the right: there is no edge from the engine to execution that does not pass through risk.

recallapproved onlyVenue adaptersws · restEvent busenvelope · replayNexus Engine8-stage pipelineMemory storetrades · lessonsRisk service13 rules · vetoExecutionrouting · fillsno bypass path exists
edge servicecore serviceguarddurable store