MARS Overview · Customer Benefits

Six benefits you can verify. Four you have to take on trust.

Benefits with an artefact

Benefits without one

Fields in the decision trail

Willpower required for brakes

None

How MARS uses this

Drawdown from Equity Peak High routes the account into a gate. The gate then selects the throttle row, caps the maximum risk tier, sets the brake tone, and constrains which management variants are even permitted. Every deployment decision starts by reading this ladder - a good setup cannot override a restricted gate.

How it benefits you

The question 'should I be trading full size right now?' gets an exact answer instead of a mood. Risk compresses automatically as damage grows and re-expands only as capital heals - protecting accumulated gains, not just starting capital, without requiring willpower in the moment.

The seven-gate capital ladder. Each state carries its own brake meaning, tier cap, and risk authority - the marker shows an account operating in Growth.

The key idea

In practice

Every decision in MARS is routed through this hierarchy in order. The plan defines doctrine; gate state defines capital posture; the throttle converts posture into deployment numbers; evidence and diagnostics inform from below; R&D stays sandboxed at the bottom until validated. When layers disagree, the higher layer wins - always.

The MARS authority stack. Authority flows down; evidence flows up; nothing lower may override anything above it.

The test being applied

A benefit is verifiable when a specific artefact would be missing without it.

The distinction used on this page is deliberately mechanical rather than rhetorical. A benefit counts as verifiable when you can name the file, the field, or the output that exists because of it, and confirm that the artefact is present and correct without trusting anyone's account of how things are going. Everything failing that test is not thereby false — several of the unverifiable benefits are the most valuable on the list — but it belongs in a different column, and merging the two columns is how benefit lists lose their credibility.

The verifiable six

Each of these leaves something behind that can be inspected.

A decision trail records what was traded, in which branch, at what authorised risk, whether the trade was cleared, what happened inside it, whether the plan was followed, whether an override was used, and what the system permitted next — nine fields, present or absent. Capital protection is architectural: the gate row and tier ceiling are computed from drawdown, so the constraint exists whether or not the operator felt cautious. Branch attribution produces a per-branch expectancy figure. Exposure accounting produces a remaining-pool number. Execution diagnostics produce capture, giveback, and fee-drag figures. Benchmark position produces a classification against a fitted envelope. Six outputs, all inspectable on demand.

The nine-field decision trail — present or absent, per trade
Gate-derived capital protection — computed, not felt
Per-branch expectancy — which branch actually carries the account
Remaining pool capacity — a figure, not an impression
Capture, giveback, and fee drag — the execution leak, quantified
Benchmark position — inside or outside a mix-fitted envelope

The unverifiable four

Real, frequently decisive, and impossible to demonstrate.

The remaining benefits leave no artefact. Reduced improvisation under stress is genuine and shows up as a decision not taken, which by construction produces no record. Evidence-based confidence is more durable than confidence built on recent wins, and no measurement distinguishes the two while both are holding. The language shift — from whether a setup feels right to which gate applies and what the throttle permits — changes how decisions are framed and leaves nothing to audit. And relief from the weekly argument with yourself about whether a bad stretch means the method is broken is worth a great deal and is not a data field anywhere in the system.

Why the split is stated

The unverifiable column is where the disappointment risk lives.

Most buyer disappointment traces to a benefit that was implicitly promised as verifiable and turns out not to be. An operator expecting the system to demonstrate that their confidence is now better founded will not find that output, because it does not exist and never will. Expecting the same system to produce a per-branch expectancy figure is entirely reasonable, and its absence would be a defect. Sorting the two columns before purchase converts a vague expectation into a checkable one, which is the same service the instruments perform on trading.

Auditing your own ledger

Three checks, available from the first month.

The verifiable column can be audited without waiting for a track record. Open a recent week and confirm all nine decision-trail fields are populated for every trade — gaps are the single most common defect and they are yours, not the system's. Take the current gate row and confirm the tier ceiling follows from the drawdown figure rather than from what felt reasonable. Take one closed trade and confirm capture, giveback, and fee drag reconcile with the broker record. If all three pass, the verifiable six are being delivered; if any fails, the failure is locatable, which is the point of keeping the columns separate.

Nine fields populated on every trade in a recent week
Tier ceiling traceable to the drawdown figure, not to judgement
One trade's capture and fee drag reconciled against the broker record

Reference

The ledger, benefit by benefit

Benefit	Verifiable?	The artefact — or why there is none
Decision trail	Yes	Nine fields per trade; present or absent
Architectural capital protection	Yes	Gate row and tier ceiling, computed from drawdown
Branch attribution	Yes	Per-branch expectancy, separated from account total
Exposure accounting	Yes	Remaining pool capacity as a figure
Execution diagnosis	Yes	Capture, giveback, stop efficiency, fee drag
Benchmark position	Yes	Classification against a mix-fitted envelope
Less improvisation under stress	No	Shows up as a decision not taken — leaves no record
Evidence-based confidence	No	Indistinguishable from any other confidence while it holds
The language shift	No	Changes how decisions are framed; produces no field
Relief from the weekly argument	No	Real, often decisive, and not a data point anywhere

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Connected — 01

MARS Overview (full page)

Open system page →

Connected — 02

The Potential for Users

Open system page →

Connected — 03

Ways to Use MARS

Open system page →

Connected — 04

The Complete Picture

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

A benefit is checkable when something would be missing without it.

Name the artefact, or move the claim to the other column.

Read the full brief →

Deep dive — 02

The benefits most operators stay for are the ones that cannot be shown.

Less improvisation. Durable confidence. Changed language. An argument that stops. None provable.

Read the full brief →

Deep dive — 03

Three checks, runnable in month one, that settle whether you are being delivered to.

Fields populated. Ceiling traceable. One trade reconciled. All three fail informatively.

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