The trade arrives into a management contract already signed.

The two doctrines

Normal regime and Trend regime hand the trade different rules.

The ATR BE Assistant classifies the environment before entry, and the classification selects a management doctrine wholesale. Normal regime: break-even at 1.4R with a static 2R runner structure. Trend regime, in session: break-even at 1.6R with ATR-trail continuation logic. These are not adjustable dials that an operator tunes as the trade develops — they are two different contracts, and which one applies was settled at clearance in the same section that fixed the branch. Coefficient selection then routes through the Volatility Intelligence Panel and the Distance Matrix rather than being eyeballed from raw ATR.

The identical-entry point

Two trades that look the same on a chart are not the same trade.

This is the consequence operators find most counterintuitive: the same pair, the same entry price, the same stop distance, taken in two different ATR regimes, are correctly recorded as two different trades with different expected behavior, different checkpoint ladders, and different branch identities. Nothing about the chart distinguishes them. Everything about how they will be managed, what they will be judged against, and what evidence they contribute is already different — because the regime that governs them was read before either was taken.

Why front-load it

Mid-trade is the worst available moment to choose a management style.

The reasoning mirrors the clearance argument. A management decision made while a position is open is made by an operator watching unrealized profit move, which is the condition under which judgment is least reliable. Front-loading moves the decision to a moment when the trade is still hypothetical and nothing is at stake emotionally. The system pays for that with rigidity — the contract cannot adapt to information that emerges after entry — and accepts the cost knowingly, on the same reasoning that puts the sober checklist sections before the exciting one.

The volatility routing

Coefficients come from the matrix, and the matrix is not the ATR reading.

The instruction to route coefficient selection through the Volatility Intelligence Panel and Distance Matrix instead of eyeballing raw ATR is a guard against a specific error: treating a high live ATR as authorization for a wider trail. The scenarios table names the failure directly — live ATR looks exciting but the authority-timeframe relation is not supportive, and the correct response is to avoid coefficient overreach and use the matrix rather than emotion. Volatility being elevated is not the same as volatility being supportive, and only the matrix distinguishes them.

• Live ATR is an observation; authority-timeframe support is the qualification.
• The Distance Matrix converts both into a coefficient — a lookup, not a judgment.
• Every coefficient decision is logged, so a bad month traces to specific choices rather than to vibes.

What the contract enables

A pre-signed contract is what makes the trade auditable afterwards.

Because the management rules were fixed before entry, the post-trade review can ask a question it otherwise couldn't: did the trade get managed the way it was supposed to be? Plan adherence becomes a checkable fact rather than an impression, and the distinction the manual insists on — separating good process from lucky outcome — becomes available. A trade improvised into profit and a trade managed to plan into profit look identical on the P&L and are recorded very differently, which is only possible because the plan existed in writing before the outcome did.

The session qualifier

Trend doctrine carries an in-session condition that Normal does not.

The trend management contract is specified as break-even at 1.6R with trail continuation logic *in session* — and the qualifier is load-bearing rather than descriptive. Trail-based management depends on continuation, and continuation depends on there being participation to continue it; a trail activated into a thinning session is being asked to work in conditions its coefficient was never calibrated for. The Normal contract carries no equivalent condition because static exits do not care what happens between checkpoints. This is one of the clearer illustrations of why the two doctrines are separate contracts rather than one contract with adjustable parameters.