Reliability

This isn't a feature list. Gamma exposure is public options-market math — the same inputs every GEX tool uses. The actual difficulty in a system like this isn't the formula, it's staying correct while it runs live against a real market, every session. This is a partial, real record of the operational problems that has actually required — not the marketing version, the engineering one.

1. Three different reasons data can be old — handled differently

   "The market is closed," "today's first scan hasn't landed yet," and "this data is stale from a prior session" are three distinct states, not one. Each gets its own honest message, computed from real wall-clock time and the actual age of the last snapshot — never one generic "last updated" label standing in for all three.

2. Every time boundary survives the daylight saving switch

   Scan windows, the session close, and every other time-of-day boundary are computed from a real timezone conversion, re-verified against both EDT and EST, not a hardcoded UTC offset. A naive fixed offset silently drifts by an hour twice a year — the kind of bug that only shows up on exactly two days out of 365 and is easy to ship without ever noticing.

3. A wall the scoring engine couldn't confidently label doesn't take the dashboard down

   The engine sometimes genuinely can't compute a confident read for a wall — that's a real, expected state, not corrupted data. The dashboard has to recognize that state and degrade gracefully to an honest "not available this scan," not crash the entire page for every subscriber over one unresolved value.

4. Scheduled and manual pushes go through the same pipe, with no special-casing

   The system runs on a fixed schedule through the trading day, but also accepts manual, off-schedule pushes. Both have to flow through identical validation, staleness, and live-update logic — a manual push at an odd hour is not allowed to behave differently from a scheduled one.

5. A significant change can't get silently crowded out by a minor one

   When several fields change in the same update, a genuinely significant shift — a wall's strength intensifying, for instance — has to stay visible even in a compact view, instead of being pushed out of frame by less important fields that happened to change in the same push.

6. The first and last read of a session are explicitly known, not inferred

   Which push was the day's first real scan, and which was its last, are computed signals in their own right — not something a subscriber has to work out by comparing timestamps themselves.

For the dated, subscriber-facing version of what's changed, see the changelog.