StrikeGEX
Sign In Start 14-Day Trial
All docs pages

Signals: Graded Order Flow

Signals are institutional options prints that clear a fixed bar, scored 0–100 at the moment they fire, and then graded by one rule that never moves. This page covers the three views in the tab (Feed, Record, Database), how to read a Signal row and its detail panel, and how grading works. Signals is a Pro feature and still in beta: the toolbar carries a BETA · v2 weights label naming the scoring engine version in use.

  • A Signal is one contract, one side, one fill: at least $100K in premium and a score of 60 or higher. One contract fires once per session; later prints on it count as repeats.
  • The score is a confluence measure of how far outside the normal tape the print sits and how well-supported it is. It is not a probability of profit.
  • FEED is today's Signals as they land, RECORD is the graded record, and DATABASE searches every scored print by date.
  • Click any row to open its detail: why it fired, the dealer map at fire time, the grading rail, and prior prints on the same name.
  • Every Signal is graded: WIN, LOSS, or MATURING until it resolves. Nothing is deleted or re-scored.
  • The rule: the option's price prints +25% above the alerted fill before it prints −50% below it, first touch decides, clock runs to expiry.
  • Peak % is the best print seen and is not a return; index/ETF and 0DTE Signals are listed apart.
  • The public record and the full methodology live at /track-record and /methodology once published.
  • Educational context only. None of this is financial advice.
The Signals tab on its Feed view. The header shows a BETA, V2 WEIGHTS badge, the line record building since Aug 18, 2026, and FEED, RECORD and DATABASE view buttons. A filter row offers Score, Side, Type, DTE, Status and Symbol. Each row below lists a time, symbol, contract, days to expiry, a BULLISH or BEARISH side, premium, a score, a one-line read, tags such as SWEEP and REPEAT PRINT, peak and now percentages and a MATURING status.
The Signals FEED view. Each row is one scored print: contract, side, premium, score, the one-line read, its tags, and how the option has moved since (peak and now) with its grading status.

The three views

The toolbar holds the FEED / RECORD / DATABASE switch, an as of time in ET, and a record building since date. The subtitle under the Signals title changes with the view.

What fires

The engine watches our live options feed for single prints that clear a premium floor, then scores each one from a fixed set of inputs: premium tier, aggressor and moneyness, sweep, floor and turnover behaviour (volume against open interest), repeat hits on the same contract, days of runway to expiry, agreement from other prints on the same ticker, an earnings date inside the contract's life, and where the strike sits on the day's dealer-positioning map. The score only uses information that existed when the print landed: a later print or a later dealer map never changes an earlier score. Weights are versioned, and each engine version keeps its own cohort in the record.

A print that scores at or above the threshold becomes a Signal and lands in the feed with the contract, side (BOUGHT or SOLD), premium, score, and a plain-language read of why it scored. Nothing about the fill is assumed better than what printed.

Note Confidence bands (HIGH ≥70, MED ≥50, LOW) are score buckets, nothing more. A HIGH label describes the print, not the outcome. Unusual turnover (high volume against open interest) also does not prove a new position was opened.

Reading a Signal row

Feed, Record and Database rows share one layout. Phones drop the expiry year from the contract so the DTE badge stays visible.

ColumnWhat it shows
TimeFire time in ET. Record and Database rows add the date.
SymbolThe underlying ticker.
ContractStrike, C or P, and expiry. An IDX badge marks index and ETF underlyings, which the record lists apart.
DTEDays to expiry at fire time, or 0DTE for a same-day contract.
SideBULLISH or BEARISH, with the mechanic beneath it (calls bought, puts sold, and so on). Bought means the buyer lifted the offer; sold means the seller hit the bid. Calls bought and puts sold read bullish; puts bought and calls sold read bearish.
PremiumDollars the print represents. Prints of $1M and up are highlighted.
Score0–100 confluence score, computed once at fire time and never revised. A HIGH score shows as a filled badge.
ReadA one-line summary of the print, such as Aggressive put buying — sweep.
TagsUp to three tags, with +N for the rest. Examples: SWEEP, FLOOR TICKET, UNUSUAL TURNOVER, WHALE-SIZE, REPEAT ×3, FIRST PRINT ON THIS STRIKE, EARNINGS, the runway bucket (≤1wk, 1–4wk, 1–3mo, 3mo+), and dealer-map tags such as GEX BREAKOUT, GEX MAGNET, GEX WALL, +γ or −γ.
Peak / NowPeak is the best print seen since the alert in the Signal's direction; Now is the latest mark. Both are a percentage of the alerted fill. Now shows only while the Signal is still maturing. Peak is a high-water mark, never a return.
StatusMATURING while the clock runs; WIN or LOSS once a rail is touched or the contract expires; EXCLUDED (or MULTI-LEG for a multi-leg structure) when it cannot be graded. Excluded rows are dimmed and listed, never rated.

Filters

The filter strip sits under the toolbar. On the Feed it filters the loaded rows instantly; on Record and Database it reruns the search, so the record and the tape reflect the same filters. The Feed shows a count such as 487 of 487. On phones, and on the Record view, the strip folds behind a More filters button that shows how many filters are on.

FilterOptions
ScoreAll, HIGH ≥70, MED ≥50.
SideAll, Bullish, Bearish.
TypeAll, Calls, Puts.
DTEAll, 0DTE, ≤1wk, >1wk.
StatusAll, Live, Maturing, Win, Loss.
SymbolType a ticker to narrow the list.
ResetClears every filter.

The detail panel

Click a row (or focus it and press Enter) to open its detail panel. Esc, the close button, or a click outside closes it. A link of the form /signals?id=… opens a Signal's detail directly.

How grading works

Every Signal is measured against the same rule, applied to every signal in the record: a WIN is the option's price printing +25% above the alerted fill before it prints −50% below it. First touch decides, checked bar by bar from one-minute trade data; a same-bar tie counts as a loss. The clock runs to the contract's expiry, and expiry without +25% is a LOSS. Sold-side prints are inverted the same way.

A rail touched on the day a Signal fires stays MATURING until that day's one-minute data is checked after the close. A Signal can show a peak above +25% during the session and still read MATURING for that reason.

The +25 / −50 pair is a measurement convention, not guidance. It exists so that every Signal is held to one bar, in public, with the misses on the same page as the hits. The target rail was +30% before 2026-08-24; the whole record was re-graded under +25% when it changed (see /methodology).

Tip A MATURING Signal is counted and visible but excluded from every rate. Long-dated contracts can stay open for weeks; the win rate you see is always the resolved set only.

The Record view

The Record opens on the current session. Range presets 1D, WK, 2W, 1M, 3M, YTD and ALL change the window. Date & lane opens From / To dates, a Cohort picker (latest in range, v2 · capture forward, v1 · legacy) and a Lane picker, with Apply and Reset (back to the current session).

The Database view

Pick a From and To date and press Apply; the filter strip applies here too. Rows load in pages with Load more. Open any row to see how many prints hit that name in the last 30 days.

The public record

Warning The record measures source prints against a rule. It is not member returns, not anyone's trades, and it contains no dollar results. Past results do not predict future outcomes; options involve significant risk.

Access and empty states

FAQ

Why did a big print not become a Signal?
Premium alone does not clear the bar. The score needs support from the other inputs (aggressor, turnover, runway, consensus, positioning), and a print that lacks it stays below the threshold.
Can the same contract fire twice?
Not in the same session. A later print on a contract that already fired is folded into the original as a repeat hit (the REPEAT ×N tag), so the feed stays quiet and the original fill is the one graded.
The peak is above +25%. Why is it still MATURING?
A touch on the fire day waits for that day's one-minute data after the close, so the order of the two rails can be checked. Until then the status stays MATURING.
Where is the public page?
At /track-record, with the full rule at /methodology. Both publish once the first cohorts have resolved; until then the Record view inside the platform shows the record building.
Is a Signal a recommendation?
No. It is a measurement of institutional order flow, shown with its reasoning and graded by a fixed rule, for your own read. Nothing here is investment advice.