Workflows

This page is about using the indicator in ways that stay explainable.

Axiom DC Pro can do more than most traders need on day one. That is why the healthiest workflows here start small, add one purpose at a time, and keep the trust burden visible.

If you are still learning the indicator, build one workflow that you can describe in one sentence before you build two that you can only half explain.

Workflow 1: the shipped same-symbol baseline

Use this when you want a clean short, medium, and higher-timeframe Donchian ladder on one chart.

Recommended setup:

• DC 01 = 5
• DC 02 = 15
• DC 03 = 60
• keep all three on the chart symbol
• keep all three confirmed with On Bar Close?
• keep the default weights 40 / 35 / 25 until you have a reason to change them

Why it works:

• it gives you three familiar context layers without forcing the dormant slots into view
• it makes the blended channel easier to interpret because the contributors are obvious
• it gives you a stable first stack to compare against future experiments

What to watch:

• do the active timeframes fit the current chart
• is price above or below each basis
• is the blend clarifying the stack or hiding disagreement

Avoid this drift:

• adding extra slots because the baseline feels inconclusive
• changing basis families before the default read is understandable

Workflow 2: the diagnostic slot

Use this when you want one extra layer on the chart without giving it summary authority yet.

Recommended setup:

• keep your core same-symbol stack intact
• enable one extra slot such as DC 04
• set that slot's Blended Weight: to 0
• leave the slot visible if you want to inspect it, or hide it if the chart gets too crowded

Why it works:

• you can test a new timeframe, basis family, or symbol without quietly rewriting the blend
• it teaches the difference between "active on the chart" and "active in the summary"

Good uses:

• testing one slower timeframe above the base ladder
• comparing one different basis family against an unchanged core slot
• holding one outside market on the chart while the blend stays same-symbol

Avoid this drift:

• forgetting that a zero-weight slot can still affect its own alerts and stack alignment
• treating the diagnostic slot like evidence just because it stayed on-screen

Workflow 3: the alternate-ticker context slot

Use this when another market genuinely changes how you frame the chart you are trading.

Recommended setup:

• keep your core slots on the chart symbol
• use Optional Ticker: on one non-core slot only
• keep that slot confirmed at first
• keep that slot at Blended Weight: 0 until you verify it

Why it works:

• it adds outside context without letting the outside market quietly dominate the blend
• it keeps the main workflow readable while you test whether the remapped slot is truly helpful

What to verify:

• the outside slot still makes sense when compared against that market on its own chart
• you can explain what the outside market is adding besides emotional comfort
• disabling the outside slot does not collapse your entire read

Avoid this drift:

• letting the remapped slot carry heavy blend weight before you trust it
• talking about the outside slot as though it proves correlation or direct confirmation

Workflow 4: the mixed-timing audit

Use this when you want to test whether earlier higher-timeframe movement adds real value or only more noise.

Recommended setup:

• keep most active slots confirmed
• turn On Bar Close? off on one non-core slot only
• keep that slot lightly weighted or at 0
• observe it during live conditions or replay before you widen the idea

Why it works:

• it teaches what a live-forming slot actually costs
• it keeps the exploratory timing posture from quietly taking over the whole stack

What to watch:

• does the earlier movement help, or does it only create more second-guessing
• can you still explain which slot is exploratory
• is the blend becoming harder to trust because the contributors no longer share one timing posture

Avoid this drift:

• turning several slots live-forming at once
• continuing to read the blend like a fully confirmed object after timing assumptions have diverged

Workflow 5: the basis-family comparison

Use this when you want to learn what a different midpoint behavior changes without rebuilding the whole stack.

Recommended setup:

• keep timeframe, symbol, and Length: constant
• use one zero-weight diagnostic slot
• change Type: on that diagnostic slot only
• compare its basis line against an unchanged core slot

Why it works:

• it isolates one change at a time
• it helps you decide whether a different basis family improves clarity or only adds novelty

What to verify:

• the basis changed the way you expected
• the raw outer channel bounds still behave like Donchian bounds
• the new basis family actually earns a role in the workflow

Avoid this drift:

• treating unusual basis families like status upgrades
• changing the whole stack before you know what one family change really did

Anti-patterns worth catching early

These are the workflow shapes that usually create more confusion than value:

• ten active slots on day one
• several contributing slots with mixed timing and no clear reason
• alternate-ticker slots carrying major blend weight before validation
• alerts layered on top of a stack you cannot describe from memory
• using the blend to hide weak slot design instead of fixing the slot design

A healthy expansion rule

When you widen the workflow, add only one of these at a time:

• one new slot
• one new basis family
• one alternate ticker
• one live-forming slot
• one new alert family

Then verify the effect before you add the next one.

That rule is not about being cautious for its own sake. It is about keeping ownership of the stack as it grows.

If the workflow starts feeling muddy

Shrink it back to:

• three active same-symbol slots
• one basis family
• confirmed timing
• clear non-zero blend contributors

That reset is not failure. It is how you get back to a stack you can trust because you can still explain it.