SDE — Middle Authority

Above raw calculation. Below hard governance.

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.

The key idea

The position

A context layer with a fixed rank.

Middle authority is a deliberate design decision, not a limitation:

If the SDE says conditions are constructive but the Gate Map says Floor or below, the gate wins. Diagnostics cannot override capital protection.
Interpretation engine: rolling windows, stability, drift, and z-scores across six structural tables.
The Interpretation Cockpit translates live or selected-entity metrics into matrix states, category outputs, and a final narrative readout.

The two failure modes

Over-trusted or ignored — both waste it.

Treated as an allocation engine, the SDE invites over-trust of intermediate diagnostics — sizing decisions it was never built to make. Treated as a passive report, its value is wasted — it exists to change review posture: continue, watch, repair, or compress. The correct use is exactly between those failure modes.

Why below the gate

Structural optimism never unlocks capital.

A constructive structural read during a defensive gate is common — structure often recovers before equity does. The hierarchy holds anyway: SDE optimism never unlocks capital during defensive gates, because drawdown authority protects against exactly the scenario where the optimism is wrong.

The middle seat

Advisory rank is the engine's power, not its limitation.

Sitting above raw calculation but below hard governance means the SDE can say anything without breaking anything. That freedom is the design: an engine with gate-level authority would need gate-level caution and would flag late; an advisory engine can flag early, aggressively, and cheaply — the hierarchy pays for its boldness.

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Connected — 01

Structural Diagnostic Engine (full module)

Open system page →

Connected — 02

The Entity Universe

Open system page →

Connected — 03

Risk Gate Map

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

Middle authority: the rung that explains but cannot command.

Above raw calculation, below hard governance — and the narrowness of that rung is the whole design.

Read the full brief →

Deep dive — 02

The two ways a diagnostic layer gets misread — and they are opposites.

Treat it as an allocation engine and you over-trust it. Treat it as a report and you waste it. Both are the same error mirrored.

Read the full brief →

Deep dive — 03

Diagnostic, not prescriptive: the four things a reading may move.

Confidence, review priority, throttle discussion, risk posture. Four things may move, and deployment is not one of them.

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