Volatility — Coefficient Calibration

The coefficient is a decision, not a default.

Why calibration beats eyeballing

Live ATR alone lacks structure.

From the master manual: the matrix prevents subjective coefficient selection. Instead of looking at live ATR and guessing whether volatility 'feels high', the operator reads it against trigger timeframe, authority timeframe, asset class, and engine mode. Raw-ATR judgment is weaker precisely because it lacks that structure.

The spectrum

From 1.5 to wide — what each band means.

Tighter coefficients (around 1.5) suit clean, orderly expansion where noise is small relative to trend; wider coefficients buy survival room in high-intensity zones at the cost of giveback. The calibration answer is never a universal number — it is a function of asset class, timeframe pair, session baseline, and current volatility zone.

01Very Low and Low zones argue for standard coefficients; High and Extreme zones argue for width or for skipping trend management entirely.

02Authority-timeframe confirmation matters: a 5M trigger trailing against a 1H authority read behaves differently than 5M alone.

03Every choice lands in the Coefficient Audit Log — calibration is a learning loop, not a setting.

The core idea

The feedback loop

Coefficient decisions become evidence.

Coefficient, volatility zone, ATR ratio, and stop distance get logged into trade capture and CP3. The SDE and MAE/MFE Lab can later diagnose whether coefficient behavior is improving or damaging trend-branch EV — closing the loop from decision to accountability.

Reference

Three coefficient layers — default, override, active

Layer	What it stores	When it applies
Default	The base system coefficient settings	Always, unless deliberately overridden
Override	A deliberate model change entered by the operator	Only when the override cell is filled — blank means no override exists
Active	The coefficient the system actually uses	Returns the override if present, otherwise the default — one unambiguous source of truth

Reference

Independent structures resolving to the same point. One wave is an opinion; agreement between unrelated structures is a signal.

Inside this module

3 pages go deeper than this one.

Why Not Eyeballing

Go deeper →

Feedback Loop

Go deeper →

The 1.5 → Wide Spectrum

Go deeper →

Connected inside MARS

This module doesn't work alone.

Connected — 01

Volatility Distance Matrix

Open system page →

Connected — 02

MAE/MFE Lab

Open system page →

Edge cases & failure modes

Where it can mislead

!Baseline K and Strict K belong to ATR threshold logic (ATR SMA × K) — regime triggers for the BE Assistant, NOT trailing-stop coefficients. The manual marks this confusion explicitly.
!High event risk (CPI, FOMC, NFP) can make a wider coefficient dangerous rather than useful — the radar exists to say so before the trade.
!High live spread can invalidate frequent trades or quietly distort EV; the coefficient read is only as honest as the execution costs around it.

Go deeper

Operator briefs on this territory.

Deep dive — 01

ATR authority: letting volatility set the terms.

How ATR coefficients and the authority timeframe anchor stops and break-even moves to actual conditions.

Read the full brief →

Deep dive — 02

The audit loop: how coefficient choices get graded and the ladder stays true.

Select → log → outcome → review → recalibrate. The loop that keeps a fixed ladder honest in a moving market.

Read the full brief →

Deep dive — 03

Changing the ladder: the documented path from finding to production.

Ladders change through the Version Log or not at all. The paper-lined road from calibration finding to production rung.

Read the full brief →

Take it further

Calibration is the opposite of eyeballing an ATR multiple, and it improves with iteration. The Foundry is where the iterations are free.

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