Diagnostics — Regime Classification

It classifies your system, not the market.

Monthly regimes

Scored metrics

Composite range

−12…+12

Sub-labels each

The regime ladder

A monthly language for the machine.

Ten states describe the system's internal condition: Expansion, Expansion Developing, Balanced, Transitional, Compression, Fragile Recovery, Instability, Degradation, Drawdown Control, and Critical State. Six metrics are scored −2 to +2 each, composited into a −12 to +12 read, with four sub-labels per regime adding nuance.

A governance-readout layer for the trading system itself — never a replacement for gate authority.
Each regime carries a call-to-action inside the larger compliance system: expand, hold, review, or defend.
Monthly cadence by design: regimes describe structural months, not noisy days.

Why it exists

“How is the machine doing?” deserves a real answer.

Without regime classification, a trader describes their system's condition in adjectives. With it, the answer is a defined state with defined implications — and transitions between states are themselves signal: Expansion decaying into Transitional is a different conversation than Fragile Recovery hardening into Balanced.

The six inputs

Pressure, health, volatility, transitions, persistence, compression.

The composite is built from six monthly structural readings pulled from the gate-state record: gate pressure, structural health, gate volatility, transition count, persistence, and compression. Each scores from −2 to +2 against fixed thresholds, and the sum — a range of −12 to +12 — maps onto the regime ladder. Six independent lenses on one machine, compressed into a single classification with a full audit trail.

The QA layer

A classification that fails its ontology check is provisional.

Each main regime permits exactly four sub-labels, and the engine's QA formula verifies that the selected pair exists in the rules table. A mismatch does not crash the readout — it flags it, and a flagged month is treated as provisional context rather than actionable state. The check sounds bureaucratic until the month it catches a mislabel that would have justified aggression inside a deteriorating structure.

How MARS uses this

Six structural inputs are scored monthly into a composite, and the composite maps onto the regime ladder. MARS reads results in context: the same numbers mean different things earned in Expansion tailwind versus survived through Instability, and posture is adjusted to the regime rather than to the last trade.

How it benefits you

You know whether the environment is friendly or hostile to your system before deciding what recent results mean. Confidence stops being borrowed from lucky months, defensive posture arrives before damage instead of after it, and monthly review gains a one-glance structural summary.

Twelve months classified across the regime ladder - the system's own weather record, from Expansion down toward Drawdown Control.

Doctrine

Inside this module

2 pages go deeper than this one.

The 10-Regime Ladder

Go deeper →

Why It Exists

Go deeper →

Connected inside MARS

This module doesn't work alone.

Connected — 01

Structural Diagnostic Engine

Open system page →

Connected — 02

Compliance Panel 3

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

Regime classification: the system's weather report on itself.

Six metrics, one composite score, ten regimes — how MARS classifies its own internal state monthly.

Read the full brief →

Deep dive — 02

Six metrics, one composite: how a month becomes a regime.

Six metrics, equal weight, −2 to +2, summed once. Restraint is the architecture.

Read the full brief →

Deep dive — 03

Ten regimes, forty sub-labels: naming a month precisely.

Main regime = the state. Sub-label = the driver. Ten × four, and never stacked.

Read the full brief →

Every module ships in the complete MARS package.

One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.

Get MARS Pro — $497 Explore the Platform