CP3 — Engine 08 · Context

The Regime Engine inside CP3. Naming the month.

How MARS uses this

The Weekly Scorecard converts branch hit probabilities into EV and tags each week by threshold. The rolling line is what MARS actually trusts: single-week readings are treated as noise until the rolling window confirms direction. RED weeks trigger doctrine - reduced aggression and review - rather than negotiation.

How it benefits you

You learn to distinguish a bad week from a broken system. Variance stops triggering rule changes, and genuine expectancy decay gets caught while it is still one line on a chart instead of a hole in the account. The GREEN/YELLOW/RED language also makes weekly review fast and unambiguous.

Weekly EV tagged GREEN / YELLOW / RED against expectancy thresholds, with the rolling-EV line separating persistent edge from one lucky week.

The key idea

What it reads

The system's own condition — not the market's.

The Regime Classification Engine explicitly classifies MARS's internal state from monthly gate and brake telemetry. It is not a market-regime detector.

Six metrics scored −2 to +2 into a −12…+12 composite: Gate Pressure, Structural Health, Volatility, Transitions, Persistence, Compression
Ten regime labels from Expansion to Critical State, each with four sub-labels and a call-to-action — forty nameable states
Dashboard-ready output: Main Regime — Driver Tag

Why it lives in CP3

Telemetry at the source.

Gate transitions, brake tones, and dwell times are CP3's Layer 03 truth. Housing the regime engine beside that telemetry means the monthly classification is computed from the same verified records the gate itself runs on — one source of truth, zero translation loss.

Go deeper

The full engine has its own page.

This page covers the regime engine as housed inside Compliance Panel 3. The dedicated Regime Classification Engine page in Diagnostics documents all ten regimes, the scoring rubric, and how driver tags route monthly review.

Month boundaries

The regime label freezes at month-close, on purpose.

Intra-month regime drift is visible but non-binding: the official classification is stamped once, at close, from the full month's inputs. Freezing the label stops posture from whipsawing on mid-month noise, and it gives every month exactly one name that the rest of the review architecture can reference without ambiguity.

Connected inside MARS

This module doesn't work alone.

Connected — 01

Regime Classification Engine (full page)

Open system page →

Connected — 02

Compliance Panel 3 (full module)

Open system page →

Connected — 03

Gate / Brake State

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

The inputs tab is a mirror. In production, nobody types into it.

A hand-typed input cell severs the classification from its evidence, and leaves no trace that it did.

Read the full brief →

Deep dive — 02

One of the six inputs has a disputed direction, and the manual says so out loud.

Two tabs read the same metric in opposite directions. The manual names the conflict instead of picking quietly.

Read the full brief →

Deep dive — 03

Disagreeing with the classifier is allowed. There is a correct way to do it.

The month felt worse than the label. Which of the six metrics disagrees with you, and by how much?

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