Distance Matrix — Operating Doctrine
Three practical questions, answered.
Role in the stack
Translation layer
Best-served branch
Trend No-Partial
Trade signals issued
0
Authorities it overrides
None
Read this first
When to use it
01Before execution. After execution. Not instead of a plan.
Best used before execution when the trade needs a volatility-aware stop or trailing decision, and after execution when the coefficient decision must be captured for review. Normal trades should not be over-engineered with coefficient analysis unless the plan explicitly calls for a runner or trail review — the coefficient battle belongs to the trend branches.
Branch relevance
02Four branches, four levels of dependence.
The guide grades the Matrix's relevance per branch, and the grades are unequal by design:
- Normal — static partial/BE/2R management. Relevance low: use only if stop-distance feasibility is uncertain.
- Trend Partial — partial at 1R plus a runner. Relevance high: the Matrix chooses the runner's breathing room after early monetization.
- Trend No-Partial — the full-position, fat-tail branch. Relevance very high: coefficient choice directly affects survival, variance, and captured outlier R.
- Overflow — supplemental controlled flow. Situational: only if the plan allows trailing logic — never a workaround.
Branch integrity
03The Matrix informs management. It never rewrites identity.
The guide states the rule as doctrine: a Normal trade should not become a Trend No-Partial trade just because price starts moving. The Matrix can support management decisions inside a branch, but branch identity is set before entry and stays set. A strong volatility read on an open Normal trade is interesting; it is not a reclassification.
The workflow position
04Sixth in line, and the line matters.
The clean sequence from the guide: the Cycle Command Console checks cycle evidence and open exposure, the Throttle confirms authorized risk, the Volatility Intelligence Panel confirms the broader regime, the Distance Matrix translates live ATR into exact distance, the Trade Launch Checklist gives final clearance, and TradeZella plus CP3 capture the evidence. VIP first for context, then VDM for translation — a distance without a regime behind it answers the wrong question.
The boundaries
05A translation engine, not a trade signal.
The doctrine's hard limits keep the matrix in its lane:
- It cannot make a disallowed trade valid — volatility context is not permission.
- A favorable volatility read cannot override a restricted gate or System Lock.
- Stop distance must still size inside throttle-approved risk.
- Respect the Sample Status ladder before trusting a zone classification.
Question discipline
06Three questions, because a fourth invites prediction.
The doctrine restricts the matrix to feasibility questions — can price reach this distance, in this regime, in this window — and refuses direction. The restraint is structural: the moment a volatility tool starts answering 'will it go there,' it has left measurement for forecasting, and every downstream consumer inherits the contamination.
How MARS uses this
MARS treats confluence as evidence quality: when independent structures - wave counts, higher-timeframe levels, volatility posture - converge on the same zone, the setup earns a higher evidence grade and access to fuller deployment. Isolated signals remain tradeable but are sized as the weaker evidence they are.
How it benefits you
Setup quality becomes a graded input instead of a binary feeling. Your best-evidenced trades systematically carry more of the risk budget, marginal trades stop consuming full-size authority, and 'A+ setup' finally has a definition that survives review.
Independent structures resolving to the same point. One wave is an opinion; agreement between unrelated structures is a signal.
Reference
Where the Matrix sits in the authority stack
| Layer | Its question | Relationship to the Matrix |
|---|---|---|
| Trading Plan / hard rules | What can be traded, when, under what branch doctrine? | The Matrix must obey it — it cannot validate a disallowed trade |
| Gate / Drawdown state | What capital posture governs risk? | A favorable read never overrides a restricted gate or System Lock |
| Throttle Control Panel | What tier, pool, and per-trade size are authorized? | Matrix distance must size inside throttle-approved risk |
| Volatility Intelligence Panel | What is the broader volatility regime? | Read VIP first for context, then VDM for exact distance |
| Volatility Distance Matrix | What does live ATR mean in stop distance? | Translates ATR into pips, zones, ratio, and the coefficient ladder |
| Trade Launch Checklist | Final go / no-go? | Distance known and acceptable becomes a clearance check |
| Trade Capture / CP3 / SDE | What happened, and what gets reviewed? | Coefficient, zone, ratio, and distance are logged for review |
Use cases
Where it earns its place
- ▸Pre-entry feasibility: classify a candidate stop as Efficient, Wide but Acceptable, Inefficient, or No-Trade Distance before clearance.
- ▸Post-execution capture: record coefficient, live ATR, zone, ratio, and session so Saturday's review can grade the decision.
- ▸Session sanity check: verify a familiar distance still means the same thing in an unfamiliar session before trusting it.
Go deeper
Operator briefs on this territory.
Deep dive — 01
The matrix is consulted before execution and again after it. It is never consulted instead of a plan.
Two moments, and neither of them is the moment you are deciding whether to trade.
Read the full brief →
Deep dive — 02
The matrix exists to reduce hesitation. A version that produced more of it would be a worse tool with better outputs.
Correct outputs are not free. Each one costs a decision, and some of those decisions did not need to exist.
Read the full brief →
Deep dive — 03
The override exists — and every use of it is priced.
A logged override is a decision. An unlogged one is a discipline breach — and the benchmark counts both.
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.