The binary switch: Normal or Trend, decided before anything else volatility says.

Why binary

The management fork is binary, so the regime read is too.

The system's exit architectures split cleanly into two families: static management (Normal's partial-at-1R, runner-to-2R) and trail management (the trend branches' unlock-and-trail structures). There is no third family and no blend — a trade is managed one way or the other, decided at entry. The regime read matches the decision it feeds: Normal or Trend, nothing in between. The restraint is deliberate. A seven-state volatility read is the right resolution for pricing a trail's width; it's the wrong resolution for a fork with two prongs, where intermediate states would just manufacture hesitation at the exact moment the checklist demands a committed branch selection.

The two doctrines

What each side of the switch actually prescribes.

The routing is fully specified in the architecture manual's own words: when the regime is Normal, the trade runs Normal rules — breakeven armed at 1.4R, static 2R-style management for the runner. When the regime is Trend, trend rules apply — breakeven at 1.6R, and the ATR trail logic takes over the runner. The 0.2R difference in BE timing is not cosmetic: Normal's earlier arming reflects a structure whose ambition is capped at 2R and whose priority is converting the ordinary continuation safely; Trend's later arming buys the position room through the 1.6R unlock zone, accepting more open risk in exchange for not strangling the very continuation the branch exists to capture. Two BE points, two runner logics, one switch.

Position in the sequence

The switch fires first — everything volatile downstream assumes it.

The volatility layer's internal ordering puts the regime read at the front: the switch decides Normal versus Trend, branch doctrine then determines whether a trail exists to price, and only then do the VIP's ladder and the matrix's distances engage. The transcripts locked this sequence explicitly when separating the coefficient's job from the regime's — the ATR/BE regime switch tells you Normal versus Trend; the coefficient tells you how much breathing room the trail deserves inside that framework. The checklist enforces the same order at launch: ATR regime identified, branch selected correctly, before stop logic and volatility distance are even reached. A trade that skips the switch and goes straight to coefficient shopping has already made its branch decision implicitly, which is exactly the unexamined routing the sequence exists to prevent.

• Regime read → branch eligibility → (if trail) coefficient pricing. The order never inverts.
• A Normal-regime read makes the entire coefficient apparatus irrelevant for that trade — correctly.
• The switch informs branch selection; it doesn't force it. Discretion still declines trades in either regime.

The honesty stakes

Regime at entry is also a data commitment.

The switch's output doesn't just route the live trade — it enters the record as the trade's ATR State, and the analytics stack slices by it: conditional EV by ATR state, branch integrity checks, the weekly diagnostic question of whether Normal and Trend regimes were classified correctly at entry. That makes the entry-time read a permanent evidentiary claim. A regime call revised after the outcome — the Normal trade that trended, retroactively remembered as a Trend read — corrupts the same populations the branch-mismatch doctrine protects: the conditional slices stop meaning anything if the condition was assigned in hindsight. The rule is the same as everywhere in the evidence layer: the read is made before entry, logged as made, and graded later against what actually happened — which is precisely how the switch itself gets calibrated over time.

The key idea

One clean fork beats a sophisticated muddle.

The BE Assistant is the least glamorous tool in the volatility layer and among the most load-bearing: a binary read, two fully specified doctrines, a fixed position at the front of the sequence, and a logged answer every trade. Its simplicity is what makes the sophisticated tools behind it safe to use — the ladder can afford seven tiers because the fork it serves has exactly two, and every coefficient ever priced inherits its legitimacy from a switch that was read honestly first.