Feed01
- State
- —
- Last bar
- —
- Mode
- —
- Updated
- —
- feed
- structure
- context
- intraday
- models
- gates
- score
- tracker
Structure draws the map. Gates decide.
Cervo reads NQ futures one bar at a time, waits for the few setups that pass every check, and writes each call into a ledger. It sends alerts. It never places orders.
Look inside the engineMost of the chart is noise. Cervo waits for the bars that aren't.
Every session prints hundreds of candles. Most of them don't matter. Cervo maps where liquidity rests, watches for it to be taken, and only then asks whether a trade is worth sending.
Most days the honest answer is no. A quiet day is the engine working as designed, not a gap in coverage.
How it works
Structure draws the map.
Twelve gates decide.
The ledger remembers.
Deterministic
Every decision is plain code. The same bars always give the same score and the same answer. No language model sits in the decision path.
Accountable
Every alert becomes a virtual trade, tracked to its exit with its score, its gates and its reasons. Losses stay in the record.
The Cervo engine: eight stages around a central hub, from the data feed to the trade tracker.
BuiltIn progressPlannedHover or tab through the stages.
A setup, step by step
The setup comes to the engine. The engine waits for the reaction.
Cervo doesn't predict. It waits for liquidity to be taken, then checks whether the market's answer is strong enough to trade.
STEP 01 / 03
Illustration of how a setup is built. Not market data.
Map
Structure draws the map.
The engine marks swings and where liquidity rests: here, a cluster of lows the market is likely to run.
Test
The sweep, then the reaction.
Price takes the lows and snaps back with displacement. That leaves a point of interest. Twelve gates and the score decide whether it counts.
Plan
A zone, a stop, three targets.
If every gate passes, the alert carries an entry zone at the POI, a stop beyond the sweep, and targets at 1R, 2R and 3R. The tracker follows it to the exit.
Live view
Inside the engine, as it decides.
When the engine is running, this panel shows what it sees: feed health, today's bias, the last setup it analysed, which gates it passed and the score that decided.
Placeholder · engine not connected
Today's brief02
- Bias
- —
- Regime · day type
- —
The pre-market brief sets the bias at 09:30. Gate 4 refuses any trade against it.
Last decision03
—
—/ 100
Waiting for the engine.
Gate rail04
Twelve gates, in order. One failure stops the trade.
01 Time12 Score
Hover or tab through the gates.
Score anatomy05
Signal threshold70 / 100
Selectivity
Hundreds of events a day. A handful of alerts. Sometimes none.
Every structure event wakes the engine. Each one is scored and gated, and nearly all of them end as NO_TRADE or WATCHING.
That ratio is the product.
Events vs. alertsIllustration
A session, filtered
Events analysedBecame alerts
Shape only, not real counts. Real counts replace this once the engine exports its decision log.
Two modelsREV · CONT
Reversal at external liquidity, or continuation with the flow.
ResultsPlaceholder
Every alert is tracked as a virtual trade.
See the recordStructure draws the map. Gates decide.
Follow the build as each stage of the engine comes online, and watch the live view when it does.
How the engine decides