A session’s notable prints on tracked tickers, each joined to the open interest its contract actually settled the next morning, and stamped opened, closed, rolled, unresolved or pending. The question a print raises is answered by OI, never by the print itself.
No alerts are stored for 2026-09-22. The collector runs at 21:15 ET, so a session is empty here until that evening. The latest session with alerts is 2026-09-21.
No rows: this session has no stored alerts.
n. A verdict rate’s n is the number of distinct CONTRACTS, not prints, because prints on one contract share one settled change — the flow analogue of overlapping forward windows shrinking an effective n. Below n_min 20 the summary shows counts and no percentage.
Cost: three queries — the session, then the prints and the coverage together. Only point lookups touch core.option_strikes: rows D and D+1 by full primary key per contract, the persistence series by full key per later session, and — new, for the default above — the newest as_of_date per tracked symbol, a primary-key prefix read each. Measured on production 2026-09-16 at 18:53 ET: the session query 34–40 ms warm (62 ms cold), the prints query 240–470 ms for 2026-09-14’s 239 notable prints and 1,299 ms once for 2026-09-15’s 174 — the same spread of production load the 2026-09-15 numbers below show, not a change to the query. Measured warm on 2026-09-15, three passes: the session 32–37 ms; the prints query 278 ms for 09-11’s 203 notable prints at $500k and 365 ms for 09-14’s 239; 1,345 ms for 09-11’s 1,554 at the $100k floor, which is the page’s worst case and the reason the floor defaults where it does. Earlier the same day the same reads measured 237–311 ms and 850–1,000 ms; the spread is production load, not a change to these queries.
Flow Discovery asks the same session’s question of the names outside the universe, where no chain exists to answer it.
Simplify Analytics