The Name · MON — Monte Carlo
The ruler, not a motivational target.
Read this first
MON — Monte Carlo
01The ruler, not a motivational target.
50,000 simulated paths across 52 weeks with the gate-aware allocator define what the system should reasonably expect. Live performance is read against median and percentile bands — the trader is not supposed to panic below median or worship a lucky P90 month.
Where it lives
02Inside The Name.
This page expands one card of the The Name page into its own reference. For orientation, the module's own framing: Montex AlphaRail is a compact expression of the system's architecture: Monte Carlo provides the benchmark ruler, expectancy grades live performance, alpha is outperformance earned cleanly, and the rails keep behavior aligned with the envelope.
Why simulation leads the name
03The name starts where honest expectations start.
Putting Monte Carlo first in the brand's etymology mirrors its position in the doctrine: before a single live trade is sized, the evidence has already been resampled into thousands of futures and the adverse bands drawn. The name leads with simulation because the system leads with it — expectations are manufactured before exposure, never after.
How MARS uses this
MARS is a closed loop, not a pipeline. Trades produce evidence, evidence produces weekly grades, grades move gate state, gate state feeds the throttle, and the throttle governs what the next execution is allowed to be. No stage is optional and no stage runs on memory or mood - each one reads the outputs of the stage before it.
How it benefits you
Discipline stops depending on willpower. Because every decision point consumes the previous stage's output, skipping a step becomes visible instead of invisible - and the system keeps improving itself, since every completed loop leaves the evidence base one cycle richer than it found it.
The MARS operating loop: execute, capture, score, gate, throttle, deploy - every cycle feeding evidence into the next.
In practice
The three-layer module ecosystem: evidence flows up from the core, authority flows down the deployment rail, context validates from above.
Connected inside MARS
This module doesn't work alone.
Go deeper
Operator briefs on this territory.
Deep dive — 01
What has to be true before a simulation may be called a benchmark.
The conditions a simulation must satisfy before it is allowed to govern deployment.
Read the full brief →
Deep dive — 02
Expectations are manufactured before exposure, never after.
Why the benchmark must exist before capital is committed — and what happens when it is built afterwards.
Read the full brief →
Deep dive — 03
Neither panic below median nor worship a lucky P90.
Why a below-median stretch and a P90 month are the same category of non-event.
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.