Contradiction Engine · Operator Playbooks

Each state carries a posture, not a trade.

Playbooks

Touch sizing

NONE

Escalation unit

PERSISTENCE

How MARS uses this

Each closed trade logs its worst adverse excursion and best favorable excursion. The lab plots them into quadrants and pairs the picture with capture efficiency, giveback, and fee drag - then the EV Driver Diagnostics rank which repair (entry location, coefficient, trail logic, cost avoidance) would move net expectancy most.

How it benefits you

Review produces one concrete fix instead of a vague resolution to 'trade better'. You see whether stops are too tight, entries are chased, exits leak the runner, or fees quietly eat the edge - and whether a profitable week was actually clean or just lucky.

Every trade plotted by pain taken (MAE) versus opportunity generated (MFE). The four quadrants diagnose entry precision and exit management at a glance.

The key idea

Playbook boundaries

A playbook prescribes review actions, never positions.

Each state's response lists diagnostic moves: which windows to re-run, which branch tables to pull, which readings to re-verify. None of them adjust sizing or entries directly, because a contradiction is an information problem, and letting an information problem trigger position changes would hand a diagnostic layer powers the hierarchy reserves for gates. The engine's output feeds the interpretation readout, so contradictions surface inside the same review rather than in a separate report nobody opens.

Where each state sends you

The response is a destination, not an adjective.

Under-monetization sends the operator to exit management and the giveback diagnostics in the execution efficiency layer, because opportunity is being generated and surrendered. Profit without efficiency triggers a deployment-quality review before the sequence turns. Dual weakness escalates past tweaks into structural repair. Transition means widen the observation window and act on nothing yet.

Alignment is the only state that permits discussing expansion, and gate authority still rules it.
One contradictory week is noise; a month of the same state is a finding.
Dual weakness is the stop condition, not the start of a tuning cycle.

The monthly question set

Persistence is the difference between a reading and a diagnosis.

Monthly review deliberately looks past any single week and asks whether the same weakness is repeating. A single weak drift is noise. The same negative structural drift appearing across expectancy, efficiency, and profit quality simultaneously is a different claim entirely, and it is the pattern the monthly slot exists to catch. The engine supports this with summary counters that tally how many weeks fell into each state rather than only reporting the current one.

Audit order

Never start at the readout.

When the workbook is being audited or tested with controlled data, the dependency chain is validated in order: source metrics, then each pipeline table in sequence, then the interpretation cockpit, then the gate map, then this engine. Jumping straight to the final readout tests whether the sentence is well formed, not whether it is true, and a well-formed sentence built on a broken window will read perfectly.

Reference

Signal pattern, interpretation, and the posture it authorises

Pattern	Interpretation	Operator posture
Expectancy strong, drawdown controlled, both quality reads aligned	Structurally constructive	Maintain, or selectively scale if the gate allows
Expectancy strong but drawdown expanding	Edge exists, capital pressure rising	Do not scale. Respect gate state; look for volatility pressure
Efficiency strong, profit quality weak	An efficient process that is not monetizing	Review exits, fees, partial logic, and risk deployment
Profit quality strong, efficiency weak	Possibly variance-driven or over-aggressive	Audit risk usage and branch composition
Acceleration negative while expectancy positive	Edge intact, compounding velocity slowing	Maintain caution; do not assume growth is accelerating
Stability ratio elevated across metrics	Instability building	Reduce confidence in short-term readings; avoid over-reacting
High deviation with aligned interpretation	A meaningful structural move	Treat as high review priority
Gate map at Floor or worse	Capital protection is active	Governance dominates. Positive diagnostics are context only

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