The panel owes the trend branches a guarantee. It owes the static branches an opinion.

The dependency map

Two branches are volatility-quoted end to end; two are volatility-aware and structurally static.

Trend Partial and Trend No-Partial depend on the panel for things they cannot compute otherwise: which coefficient the trail should run at, how wide the envelope needs to be for the instrument's current state, whether continuation conditions justify the management posture at all. Remove the panel and those branches lose a required input. Normal and Overflow are static by design — a fixed break-even level, a fixed target, no trail — so no panel output enters their management. They still benefit from the reading, but as context rather than as a parameter, and the difference between those two roles is what the tiering encodes.

Why tier the guarantee

Freshness is expensive, and paying for it uniformly means underpaying where it matters.

Keeping a volatility read genuinely current has a cost measured in operator attention: refreshing baselines, confirming windows, checking that the intelligence read has not aged past its doctrine. Applying that discipline everywhere sounds rigorous and produces a predictable outcome — the operator does it approximately everywhere and rigorously nowhere. Concentrating the strict guarantee on the two branches where a stale coefficient changes a stop distance means the discipline is small enough to actually hold, and the consumers who genuinely need it are the ones who get it.

What the static branches still get

Context is not a consolation prize; it is the skip signal.

It would be easy to read advisory status as meaning the panel is irrelevant to a Normal trade, and that is wrong in one important way. The static branches do not consume a coefficient, but they do care whether the instrument is currently in an extreme state — because extreme conditions argue for standing aside rather than for wider management, and standing aside is available to every branch. A Normal setup in a violently expanded environment is a fixed-target trade in a market that will overshoot the target's neighbourhood in both directions. The panel cannot change how that trade would be managed. It can inform whether it is taken.

• Static branches use the reading as a participation decision, not a parameter.
• Extreme zones argue for skipping, which is a decision every branch can act on.
• That is a genuine use, not a courtesy — it is simply a different one.

The resourcing argument stated plainly

Casual consumers should not pay for rigour they do not use.

There is a design principle underneath this that recurs across the system. Every guarantee a tool offers is paid for by someone, usually in operator time, and a guarantee extended uniformly is a tax on the consumers who did not need it. Tiering makes the cost land where the benefit lands. It also makes the tool honest about itself: a panel that claimed uniform freshness across all consumers would either be lying or be imposing a maintenance burden heavy enough that it gets skipped, at which point the claim is false anyway and nobody knows which readings are current.

The failure this prevents

Uniform service invites a static-branch operator to act on a coefficient they have no use for.

The subtle risk of presenting every reading identically to every consumer is that it implies every consumer should act on it. A Normal-branch operator reading a recommended wide coefficient, with no tiering to tell them the recommendation is not addressed to them, has an obvious next thought: perhaps this trade should be managed with a wider stop. That thought is the beginning of a static trade acquiring trend management, which is the identity drift the branch architecture exists to prevent. Naming who the output is for is a small piece of copy doing real structural work.

The key idea

Say who a tool is for, or its outputs will be acted on by people it was not built to serve.

The volatility panel is unusually explicit about its audience and that explicitness is the point rather than a stylistic preference. Every module in the system has a primary consumer and a set of secondary ones, and the difference between them is not politeness — it determines what guarantees are owed, what maintenance is justified, and which readings should change someone's behaviour. A tool that never states its audience will eventually be used as though everyone is it.