Skip to content
Montex Alpha Rail System
$497

Resources — Documentation

Every module ships with a full operator manual.

The key idea

The library

Twenty operator manuals, one per instrument.

The set covers the Master System Architecture, the Compliance Panel 3 Operator Manual in two parts, the Weekly Trading Scorecard, the Cycle Command Console, the Throttle Control Panel, the Cycle-to-Throttle extended workflow pack, the Volatility Intelligence Panel, the Volatility Distance Matrix, the Structural Diagnostic Engine framework, the Regime Classification Engine framework, the MAE/MFE Execution Efficiency Lab, the Advanced EV Analytics Lab, the Certified Validation QA workflow, the Branch Variant Selection Matrix, the Dynamic 7-Tier MC Benchmark Operating Standard, the Trading Plan Evolution manual, and all three indicator guides.

  • Every manual defines its module's authority boundary — what it decides, and what it may never override.
  • Formula families are documented conceptually, so outputs are auditable rather than mysterious.
  • Worked scenarios run real inputs through the module and show the reading, not just the mechanism.

How a manual is built

The same six-part shape, every time.

The manuals are deliberately uniform, because a library learned once should not need relearning per instrument. Each opens with the module's purpose and the single question it owns. Then the tab-by-tab reference, in the order an operator actually moves through the workbook. Then the formula families — what is computed, from which inputs, and why that construction rather than another. Then the authority boundary. Then the QA checks that confirm the module is being fed correctly. Then worked examples. Learning the shape is most of the work; after the second manual, the rest read quickly.

The authority boundary

The section that matters most is the one about limits.

Every manual states what its module may not do, and that section carries more weight than the feature list. The Monte Carlo Lab informs and never authorises. The indicators inform and never size. The Advanced EV Analytics Lab is explicitly R&D and holds no live authority. Documenting the ceiling as carefully as the capability is what keeps eleven workbooks from becoming eleven competing opinions — and it is the part of the documentation most often skipped by readers and most often needed later.

Reading order

04

Start with the architecture, then the module in front of you.

The Master System Architecture manual is the one to read first, because it explains how authority descends through the stack and where each module sits in that chain. After that, the honest advice is not to read the library front to back: open the manual for the workbook currently in use, keep its tab reference beside you while working, and let the rest wait. The Comprehensive Product Orientation that ships with every order exists to sequence exactly this, and it is a better guide to order-of-approach than the library's own alphabet.

Versioning

Manuals are versioned with their modules, not separately.

Each manual carries the version of the workbook it documents — the Throttle Control Panel manual is written against v4.4F, the Cycle Command Console against v4.6, the MC Lab against v2.5. This matters when a module updates: the manual moves with it, and a mismatch between the two version numbers is the first thing to check when the reference and the file appear to disagree. Versions are printed on the manuals themselves rather than tracked in a separate changelog nobody would open.

What it is not

Documentation is a reference, not a course.

The manuals explain how each instrument works and how to read its output. They do not teach a trading strategy, and they are not where a new operator should begin — the onboarding materials and video walkthroughs are built for that. Read as a curriculum, the library is overwhelming; read as a reference consulted at the moment of use, it is exactly the right size. The distinction is worth holding, because the most common complaint about deeply documented systems comes from people who tried to read them like a book.

Reference

The twenty operator manuals

ManualDocumentsThe question it answers
Master System ArchitectureThe whole railHow does authority descend through the stack?
Compliance Panel 3 — Part 1CP3 evidence coreHow is evidence recorded and reconciled?
Compliance Panel 3 — Part 2CP3 housed enginesWhat do the engines inside CP3 read?
Weekly Trading ScorecardWeekly EV cockpitIs the system still +EV by branch and blend?
Cycle Command ConsoleCycle evidence + exposureWhat happened this cycle, and what is still open?
Throttle Control PanelDeployment authorityHow much risk may be deployed next cycle?
Cycle-to-Throttle Workflow PackThe handoff between themHow does console evidence become throttle authority?
Volatility Intelligence PanelCoefficient authorityWhat coefficient governs stop and trail?
Volatility Distance MatrixATR-normalized distanceWhat is normal distance for this asset and session?
Structural Diagnostic EngineStructural healthIs the machine improving, weakening, or contradicting itself?
Regime Classification EngineMarket contextWhat regime is this, and how long has it held?
MAE/MFE Execution Efficiency LabTrade lifecycle qualityWas opportunity converted into realized R?
Advanced EV Analytics LabExpectancy R&DWhat would happen under different assumptions?
Certified Validation QA WorkflowChange validationIs this change safe to promote to production?
Branch Variant Selection MatrixVariant comparisonWhich management structure earns deployment?
Dynamic 7-Tier MC Benchmark StandardThe benchmark rulerWhere does live performance sit in the fan?
Trading Plan EvolutionPlan governanceHow does the plan change, and on what evidence?
Trend Continuation IndicatorChart toolIs this continuation structurally supported?
EW Convergence IndicatorChart toolAre the wave counts converging on a termination zone?
ATR BE AssistantChart toolWhere does break-even sit under current volatility?

Use cases

Where it earns its place

  • ▸Working inside a workbook and needing the exact meaning of a tab, field, or computed column.
  • ▸Checking what a module is permitted to decide before acting on its output.
  • ▸Reconciling two instruments that appear to disagree about the same period.
  • ▸Confirming a manual's version matches the workbook version actually in hand.

Edge cases & failure modes

Where it can mislead

  • !Learning to trade — the manuals document instruments, they do not teach a method.
  • !Reading front to back as a curriculum — start with the Orientation and the architecture manual instead.
  • !Looking for a term's definition — that is the Knowledge Base, which consolidates across all twenty.

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Connected — 01

Downloads & delivery

Open system page →

Connected — 02

Knowledge Base

Open system page →

Connected — 03

Module Ecosystem

Open system page →

Connected — 04

Get MARS — $497

Open system page →

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