Limitations and Trust Boundaries

This is not a disclaimer page. A disclaimer page exists so the publisher is protected. This page exists so you know what the tool is actually good at, what it cannot tell you, and what you are choosing every time you keep using it. Read it as trust-setting, not as legal boilerplate.

What the Base trim is reliably good at

When used within its designed scope, the Base trim does a specific job well:

• It draws up to three independent Bollinger stacks on one overlay, each configured to its own price source, moving-average type, length, standard-deviation multiplier, and timeframe.

• It evaluates each slot's Bollinger calculation inside that slot's higher timeframe, rather than resampling chart-bar values and calling the result a higher-timeframe read.

• It offers a single, named switch that decides whether each slot reports confirmed higher-timeframe values or live higher-timeframe values, and it is consistent about applying that choice to every slot together.

• It composes a blended band from the slots you enabled with non-zero weight when the contributing weights sum above zero, using a rule — weighted average for the bands, weight-majority vote for the basis trend — you can hold in your head and verify on your own chart.

• It fires ten alerts on chart bar close, covering per-slot and blended basis-trend direction plus full alignment, with a pair of hidden count plots available for alert messages.

If that list is what you want, the trim is doing its job.

What the Base trim cannot tell you

Several things readers sometimes want from a Bollinger indicator, this one does not do:

• It cannot tell you whether a trade is a good trade. Nothing in this indicator is structured as a setup, a signal, a confirmation, or a trigger. The alerts name conditions; the rest is your decision.

• It cannot tell you what the market is doing from the blended band alone. The blended band is a composite of weights you set. When the slots agree, the composite concentrates that agreement. When the slots disagree, the composite averages the disagreement. It does not distinguish between those two states on its own — that is a read you make by checking the slots under the blend.

• It cannot tell you what a higher-timeframe bar will close at. Under On Bar Close? OFF, the slot is reading a live higher-timeframe bar. The live read is honest about being live; it is not a prediction of the close.

• It cannot tell you what a slot's basis means. A basis is a moving average of a price source on a higher timeframe. It is a description. The interpretation — whether rising means trending, whether flat means consolidation, whether a basis cross means anything — is a decision you bring to the tool.

Stating these out loud is not a product limitation to apologize for. It is how the tool stays honest.

Trust boundaries on the blended band

The blended band is the element readers over-trust most, so it deserves its own cluster.

• The blend does not know anything its components do not know. It is a weighted composite of enabled, non-zero-weight slots when those weights sum above zero. Three slots, three weights, one rule. If every slot is noisy, the blend is a weighted average of noise. The weights do not launder the inputs into a cleaner signal.

• The blend does not guard every weight edge for you. The Blended Weight: inputs do not declare a minimum. Keep normal configurations at zero or positive values and keep the contributing total above zero. If the contributing total is zero or negative, the script falls back to zero values rather than a useful blended band.

• A weight of zero is a specific tool. It displays the slot's lines and excludes it from the blend. It is not a way to turn a slot "mostly off." Either the slot steers the blend or it does not; make that call explicitly.

• Hiding a slot does not exclude it from the blend. Hide BB 0N Plot is a cosmetic control. The slot is still computed, still weighted, and still contributing. If a chart looks like the blend is shifting without visible cause, check for hidden slots before you check anything else.

• The blended basis-trend is a vote, not a curve reading. The trend state reported by the blended-basis alerts is the weight-majority across the slot basis states, with ties counted as uptrend. A near-flat blended basis curve can still report "uptrend" if the uptrend-voting slots carry more weight than the downtrend-voting slots. That is not a numeric glitch — it is the rule this page, and For the Geeks, state out loud rather than bury in behaviour.

Trust boundaries on the alerts

Every alert this indicator fires is gated by the close of the chart bar in which the condition held. That is the whole claim. In particular:

• An alert does not confirm the underlying higher-timeframe bar has closed. Under On Bar Close? OFF, the slot may be reading a live higher-timeframe bar. The chart-bar gate makes the alert clean with respect to the chart; it does not make the slot clean with respect to the higher-timeframe side.

• An alert does not confirm intent or direction. It names a computed condition. The condition may or may not mean something useful for your process; that judgment is yours.

• Alignment alerts include hidden-plot slots and exclude disabled slots. The set of slots the alert is reasoning over is the set you enabled, visible or not. If the alignment alert is silent when two slots obviously agree, check whether a third enabled slot — visible or hidden — disagrees.

• Partial agreement is not alignment. Two-of-three is not a missed alert. Alignment requires every enabled slot with a non-na basis to agree.

• The hidden count plots are not alerts or Data Window rows. They are display.none plots available for alert message placeholders and platform consumers that can reference hidden plots. What TradingView does with them inside a message template is platform behaviour, not indicator behaviour.

What this trim is not, scoped directly

The Base trim is the focused starting surface in the Axiom BB family. It ships a specific surface on purpose: three chart-symbol slots, one global timing posture, and the Lite moving-average set. It is not a diminished version of a larger tool; it is the version for readers who want this surface specifically. With that said, naming what it is not is useful because readers carrying expectations from other Axiom tools can carry them in here without noticing.

• No cross-ticker or cross-symbol bands. There is no Optional Ticker input. Every slot is computed on the chart symbol in the slot's chosen timeframe. No external symbol is re-projected into chart price space. If you need cross-ticker bands — say, reading SPX bands on an ES chart — that lives in the CTX trim. Not here.

• No per-slot repaint control. On Bar Close? is a single global switch that governs every slot. There is no per-slot override. If your workflow needs one slot live and another confirmed, the CTX trim exposes that control. The Base trim does not.

• No Pro moving-average parameter surface. The Base trim is bound to the Axiom MA Library Lite. The Type: picker is the full moving-average surface on this trim. Per-moving-average parameters — ALMA offset, Jurik phase, KAMA and FRAMA length controls, Laguerre alpha, VAMA vol length, and similar — live in the Pro library, which the CTX trim uses. For the types you can choose on this trim, cross-link at Axiom MA Library (Lite).

• No slot count beyond three. There are three slots. If your read genuinely requires more independent Bollinger stacks on the same chart, that is a CTX trim conversation.

• No band-touch, squeeze, or crossover alerts. The alert set is documented in Alerts. Events outside that set — a price crossing a band, a basis crossing price, bands narrowing — are not exposed as alerts by this indicator.

If one of these limitations is in your way, the answer is not to force the Base trim to pretend it has the feature. The answer is to route to the CTX trim or to add another layer on your chart. Stretching the Base trim past its surface quietly is how misconfiguration settles into a workflow.

What you are choosing when you trust this indicator

Every time you act on what the chart is showing, you are accepting a small set of implicit choices. Making them explicit:

• You are choosing the repaint posture. ON or OFF, and — on this trim — on every slot at once. The cost of each posture is real in its own direction. You are making that tradeoff on purpose if you read MTF and Repainting; you are making it by accident if you do not.

• You are choosing the blend rule. The weights are yours. Equal weights is a statement. Uneven weights is a statement. Zero-weight is a statement. The blended band reports what you said to report.

• You are choosing the lookbacks. Length: and Basis Trend Length: are two different knobs for two different questions; keeping them in their own lanes is a choice.

• You are choosing which slots participate in alignment. Disable silently removes; hide silently keeps. Make those choices on purpose.

• You are choosing what to do with each alert. The tool reports a condition at chart bar close. What you read into the condition is the part the tool cannot do for you.

The reason to write these out is not to make the tool sound more serious than it is. It is to protect something specific: your ability to go back after a bad day and trace the decision through. A configuration you can read back as sentences — "I was reading a confirmed higher-timeframe posture, I was weighting the 60-minute slot higher because the setup was about context not trigger, I was tolerating two-bar flicker on the basis-trend because I wanted the state to flip fast" — is a configuration you can revise deliberately. A configuration you cannot reconstruct is a configuration that will drift, because every time you touch it you will be re-guessing at the reasoning you did not record. The tool supports either posture. It cannot build the recording habit for you.

A closing note on the shipped defaults

The defaults — three slots at 5 / 15 / 60, Length: 20, StdDev Mult: 2.0, Type: SMA, Basis Trend Length: 3, equal weights, On Bar Close? ON — exist so the indicator loads cleanly on a fresh chart and lets you see what three slots at three timeframes looks like before you make any configuration decisions. They are not a ranking and they are not a tested benchmark. Treat them as the shape of the surface, not as the shape of a correct answer, and tune on purpose from there.