The week is the machine: MARS as a repeating rhythm.

Why a rhythm at all

Governance that isn't scheduled is governance that's optional.

Every control in MARS has a moment in the week when it's supposed to fire, and the rhythm is what guarantees the moment arrives. A checklist consulted 'when needed' is consulted until the first exciting setup; a journal updated 'regularly' decays into backfill; a review held 'when there's time' is held in good months and skipped in the months that needed it. The weekly loop removes the discretion about when discipline happens — trades during the week, capture in the moment, entry on Saturday, interpretation after, posture set before the next session opens. What's left discretionary is the trading. The schedule never is.

The loop's stations

Five stations, one revolution per week.

The revolution runs: governed execution through the live sessions, with the Trade Launch Checklist cleared before each entry and the Cycle Command Console tracking cycle evidence and open exposure as trades resolve. Paper capture immediately after each execution — one Trade Capture Document sheet per trade, completed as outcomes finalize. Saturday entry, where every paper sheet is transferred into the CP3 Journal and verified against the TradeZella digital record. Weekly interpretation, reading the Weekly Summary, EV Scorecard, and Gate/Brake state that the closed journal now feeds. And re-arming: the throttle's next-cycle authority, informed by the week's closed evidence, sets the posture the new week opens under.

The load-bearing gap

The week's genius is the deliberate delay between doing and judging.

Notice what the rhythm refuses to do: it never asks the operator to interpret performance mid-week. Trades are executed and captured, but the evidentiary verdict — hit rates, branch EV, week status — is computed only after the record closes on Saturday. That gap is protective in both directions. It keeps a hot Tuesday from inflating Wednesday's sizing, because the throttle's structural inputs only update on the weekly close; and it keeps a cold Thursday from triggering mid-week rule surgery, because there's no fresh verdict to panic over — only the gate ladder, which responds to drawdown arithmetic and nothing else. During the week, the operator executes and records. Judgment has an appointment, and it isn't today.

• Mid-week, only capital-state authority moves — gates respond to drawdown in real time; verdicts wait for the close.
• The paper capture is what makes the delay safe: nothing is trusted to memory across the gap.
• A week that was never closed properly cannot be interpreted properly — the Saturday station is not skippable.

The nested cadences

Slower loops ride on the weekly one.

The weekly revolution is the base gear; the monthly, quarterly, and structural cadences are gears that turn only because it does. Monthly reads — capital dynamics, regime classification, benchmark comparison — consume four or five closed weeks. Quarterly reviews consume the monthlies. The structural layer consumes all of it. None of these deeper examinations has an independent data supply: they are all downstream of the same Saturday close, which is why a single sloppy week quietly degrades every horizon above it. The rhythm isn't one process among several. It's the one all the others are made of.

The key idea

Consistency is the feature; the loop is how it's manufactured.

The workbooks are strongest when used consistently and weakest when inputs are incomplete or backfilled carelessly — the manuals say so outright. The weekly rhythm is the mechanism that makes consistency structural rather than aspirational: every control has an appointed moment, every record has a closing bell, and every judgment has a waiting period. Operate the loop and the system's evidence compounds. Operate the modules without the loop and you own eleven workbooks and no system.