The SCORE gauge is a single momentum read that spans both sides of the risk trade: bonds and equities: so you can size up the tape without staring at eight tickers. It's built to answer one question fast: which way is the market leaning right now, and how hard. This page covers what the number means, how it's assembled, and what pushes it.
Rates and equities don't move in a vacuum. A payrolls beat that steepens the curve and a risk-off bid that flattens it read very differently in stocks, and a single-asset gauge misses the interplay. The Helious score reads bonds and equities together so the gauge reflects the whole macro posture: a bond-bullish, equity-bearish risk-off session looks distinct from a broad reflation push. It's a read on momentum and direction, not a price target or a trade signal.
The gauge blends real-time price momentum across the tracked bond and equity instruments with the flow coming off the market-moving [feed](/): the same de-duplicated, impact-scored stream that drives the rest of the desk. Economic surprises feed in through the standardized surprise z-score on releases, so a print that lands far from consensus moves the gauge more than a marginal one. The result is a scorer that weights genuine information over noise rather than just chasing the last tick.
Read the score for lean and intensity: which direction the combined tape is pushing, and whether that push is strong or fading. It's most useful as a fast orientation: a way to confirm or question what you're seeing in the curve and spread board and the feed, not as a standalone entry trigger. Pair it with the underlying context: a strong reading into a FOMC decision or a heavy data day means something different than the same reading on a quiet afternoon.
The gauge sits on the live [desk](/) alongside the feed, the release breakdowns, the auction panel and the rates board, so momentum context is always one glance away from the thing that's driving it. When a release or a Fed headline moves the score, you can jump straight to the item that caused it. For how the surprise inputs are standardized, see the methodology.
