Skip to content
Montex Alpha Rail System
$497
← Back to Data Flow

Operator brief · 142

What the linear pipeline diagram leaves out.

The key idea

The legacy line

The original loop is still valid — as a foundation, not as a complete map.

The architecture manual is careful about this. The original loop — TradeZella captures raw execution, the Compliance Panel organizes it, the Weekly Scorecard converts it into EV health, the EV Lab provides sandbox testing — is described as still valid as the historical foundation, and the legacy documents are explicitly not dismissed as obsolete. What changed is scope: the modern stack adds pre-trade paper controls, post-trade capture sheets, daily and cycle risk tools, throttle governance, volatility intelligence, structural diagnostics, and regime classification. The line did not become wrong. It became a subset.

Before the pipeline

Two physical documents sit upstream of anything digital.

The layer table opens with two entries that involve no workbook at all. Pre-entry verification asks whether the trade is allowed before risk is deployed, and its tool is the Trade Launch Checklist. Post-execution capture asks what exactly happened and what must be entered on Saturday, and its tool is the Trade Capture Document. Both are physical. Both precede the journal. The daily workflow is explicit that the checklist runs before each trade and is not to be skipped because the setup looks obvious, and that a capture document starts immediately after execution rather than at review time. Everything downstream inherits the quality of these two, which is a strong argument for their being the least digital things in the stack.

FigureThree groups that a single line cannot show
Upstream — physicalbefore any workbook· Trade Launch Checklist· Trade Capture Document· Filed by week until CP3 reviewverifiesThe rail — sequentialevidence becoming authority· TradeZella + CP3 Journal· Weekly Summary + EV Scorecard· Gate/Brake + Dashboard· Cycle Console → Throttle PanelOff-rail — parallel & sidewaysinforms, never feeds· Monte Carlo benchmark(parallel)· Volatility Panel + DistanceMatrix (sideways)· SDE + Regime Engine (above)· EV Lab (sandboxed)

The pipeline is real but partial. The physical layer precedes it, the context engines arrive from the side, and the simulation layer runs parallel — comparing against the pipeline rather than feeding it.

The parallel track

Simulation runs alongside the rail, and the distinction is load-bearing.

The Monte Carlo layer is described in the layer table as the external ruler every live result is compared against — and 'compared against' is doing precise work. The simulation does not receive evidence from the pipeline, process it, and hand something back downstream. It generates an independent expectation from declared assumptions, and live results are then measured against it. If it sat inside the rail it would become another opinion in the chain, and a benchmark that participates in the process it measures has stopped being a benchmark. The production rule in the R&D table reinforces the separation: compare actual performance to the statistical baseline during review, not during a single trade.

The sideways arrivals

Volatility intelligence enters the trade, not the pipeline.

The Volatility Intelligence Panel and Distance Matrix answer what regime and coefficient context governs stop and trail logic — which is a question about how an already-permitted trade gets managed, not about whether it is permitted or how large it is. They therefore attach at the trade rather than at any pipeline stage, and their output never travels up the evidence chain or down the authority chain. This is why a strong volatility read cannot expand risk beyond the gate cap: the read is not on the authority path at all, and there is no route by which it could reach the tier decision even if an operator wanted one.

Reading the map correctly

The line answers 'what happens next'; the full map answers 'what governs this'.

Both readings are needed and they serve different moments. When reconciling a week — trades captured, journal entered, summary reviewed, gate checked — the linear rail is exactly the right mental model, because the work genuinely is sequential and the order genuinely matters. When diagnosing why a decision came out the way it did, the line is misleading, because the binding constraint frequently arrives from off-rail: a gate row set by capital state, a coefficient set by volatility context, a benchmark comparison that reframes a mediocre month as statistically ordinary. Knowing which map to hold is most of what architectural literacy amounts to here.

Connected inside MARS

Data Flow →
Monte Carlo Lab →
Volatility Intelligence Panel →
Trade Lifecycle →

Every brief documents the same shipped system.

The complete MARS package — eleven workbooks, three TradingView indicators, the full manual library — $497.

Get MARS Pro — $497Explore the Platform