Operator brief · 437

The brake is chosen months early, by someone who is not losing money.

The key idea

The transfer

A rule written in advance is a decision taken away from your future self.

Stress testing produces the depth, frequency and duration the account should expect. Its output is not the numbers — it is the response chosen against them: which brakes apply at which state, what the daily and weekly limits are, what happens at each gate. Those choices are made in advance precisely so that they are not available for revision later. The operator at the floor is not consulted, because the whole architecture rests on the observation that they should not be.

Why the calm operator is the better judge

The two decision-makers have access to different information.

This is not a claim that the future operator is weak. It is that they are worse positioned. The calm operator can see the entire distribution and reason about the average case across all of it. The operator at the floor sees one path — the one they are standing in — with maximum vividness and no view of the others, while holding a position that makes one answer far more comfortable than the other. Judgement made under those conditions is not a worse version of the same judgement. It is a different question being answered. This is why the rule is written as an instruction to a future person rather than as advice: advice is weighed against present circumstances, and the whole value here lies in a decision that does not get weighed again.

FigureWho is setting the rule, and what they can see

The same operator, two conditions, two very different information sets.

The condition that makes it work

It only binds if it was specific.

A predefined response has force in proportion to how little interpretation it permits. An intention to reduce risk if things get bad provides no constraint whatsoever, because both terms will be defined at the moment of use by the person who needs them to mean something convenient. A response that names the state, the threshold and the action leaves nothing to be settled later. The daily and weekly brake limits are written the same way and for the same reason — as states and thresholds rather than intentions. The test of a brake rule is simple: could two people read it during a drawdown and disagree about whether it had triggered? If so, it is a sentiment rather than a rule. Specificity also makes the rule auditable after the fact, which matters more than it sounds: a vague rule cannot be shown to have been followed, so a record built from vague rules proves nothing about the operator who kept it.

Grounded, not guessed

The thresholds come from the distribution, not from a round number.

Predefinition without stress testing produces arbitrary limits, and arbitrary limits get overridden because everyone involved knows they were arbitrary. The value of running the simulation first is that the response is calibrated to what these rules actually do: brakes set against depths the distribution says will genuinely occur, gate expectations matched to how often the model says defensive states should be visited. A threshold that the operator has seen justified by fifty thousand paths is markedly harder to argue with at the floor than one chosen because it sounded prudent.

Deviation is the real output

The rule's second job is to make breaking it visible.

A predefined response will occasionally be broken, and the system does not pretend otherwise. Its more durable contribution is that a written rule converts a deviation into a recordable event: without it, an operator who reduces risk late or overrides a brake has simply exercised judgement, and there is nothing to notice afterwards. With it, the same act leaves a trace with a date and a reason attached. Over enough cycles that record is the most valuable diagnostic material the account produces, because it describes the operator rather than the market.

The standing exception

Revise the rule between drawdowns, never inside one.

None of this makes the response permanent. Thresholds should be revisited as evidence accumulates, and a rule that the record shows to be miscalibrated ought to change. The single constraint is timing: revision happens when the account is not currently being tested by the rule in question. A threshold amended while it is triggering is not a revision, it is an override with better manners — and the practice of allowing it, once established, dismantles every other predefined response in the system at the same time.

Connected inside MARS

Drawdown Stress Testing →

Drawdown Control →

Cycle Command Console →

Monte Carlo Lab →

Every brief documents the same shipped system.

The complete MARS package — eleven workbooks, three TradingView indicators, the full manual library — $497.

Get MARS Pro — $497 Explore the Platform