Antick.io
IntermediateReading The Signals

How to read the regime panel and Structure DNA

The radar views compress dozens of measurements into one shape. Here is how to read them and where they can mislead.

8 min read
1

The Regime Map radar

Every engine has a Regime Map: a spider web with one axis for each dimension the engine measures, scored from 0 to 100. On the market-wide view, the shape describes the whole market on that engine; SMOD, for example, shows Discovery, Momentum Expansion, Silent Accumulation, Distribution, Liquidity Trap, High Manipulation and Emerging Coin.

Above the radar you see the dominant regime, the bias (up, down or balanced) and a confidence level. The center score places the engine's signed score on a 0 to 100 scale: near 50 is close to neutral, higher leans up and lower leans down. It does not measure how strong or how reliable the read is.

MSI Regime Map with its regime, bias and confidence, next to the Volatility Regime card.
2

Reading the scale

The legend groups values into four bands: Weak up to 30, Soft up to 50, Firm up to 70 and Strong up to 100. A reading only matters when some axes clearly stand out; a round, even shape means no single behaviour dominates.

3

Structure DNA for one asset

On the Structure Analysis and Metrics Breakdown pages, the radar becomes the asset's Structure DNA. For MSI its axes include Trend Strength, Directional Efficiency, Range Stability, Volatility Level, Participation, Signal Quality, State Stability and Market Risk.

Look for the axes that stick out. High Market Risk with low Signal Quality warns that the current label rests on weak evidence.

4

Regime Interpretation

Next to the radar, Regime Interpretation names the current regime, explains what it means in a few short points and states the directional bias. It is the quickest way to turn the shape into words.

MSI Structure DNA and Regime Interpretation for one asset.
Where the radar can misleadThe radar shows one timeframe at one moment. Confirm a strong shape on a higher timeframe and with the scenarios and invalidation zone before you rely on it.