Skip to content
Montex Alpha Rail System
$497

Use Case 06 — Monte Carlo Survivability

Will the system survive its own variance?

The question

Rules can be followed perfectly and still lose.

Survivability analysis accepts an uncomfortable truth: a positive-expectancy system with real variance still has some probability of hitting its own shutdown boundary. The honest question isn't whether that probability is zero — it's whether it's acceptable, known, and priced in before deployment.

The core idea

How MARS uses this

The Weekly Scorecard converts branch hit probabilities into EV and tags each week by threshold. The rolling line is what MARS actually trusts: single-week readings are treated as noise until the rolling window confirms direction. RED weeks trigger doctrine - reduced aggression and review - rather than negotiation.

GREEN ≥ +0.25RYELLOWREDROLLING EVW1W2W3W4W5W6W7W8W9W10W11W12

How it benefits you

You learn to distinguish a bad week from a broken system. Variance stops triggering rule changes, and genuine expectancy decay gets caught while it is still one line on a chart instead of a hole in the account. The GREEN/YELLOW/RED language also makes weekly review fast and unambiguous.

Weekly EV tagged GREEN / YELLOW / RED against expectancy thresholds, with the rolling-EV line separating persistent edge from one lucky week.

The measurement

02

Lock-risk across 50,000 histories.

Across the full simulated distribution, the analysis counts the paths that touch System Lock — and studies how they got there: drawdown sequences, gate cascade patterns, and the variance profiles that precede lock events. Sequence sensitivity shows how much of ruin risk is pure trade-order luck.

Modules involved

The survivability stack.

The Monte Carlo Lab runs the paths, the gate ladder defines the lock boundary being tested, and Risk-Tier Performance Bands show how tier behavior shifts survival odds.

Reference

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.

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.

GROWTHto −7%Full compoundingRECOVERY−7.1 → −13%Stability brakeBUFFER−13.1 → −19%Defense brakeFLOOR−19.1 → −27%ContainmentDEEP-FLOOR−27.1 → −34%SuppressionGROUND-FLOORbelow −34%Minimal defenseSYSTEM LOCKlock boundaryDeployment stopsYOU

Connected inside MARS

This module doesn't work alone.

Connected — 01

All eight use cases

Open system page →

Connected — 02

Monte Carlo Lab

Open system page →

Connected — 03

Risk-Tier Performance Bands

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

The goal is not zero risk of ruin. It is a number you have seen and accepted.

Every honest system has a ruin number. The dishonest ones have a claim instead.

Read the full brief →

Deep dive — 02

System Lock sits where you put it, so the lock rate is partly a statement about your settings.

Lower the boundary and the ruin number improves. Nothing else does.

Read the full brief →

Deep dive — 03

Reading survival curves without fooling yourself.

Hit-week percentiles are successful-path-only. Miss that, and every survival read is a highlight reel.

Read the full brief →

Take it further

Survivability is a question about the tail, and tails are learned by running the same profile many times. The Foundry is built for exactly that loop.

Open the AlphaRail Foundry Lab ↗

Every module ships in the complete MARS package.

One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.

Get MARS Pro — $497Explore the Platform