Skip to content

Execution Efficiency · The Saturday Pass

Reconcile first. Grade second. Always in that order.

Weekly slot

SATURDAY

Repair themes

1

Graded after

RECONCILIATION

Layer 01 — The sequence

Data quality, headline metrics, weekly rollup, then the drill.

The pass runs in a fixed order after reconciliation: confirm the data quality flags are clean, read the core metrics for the week, open the weekly rollup for adverse excursion counts, weak capture, fee drag and swap exposure, and only then drill into the selected week. Skipping to the drill produces a detailed investigation of whichever week looked most interesting, which is not the same as the week that most needed looking at.

Layer 02 — The cleanliness check

A profitable week still gets audited.

Profit is not a certificate. A week that made money while capturing little of the opportunity it generated, surrendering a large share of open profit, and paying heavy friction is flagged as low-quality alpha, and it is flagged specifically because nothing else in the review stack will object to it. The account grew, the dashboard is green, and the process that produced the result is degrading. This is the single most valuable check in the pass.

Layer 03 — One theme, not a list

The week closes with a single recorded repair.

One repair theme is recorded for the coming week rather than a resolution list. The constraint is deliberate. A list of six improvements is a list of six things that will not happen, and it also makes attribution impossible: if six things change and results move, nothing has been learned. One change, carried for a week, produces evidence. The remaining findings stay in the notes and wait their turn.

Layer 04 — Localise before generalising

Branch and timeframe drills come before any system-wide change.

A weakness that appears at the account level is almost always concentrated somewhere: one branch, one timeframe, one session, one cost condition. The branch and timeframe views exist to find that concentration before a global rule is adjusted, because a system-wide change made to fix a localised leak damages the parts that were working in order to repair the part that was not.

  • Red weeks get the adherence and excursion check before being ruled variance versus execution failure.
  • Timeframe analytics catch structural mismatches that outcome data alone will never surface.
  • Persistent weakness across several weeks becomes structural evidence for the longer-horizon review.

Reference

The pass, condition by condition

What the week showsLikely meaningCorrect response
Profitable week, poor capture, high giveback, heavy feesLow-quality alphaFlag it. Profit does not exempt a week from the cleanliness check
High adverse excursion count across the weekEntry timing or stop placement is driftingDrill the branch and timeframe before touching anything system-wide
High opportunity generated, weak final resultsManagement is failing to monetizeReview trail, breakeven, and partial logic; inspect giveback directly
Elevated fee drag or swap exposureFriction is consuming expectancyAvoid the conditions or require better reward potential
Red week with high adherenceProbably normal varianceDo not rewrite the system from one clean loss
Green week with low adherenceLucky result, weak process evidenceDo not count it as clean alpha; log the deviation
Short-timeframe trades carrying swap exposureStructural mismatchInvestigate the branch and timeframe pairing, not the outcome

The governing idea

Connected inside MARS

This module doesn't work alone.

Go deeper

Operator briefs on this territory.

Every module ships in the complete MARS package.

One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.