Limitations & Trust Boundaries

This page is a working frame for what Axiom DC can reliably do, what it cannot, what can drift depending on how you configure it, and what the Base trim deliberately does not carry. It is not a disclaimer page. Treat it as the section you would skim before making a decision that depends on the indicator behaving the way you think it behaves — and the section you would re-read on a quiet afternoon when you notice you have started trusting a line without remembering why.

A trust boundary is not a warning to dismiss. It is a short description of where your confidence should stop being free and start being earned by a check you actually did.

What this tool is reliably good at

Axiom DC is a multi-timeframe Donchian stack with a user-defined composite on top. The things it does well, by design:

• Layers up to three honest Donchian channels on a single chart, each at its own higher timeframe, each on the chart symbol.

• Keeps the outer channel bounds raw and lets you choose whether and how to smooth the midpoint basis — so you can see a rough read and a calmer read at the same time without resorting to two indicators.

• Exposes a single, clearly scoped repaint switch. The ON posture is stable history; the OFF posture is live at the cost of redraw. You decide; the indicator does not decide for you.

• Publishes a weighted composite whose rule is named rather than concealed: weighted average for upper, lower, and basis; weight-majority vote for the basis-trend state with a tie-break favoring rising.

• Ships ten alerts that are gated at chart-bar close — six per-slot basis trends, two blended basis trends, two alignment alerts — and exposes two count handles so you can include live counts in custom alert message bodies.

What this tool cannot tell you

• Where price is going next. This is a range-structure tool. A channel touch, a basis crossing, or a basis-trend flip is a computed condition at the moment it happened. What price does after is not the tool's claim to make.

• Whether a given basis-trend is "strong" or "weak." The tool reports a boolean: rising or falling, at this slot, at this Basis Trend Length. Strength is a layer you add; it is not something the tool publishes.

• What the "right" timeframes, lengths, or weights are for your chart. The shipped defaults are a working baseline. They are not a ranking, not an optimized set, and not a recommendation about what to trade. Every number on this indicator is a knob you own.

• Whether the blended channel "agrees with" the market. The blend is a weighted summary of the slots you chose at the weights you chose. It summarizes your inputs, not the market's state.

Trust boundaries on the blend

The blended channel is the part of this indicator readers are most likely to over-trust. Four things to keep in mind every time you look at it:

• It is a composite you authored. Change any weight or enable flag and the blend recomposes. It does not represent a discovered truth about the chart.

• Hidden-plot slots still contribute. A slot with Hide DC NN Plot = true and a non-zero Blended Weight continues to steer the blended channel. If a reader sees the blend move and cannot point at a slot on the chart, the cause is on a hidden slot, not a bug.

• Weight-zero slots are drawn but silent. A slot with Blended Weight = 0 stays visible on the chart and is excluded from the vote. Make sure you know which posture each slot is in before you read the composite.

• Negative weights are not a documented operating pattern. The input does not enforce a friendly minimum, but the blend is written and explained as a zero-or-positive weighted summary. Use zero when you want a visible slot removed from the blend.

• Warmup can draw a useless blend. Missing slot values can be zero-filled internally so the blend stays numeric. Do not trust the blended channel or blended basis alerts until the contributing slot lines are actually plotted.

• The tie-to-rising rule is a convention. On a weight-tied basis-trend vote across enabled, non-zero-weight slots, the blended state resolves as rising. This is a deterministic rule so the state always has a value. It is not a market opinion. If your weights produce frequent ties and the bias matters for your read, adjust the weights to break them or read the slots directly.

Trust boundaries on alerts

Every alert on this indicator is a notification that a computed condition held on a closed chart bar, under the configuration you had when it fired. Specifically:

• Chart-bar close, not higher-timeframe close. Alerts fire at the close of the chart's own timeframe. Under On Bar Close? = OFF, the value the alert was evaluated against may later redraw because the higher-timeframe bar has not yet closed.

• Slot-configuration-dependent. A per-slot basis-trend alert depends on that slot's Basis MA Length, Basis MA Type, and Basis Trend Length. Change any of those and the alert means a different thing on the next bar.

• Global-repaint-dependent. Under ON the alert was evaluated against a confirmed value. Under OFF it was evaluated against a live value. Same alert name, different trust weight.

• Not an execution signal. Nothing in this indicator is a "trigger" for a trade, an entry, or an exit. The tool surfaces computed conditions. The reading is yours.

Hidden-plot slots still participate in alignment alerts. If you want a slot excluded from the alignment vote, disable the slot — do not hide it.

Trust boundaries on the shipped defaults

The shipped defaults — three slots at 5m / 15m / 60m with weights 40 / 35 / 25, Length: 20, Basis MA Length: 1, Type: SMA, Basis Trend Length: 3, On Bar Close?: on — are a working baseline, not a recommended trading configuration.

That distinction matters. A "working baseline" is the smallest set of values at which the tool renders cleanly and teaches itself to a new reader. A "recommended configuration" is something we do not publish, because the right configuration depends on your chart, your timeframe, your instrument, and what you are trying to read. Treat the defaults as a starting point. Change them when you have a reason. Do not treat the shipped numbers as an endorsement.

What's stable across context, and what can drift

• Stable. The slot math, the blend rule, the alert list, and the runtime-error guard are stable across ordinary time-based chart contexts with usable TradingView OHLC data. The code does not contain market-specific branches, but that is not the same thing as a promise that every symbol, chart type, or data history will produce a useful read.

• Drifts with Length:. The tightness of the outer channel depends on Length: and on the volatility of the instrument on the slot's timeframe. A Length of 20 on a choppy small-cap and a Length of 20 on a broad-market index are two different reads.

• Drifts with Basis MA Length and Type:. With the default SMA, the basis shape can move from "raw midpoint" (at length 1) through a range of smoothed shapes as you raise the length and change the type. SWMA is the Lite-library exception because it ignores the user length. The outer bounds do not change with these knobs. Keep that asymmetry in mind.

• Drifts with On Bar Close?. ON produces historically stable lines. OFF produces lines that were live when they were drawn and may have moved. Reading the same chart under one posture versus the other is reading two related-but-not-identical pictures.

What this trim does not carry

The Base trim ships with a focused surface. Some features readers sometimes reach for are intentionally not part of this trim. They are scope decisions, not omissions.

• No alternate-ticker input. Every slot on the Base trim reads highs and lows on the chart symbol. There is no per-slot way to point a slot at a different symbol. If your read depends on cross-symbol range context — for example, overlaying index range on a single-stock chart — reach for the CTX trim (axiom-mtf-dc-ctx). No configuration on this trim will produce cross-symbol behavior.

• No per-slot repaint switch. On Bar Close? is a single global control. You cannot run Slot 01 on ON and Slot 03 on OFF on this trim. For per-slot repaint control, the CTX trim is the right tool.

• No Pro-library smoother catalog. The basis smoother runs through the Axiom MA Lite library, which exposes a narrower catalog than the Pro library carried by the CTX trim. Readers expecting specific Pro-only smoothers will not find them here. If the exact smoother you need is in the Pro catalog, check the CTX trim.

• No more than three slots. The ceiling is three, by design. If you need more simultaneous timeframes on a single chart, the CTX trim opens a wider surface.

• No channel-touch alerts, no breakout alerts, no cross-basis alerts. The ten alerts on this trim are basis-trend and alignment alerts only. If you want alerts on price touching the upper or piercing the lower, you would need to build them in another layer.

• No synthetic-chart correction. The script reads the chart's high and low series as TradingView provides them. On Heikin-Ashi, Renko, range bars, or other synthetic chart types, the bounds describe the synthetic series rather than standard candle highs and lows.

None of the above should be read as a shortcoming. The Base trim is narrower by choice. A reader who wants a focused workbench is not behind a reader who wants a wider one. If the feature you need lives on CTX, use CTX. If this trim fits your actual read, use this trim.

What not to assume when the chart feels persuasive

A working indicator on a liquid symbol tends to produce pictures that feel convincing. A few habits to guard against:

• A narrow blended channel is not necessarily "low volatility." It can be slot agreement or it can be weight-driven cancellation. Check the slots.

• An aligned basis-trend is not "the market has decided." It is a report that every enabled slot with a valid basis is moving the same direction, on its own timeframe, under the lookback you configured. A useful fact, not a verdict.

• A clean-looking basis inside a jagged outer channel is a Length: problem, not a smoothing problem. Basis MA Length cannot fix the bounds because it does not touch them.

• A persuasive mid-bar alert under On Bar Close? = OFF is evaluated on a live higher-timeframe value that may redraw. If you want alerts you can trust unsupervised, run the indicator under ON.

• A slot you cannot remember enabling is still doing work. Configurations you set up three weeks ago are still steering the composite you are reading today. A monthly glance at the inputs dialog is cheaper than acting on a blend whose contributors you cannot name.

This is not about distrusting the indicator. It is about distrusting how confident the picture can make you feel when the picture is composing itself the way you asked it to.

Why this page rewards re-reading

The habits in this pack are easy to hold when you are calm and easy to lose when the chart is doing something interesting. If you find yourself acting on the blend without checking the slots, or setting an alert without noticing On Bar Close? is off, or reading a narrow band as "low volatility" without looking at the weighted split that produced it — those are not mistakes unique to this tool. They are what happens to every reader whose attention has moved faster than their verification. The fix is not harder discipline; it is a page you re-read when you notice the drift.

Come back here when you have made a decision that did not work out and you are not sure whether the tool or the reading is to blame. The answer is almost always in the way the picture was composed. The boundaries above are where to look for it.