Contradiction Engine · Operator Playbooks

Each state carries a playbook.

How MARS uses this

Every governing metric is tracked as a rolling series with stability bands and a z-score against its own history. Readings inside the band are treated as variance and left alone; sustained drift toward the outer bands raises a structural flag that outranks the P&L column.

How it benefits you

You stop repairing noise and stop ignoring decay. A losing week inside the band changes nothing - which protects working rules from panic edits - while genuine deterioration is caught as a line on a chart weeks before it becomes a hole in the account.

A rolling metric leaving its normal band: inside ±1σ is weather; a sustained walk toward −2σ is climate - and climate gets flagged.

The key idea

Operator response

Each state carries a playbook.

Contradiction states are not trivia — each maps to a response. Under-monetization sends the operator to exit management and the MAE/MFE Lab's giveback diagnostics. Profit-without-efficiency triggers a deployment-quality review before the luck runs out. Dual weakness escalates past tweaks into structural repair. Transition means widen the observation window before acting at all.

Alignment is the only state that permits discussing expansion — and even then, gate authority still rules.
State persistence matters: one contradictory week is noise; a month of it is a finding.
The engine's output feeds the SDE readout, so contradictions surface inside the same review, not in a separate report nobody opens.

Where it lives

Inside Contradiction Engine.

Pulled from the Contradiction Engine page so it can be linked, cited, and studied on its own. In the module's words: The RAER/RAPF Contradiction Engine detects when efficiency quality and profit quality stop confirming each other — exposing under-monetization, profit-without-efficiency, dual weakness, alignment, and transition states that neither metric reveals alone.

Playbook boundaries

A playbook prescribes review actions, never trades.

Each contradiction state's playbook lists diagnostic moves — which windows to re-run, which branch tables to pull, which authority reads to re-verify. None of them touch sizing or entries directly, because a contradiction is an information problem, and letting it trigger position changes would hand a diagnostic layer powers the hierarchy reserves for gates.

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Connected — 01

Contradiction Engine (full page)

Open system page →

Connected — 02

The Five States

Open system page →

Connected — 03

Why Contradictions Matter

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

Alignment: the state that authorises nothing.

The two metrics agree. That is the engine's resting state, not a result — and agreement can be negative.

Read the full brief →

Deep dive — 02

Dual Weakness: the one state the manual calls a danger condition.

Both efficiency and monetisation impaired at once. The only state the manual calls structural danger rather than a finding.

Read the full brief →

Deep dive — 03

Transition: the engine's licence to say nothing yet.

Mixed or changing signals, and an explicit instruction to wait. An engine that can decline is rarer than it sounds.

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