Structural Diagnostic Engine · Authority

Middle authority, and why that is the hard design problem.

Position in stack

MIDDLE

Deployment authority

NONE

Pipelines consumed

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 rule that settles conflicts

If the diagnostics say constructive and the gate says Floor, the gate wins.

This is written as a hierarchy rather than a guideline because the conflict is not hypothetical. A structurally improving system can be in genuine capital distress at the same moment, and the two readings are both true. The engine describes the machine; the gate describes what the account is permitted to do. No positive structural readout has ever been sufficient grounds for aggressive deployment inside a defensive gate, and the design forbids the argument rather than relying on the operator to decline it.

Diagnostic, not prescriptive

It can influence confidence, review priority, and posture. It cannot size a trade.

The distinction is drawn explicitly against what a future operational sensor framework might do. This engine reads structural behaviour: it does not clamp, it does not produce a normalised deployment score, and it does not perform allocation arithmetic. That restraint is what keeps it honest as an interpretation layer, because a diagnostic that can move size acquires an incentive to be confident.

It is a structural diagnosis engine, not a live signal generator.
It is a context layer for the five metrics, not a direct risk allocation engine.
It detects hidden deterioration or improvement; it is not a reason to override brake authority.

Interpretation discipline

Never read one metric alone.

The expectancy pipeline can report an improving edge in the same week the drawdown pipeline reports expanding capital pressure. Both readings are correct, and cherry-picking the stronger one is the failure the whole stack exists to prevent. The operator's job is to reconcile the readings, and the design supports that by keeping the pipelines structurally identical: the same six tables in the same order, so the comparison is between findings rather than between formats.

Where the boundary is enforced

The final readout is not permitted to override governance.

The quality checklist for the workbook includes the requirement as a line item, alongside checks on entity consistency, window maturity, and cumulative arithmetic. Placing it there rather than in a preamble is deliberate. A boundary that lives only in a philosophy section gets forgotten during the month it is needed; a boundary that appears in a checklist gets verified.

Reference

The authority stack, and what each layer hands the next

Layer	Primary role	Relationship to the engine
Execution and journal	Raw evidence: trades, branches, risk, outcomes, fees, adherence	The engine never alters raw data; it consumes downstream weekly metrics
Weekly summary and scorecard	Branch statistics, probabilities, expectancy, PnL, weekly outputs	These outputs are the engine's source truth
Compliance panel	Governance cockpit: brakes, quotas, adherence, milestone pacing	The engine adds structural interpretation to this ecosystem
The five pipelines	Diagnose expectancy, drawdown, efficiency, profit quality, acceleration	The core structural analytics layer
Interpretation cockpit	Converts selected-entity metrics into meaning and readout	The live translation surface for the operator
Gate and brake system	Hard capital governance from drawdown and loss thresholds	The engine informs context; this layer retains authority

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