Limitations and Trust Boundaries

This page matters because Axiom DC Pro can look more decisive than it really is, especially once several layers collapse into one tidy blended view. Whenever a configurable tool compresses several contexts into one summary view, the chart can start looking settled before the design choices behind it are settled. The blended channel may look calm while the stack underneath it still needs verification. That is the failure mode to watch most closely here. The risk is usually not hidden behavior. The risk is a thoughtful-looking stack built from choices that were never thought through enough. The goal here is not to scare you away from the indicator. It is to keep the tool in the right role. Read this page before you add heavy weights, alternate tickers, or alert automation on top of a stack you have not fully checked yet.

What you can trust, if you verify it

You can trust this indicator to help you do a few specific jobs:

• keep several Donchian contexts visible in one place
• show where current chart price sits relative to each active basis line
• summarize selected contributors into one blended channel
• surface basis-state, alignment, and blended-cross conditions through alerts

Those are real jobs. They are also narrower than "tell me what to do next."

The first hard boundary: chart timeframe fit

Each enabled slot has to run on the chart timeframe or a higher timeframe. If you place the default `5 / 15 / 60` stack on a chart above five minutes without adjusting it, the runtime error is telling you the stack does not fit the chart. It is not telling you the indicator is broken. That matters because a bad first fit is easy to mistake for bad tooling.

The second boundary: confirmed versus live-forming slot values

`On Bar Close?` is a per-slot trust choice.

When a slot has it on:

• that slot uses the last closed higher-timeframe values
• that slot is easier to compare across history and live use
• that slot carries a stronger default trust posture

When a slot has it off:

• that slot can update from the still-forming higher-timeframe bar
• that slot can react earlier
• that slot also carries a weaker trust boundary because what looks settled later may not have felt settled in the moment

That is why this manual refuses blanket non-repainting language. The script gives you a steadier confirmed mode to document and verify. It does not free you from checking which slots are running in which mode.

The third boundary: remapped alternate tickers are contextual, not native

When you set `Optional Ticker:` on a slot, the script pulls that slot from another market and remaps it into the current chart's price area. That can be genuinely helpful. It keeps related-market structure on one panel instead of forcing you to keep flipping charts. It can also mislead if you stop at the visual result. Once the remapped channel sits in your chart's price region, it can start to feel native. It is not. It is translated context.

The safer verification habit:

1. keep the alternate-ticker slot at `0` blend weight first
2. compare it to that market on a separate chart
3. decide whether the relationship is helping before you let it shape the blend

The fourth boundary: the blend compresses choices, it does not certify them

The blended channel only reflects enabled slots whose `Blended Weight:` is not `0`. That means the blend inherits:

• your chosen timeframes
• your chosen basis styles
• your chosen weights
• your slot-by-slot timing posture
• any alternate-ticker remapping you allowed into the contributor set

So the blend is useful as a summary, not as proof. If the contributor set is thoughtful, the blend can reduce clutter well. If the contributor set is careless, the blend can make weak choices feel organized.

The fifth boundary: hidden and zero-weight slots still matter

These are easy to misread.

• a hidden slot still exists
• a zero-weight slot still exists
• only a disabled slot is actually gone

That means a zero-weight slot can still plot, flip basis state, and affect alignment alerts. A hidden weighted slot can still shape the blend. If you do not keep that straight, the chart can start "mysteriously" disagreeing with you when the logic underneath it is actually doing exactly what you asked.

The sixth boundary: alerts are prompts, not conclusions

All alert conditions are chart-bar-close gated, which helps keep the alert surface cleaner. That still does not make an alert self-justifying.

• a slot state alert is only as good as the slot behind it
• a blended alert is only as good as the contributor set behind it
• an alignment alert is only telling you that the active basis lines agree, not that the trade is finished

Treat alerts as review prompts that pull your attention back to the chart. Do not ask them to carry the reasoning for you.

The edge case you should know now, not later

If every enabled slot has `Blended Weight:` set to `0`, the blended output stops being meaningful in the current build. This is not a clever hidden mode. It is a sign that the summary layer has no real contributors left. If you choose that configuration, stop reading the blend and work from the slots themselves.

What this tool cannot decide for you

It cannot decide:

• which timeframe ladder fits your market and chart
• whether a smoother basis read is actually more useful for your workflow
• whether a remapped outside market is adding signal or adding story
• whether full-stack basis agreement matters enough in the current context
• whether earlier live-forming information is worth the weaker trust boundary

Those decisions still belong to you.

A fast trust checklist

Before you lean on the chart, check these:

1. Every enabled slot timeframe is valid on this chart.
2. I know which active slots are confirmed, live-forming, or mixed.
3. I can name which slots are shaping the blend and which ones are only diagnostic.
4. I know whether any hidden slot or zero-weight slot still matters somewhere else.
5. I can explain why each non-zero-weight slot belongs in the summary.
6. I know whether any contributing slot is remapped from another ticker.
7. I am treating alerts and alignment as prompts, not verdicts.

If you cannot clear those checks, the indicator is ahead of your understanding. Slow it back down.

When this indicator is the wrong fit

This tool is a poor fit when:

• you want one fixed Donchian answer instead of a configurable stack
• you do not want to verify higher-timeframe behavior
• you expect alternate-ticker context to be self-explanatory
• you want the blend to make the slot-level design work disappear
• you mainly want the chart to feel simpler without keeping track of the choices that made it look simpler

Used honestly, Axiom DC Pro can make layered channel work easier to manage and verify. Used carelessly, it can make a weak stack look more settled than it is.