Variant Attribution · Checkpoint Ladder
Hit flags explain the EV.
Layer 01 — The checkpoint ladder
Hit flags explain the EV.
0.75R and 1.25R test Time-Conservative banking. 1.3R tests whether delaying first protection actually works. 1.4R tests the Exposure-Conservative bank. 1.6R is the trend unlock. 1.8R tests TNP's delayed trail activation. 2R/2.5R/3R+ diagnose right-tail preservation — are aggressive variants preserving upside or destroying expectancy?
- Rollups: variant count, Avg R by variant, Total R, EV share %, variant-vs-Standard ratio, net R after fees, capture/giveback by variant.
- Variant does not choose the branch. Branch identity comes first; variants tune management inside it.
Layer 02 — Where it lives
Inside Variant Attribution.
Within Variant Attribution, this is one load-bearing idea — worth its own page. The parent module frames it this way: The variant layer compares Standard logic against Time/Exposure Conservative and Aggressive management variants inside each branch. Attribution shows where realized R came from; checkpoint hit rates explain why; the seven-lens matrix decides which variant is even permitted.
How MARS uses this
Every proposed rule change - stop policy, branch weights, fee model - is cloned into a scenario profile and resampled against the same evidence. The grid renders the trade-offs, and only profiles whose edge survives without deepening the P10 tail earn candidate status for live promotion.
How it benefits you
System changes stop being vibes-based. The tempting tweak that costs 0.07R of expectancy for a modest drawdown saving gets rejected by arithmetic before it silently taxes six months of trading - and promising candidates carry their evidence with them into review.
BASELINE
LIVEcurrent governing profile
TIGHTER STOPS
REJECTEDEV cost exceeds drawdown saving
TNP WEIGHT +10
SANDBOXedge up, adverse tail deepens
FEE MODEL B
CANDIDATEfriction saving survives resampling
Four scenario profiles judged side by side: expectancy, adverse-tail cost, and a verdict. Changes graduate through this grid or not at all.
Layer 03 — Flag integrity
Hit flags are recorded at the moment, not reconstructed later.
Each checkpoint flag — 1R hit, 2R hit, BE triggered — is logged when it happens, because reconstructed flags inherit hindsight. A trade remembered as 'almost made 2R' gets recorded generously; a trade flagged live gets recorded truthfully. The ladder's diagnostic power depends entirely on that timestamp discipline.
The governing idea
Connected inside MARS
This module doesn't work alone.
Go deeper
Operator briefs on this territory.
Deep dive — 01
The R levels are not milestones. Each one is a hypothesis with a variant attached.
0.75R interrogates one variant. 1.3R interrogates another. Nothing on the ladder is decorative.
Read the full brief →
Deep dive — 02
The number that grades management is the probability of the next rung given the last one.
Not how many reached 2R. How many of those that reached 1R went on to reach it.
Read the full brief →
Deep dive — 03
From No Data to Hardened: trusting a baseline exactly as much as it deserves.
A baseline built on twelve readings is a guess wearing a percentile. The status ladder says which keys have earned trust.
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.

