Visuals and Logic

This page is about reading what is on the chart without giving it more authority than it has earned.

The easiest way to stay grounded is to read Axiom DC Pro in layers:

1. understand one slot first
2. understand what the basis line adds to that slot
3. understand what the blended channel is compressing
4. understand what the chart is not telling you by itself

If you skip straight to the blend, the chart can feel clearer than your interpretation really is.

Start with one slot

Each active slot draws three lines:

• an upper Donchian boundary
• a basis line
• a lower Donchian boundary

The upper and lower lines define the raw channel bounds for that slot's chosen timeframe and symbol context. The basis line is the midpoint of that channel after optional smoothing has been applied.

That last part matters. The basis is not a separate market truth. It is the slot's smoothed center line.

What each visible element means

How to read price versus basis

The indicator's main state logic is simple on purpose:

• a slot is above basis when chart price is at or above that slot's basis line
• a slot is below basis when chart price is below that slot's basis line
• a slot's Basis Change condition marks the flip between those two states

That means the core question is not "Did the indicator discover a hidden regime?" The core question is "Where is current price sitting relative to the basis lines I chose to trust?"

This is why the docs keep returning to slot roles. A basis state only means as much as the slot underneath it deserves.

Why the basis can move when the channel edges do not move the same way

This is one of the quickest ways to verify how the script is built.

When you change Basis MA Length: or Type:, you are changing how the midpoint basis is smoothed. You are not turning the upper and lower channel edges into a different Donchian calculation.

The fastest proof:

1. leave one slot active
2. change only Basis MA Length: or Type:
3. watch the basis line respond
4. compare that to the outer channel edges

If the basis line changes more than the outer bounds, the script is behaving as intended.

What the blended channel is actually doing

The blend is a summary layer, not an eleventh normal slot.

The useful mental model is:

• each active slot does its own work first
• the blend only looks at enabled slots whose Blended Weight: is not 0
• upper values, basis values, and lower values are summarized separately

So the blended channel is not asking, "What would one Donchian channel look like here?"

It is asking, "Given the active contributors I allowed in, what does the summary envelope of those contributors look like?"

That distinction is why a neat blend can be useful and why it can also be over-trusted.

Hidden, disabled, and zero-weight are three different states

These settings sound close. They do very different jobs.

That is why a hidden weighted slot can still shape the blend, and why a zero-weight slot can still matter.

What full-stack agreement means and what it does not mean

All DC Slots Above Basis and All DC Slots Below Basis are alignment conditions.

They can be useful because they tell you whether the active basis lines agree about price location. They can also be over-read quickly.

They do not mean:

• the move is confirmed
• the stack is well-designed
• the blend is automatically trustworthy
• the trade is decided

They mean only this: every enabled slot with a valid basis is currently on the same side of its basis line.

The hidden counts and why they exist

The script also maintains hidden counts for active slots above basis and below basis.

Those hidden values are not there to impress you with extra logic. They are there to support alert workflows without adding more visible clutter to the chart. That is useful to know because the alert surface can stay broader than the visible surface.

A good reading sequence under live pressure

If the chart is busy, use this order:

1. Which slots are active?
2. Which of those slots are contributing to the blend?
3. Is price above or below each basis?
4. Is the blend confirming your read or hiding disagreement?
5. Is any contributor using a live-forming higher-timeframe value or an alternate ticker?

If you cannot answer step 2 cleanly, do not let step 4 carry the decision-making weight.

That order is slower than staring at the fill and guessing. It is also more honest.

Three quick verification drills

Drill 1: prove the blend is a summary, not a native channel

1. Keep two slots active with non-zero weights.
2. Set one active slot's Blended Weight: to 0.
3. Watch the blended channel change while that slot can still remain visible.

If the slot is still on the chart but the blend stopped listening to it, you are seeing the summary layer behave correctly.

Drill 2: prove that hide and disable are not the same thing

1. Hide one weighted slot.
2. Watch the drawing disappear.
3. Change that slot's Blended Weight:.

If the blend still responds, the slot is hidden, not gone.

Drill 3: prove that alignment is narrower than conviction

1. Wait for All DC Slots Above Basis or All DC Slots Below Basis.
2. Check whether the active slots still share the same timing posture and symbol context.
3. Decide whether that alignment actually deserves weight in your workflow.

That final step is the point. Agreement on the chart is not the same thing as a finished decision.

Visual placeholder: Annotated chart labeling one slot's upper, basis, and lower lines beside the blended channel, with callouts showing hide-versus-disable and zero-weight-versus-contributing behavior.