Features Pricing Knowledge base
Start free trial Log in
live feedconnecting
Knowledge baseSignals and consensus

Pattern signals, the verdict box and the Signals page

How a chart pattern becomes a signal, the signal states, the verdict box, and filtering or exporting signals.

From pattern to signal

The pattern engine runs on every closed candle of every timeframe. A pattern that just confirmed (completion within the last two bars) is passed through signal fusion: pattern probability from the pair's statistics and the trained model, timeframe confluence, indicator confirmation, derivatives (funding, open interest, long/short ratio, liquidations), order-book context and crash risk. Hard vetoes apply, for example crowded funding, open interest building against the trade, the book stacked against it, or any crash level for a long.

If the fused confidence reaches the threshold and no veto applies, a signal is created: the widget border flashes, the signal sound plays, a popup opens, and the signal panel appears on the widget. Otherwise the pattern stays in the Watching list with its would-be confidence and the first veto.

Only one signal per pair, timeframe and pattern type is raised within the signal cooldown (Settings > Alerts > signal cooldown (min), default 30).

Signal states

State Meaning
confirmed The pattern completed; price has not entered the entry range yet.
active Price entered the entry range; the trade is live.
target_hit TP1 was reached.
stopped The tight stop was crossed.
expired Price never entered the zone within the signal expiry (Settings > Analysis > signal expiry (bars), default 12 bars of the signal's timeframe), or the tight stop was crossed before entry, or an active signal ran six times the expiry without resolving.

Outcomes are recorded with entry and exit price and the unleveraged P&L and feed the Live signal tracker on the Performance page.

The verdict box

On the pair detail page a second coloured block, the verdict box, shows what the pattern engine alone says: OPEN LONG / OPEN SHORT while a signal is confirmed or active, PREPARE LONG / PREPARE SHORT when the best forming pattern would pass the bar if it confirmed, WAIT, NO LONGS under crash warning or critical, and CLOSE LONGS when a long signal is live during a crash warning. Its headline names the pattern, timeframe and the level to confirm above or below, and its note says whether the ranges apply yet (These ranges apply only once the pattern confirms; do not enter before.). The consensus card quotes this headline on its pattern engine: line.

The Signals page

Open Signals in the sidebar for every signal, live and historical.

  • Filter by symbol, state, direction (long + short, long, short) and timeframe (all tf or one).
  • Columns: time, symbol, timeframe, pattern, direction, confidence, entry range, tight stop, TP1, R:R, state, outcome P&L and whether it was marked as Taken.
  • Click a row to expand the Why block (reasons with a plus, vetoes with a minus) and the secondary numbers: chase limit, wide stop, TP1 hit rate, TP2 and its hit rate, expected bars, expectancy, and the recorded entry and exit prices.
  • Refresh reloads; CSV downloads the filtered rows (signals_YYYY-MM-DD.csv) including reasons and vetoes.

New signals and state changes arrive live over the WebSocket, so the table updates without reloading.

Marking a signal as taken

Mark as taken on the signal panel, on the signal popup, or the I took this button on the consensus card, opens the position form prefilled with the direction, live price, the tight stop and TP1 / TP2. Saving it records the order in My Positions and marks the signal as taken for P&L tracking. A taken signal's button changes to Taken · add position so you can record a second entry.

Note: a signal's P&L on the Signals page is the engine's own outcome at the tight stop and TP1, measured from the entry-range mid. Your real result lives in My Positions.