Skip to content
Montex Alpha Rail System
$497

System Architecture · Data Flow

From trade evidence to governed intelligence.

The key idea

The data flow

From trade evidence to governed intelligence.

The modern operating loop expands the original TradeZella → Compliance Panel → Weekly Scorecard → EV Lab pipeline into a full authority system with pre-trade controls, daily/cycle tools, throttle governance, volatility engines, structural intelligence, and sandboxed R&D.

  • Execution & capture: trades recorded with branch, risk, R outcome, hit flags, BE status, fees, MAE/MFE, adherence.
  • CP3 Journal → Weekly Summary → EV Scorecard → Gate/Brake → Dashboard: the evidence backbone.
  • Cycle Command Console → Throttle Control Panel: the daily deployment rail.
  • SDE + Regime Engine: structural interpretation above the raw numbers.
  • Monte Carlo Benchmark: the external ruler every live result is compared against.

Where it lives

Inside System Architecture.

This page expands one card of the System Architecture page into its own reference. For orientation, the module's own framing: MARS is not a pile of disconnected spreadsheets — it is an engineered authority stack. Data flows forward from execution evidence to governance; permission flows downward from capital protection to trade sizing. Nothing lower in the stack can override anything above it.

Flow direction audit

Data moving the wrong direction is the first smell of decay.

The architecture defines legal flows — evidence up, authority down, context sideways — and the fastest structural audit is checking for violations: a sizing decision quoting floating P&L, a diagnostic writing into a journal. Wrong-direction flow is how clean systems begin dissolving into the everything-touches-everything sprawl MARS was built to escape.

Worked example

Every workbook in MARS belongs to one of three layers. The evidence core records and grades what actually happened; the deployment rail converts capital state into governed risk; context and validation engines judge whether the environment and the structure can be trusted. Data crosses layers on defined rails - never informally.

The three-layer module ecosystem: evidence flows up from the core, authority flows down the deployment rail, context validates from above.

CONTEXT & VALIDATIONVolatility · Regime · Diagnostics · QADEPLOYMENT RAILGate Map · Cycle Command · Throttle · TiersEVIDENCE COREJournal · Scorecard · EV Lab · MAE/MFEevidence flows upauthority flows down

Before you go deeper

Connected inside MARS

This module doesn't work alone.

Connected — 01

System Architecture (full page)

Open system page →

Connected — 02

Prime Directive

Open system page →

Connected — 03

Why Hierarchy Wins

Open system page →

Go deeper

Operator briefs on this territory.

Deep dive — 01

Evidence up, authority down, context sideways — and the audit that checks it.

Three legal directions. Wrong-direction flow is the first smell of a system dissolving.

Read the full brief →

Deep dive — 02

The rail end to end: journal to deployment, in one pass.

Ten modules and a bonus QA architecture, one path: evidence in at the journal, deployment authority out at the throttle.

Read the full brief →

Deep dive — 03

What the linear pipeline diagram leaves out.

The rail is real, but three things don't sit on it. Missing them is how the diagram misleads.

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 — $497Explore the Platform