Workflows

Five setups are consistent with how Axiom DC CTX is designed to be used. Four traps are consistent with how readers have actually hurt themselves with it. This page walks both. Each workflow is written end-to-end so you can follow it, verify the setup, and know which misuse sits right next to it.

The general rule for every workflow here: the tool does not replace your judgment; it removes the friction of holding several timeframes' worth of range in your head. Whenever a workflow feels like it is asking the tool to make a call on your behalf, you are probably about to walk into an anti-pattern instead.

Workflow 1 — The three-slot default read

This is what ships, used as shipped, with one small habit added.

Why use it: you want to see how the 5-minute, 15-minute, and 60-minute ranges relate to each other on a low-timeframe chart, without assembling the stack yourself and without introducing repaint exposure on the HTF overlays.

Setup:

1. On a 1-minute chart of a liquid symbol, add Axiom DC CTX.

2. Leave every input at its default. Slots 01, 02, 03 enabled; Slots 04–10 off. Weights 40, 35, 25. On Bar Close? ON on every slot.

3. Watch one full 5-minute, 15-minute, and 60-minute cycle so you have seen each slot step forward once.

Verify:

• Teal stack steps at 5-minute close. Blue stack steps at 15-minute close. Purple stack steps at 60-minute close.

• Red blended channel with a lime basis sits inside the envelope of the three stacks most of the time.

• No runtime error banner.

The habit to add: whenever the blended channel looks unusually narrow or unusually wide, open your eyes to the slot lines underneath before you conclude anything from the blend. A weighted average can be narrow because the inputs are narrow or because the inputs disagree; those are different situations.

Misuse to avoid: treating the three-slot default as "the recommended configuration." It is a working baseline. It is not the right layering for every instrument, every session, or every trading horizon. Once you know what you are asking the tool, adjust the timeframes and the weights deliberately.

Workflow 2 — A custom HTF ladder on your own cadence

When the shipped 5/15/60 cadence does not match the rhythm you actually trade on.

Why use it: you trade on, say, 15-minute closes, and the shipped 5-minute slot is noise for you; you want the stack to cover 15m / 60m / 240m instead.

Setup:

1. In the inputs dialog, disable Slot 01.

2. On Slot 02, change TimeFrame: to "15" (if not already), confirm On Bar Close? = ON, set Blended Weight: to whatever fraction of the blend you want 15-minute to carry.

3. On Slot 03, change TimeFrame: to "60", keep ON, set its weight.

4. Enable Slot 04, set TimeFrame: to "240", confirm ON, set its weight.

5. Adjust Slot 02 and 03 weights so the total across Slots 02, 03, 04 reflects how much you trust each timeframe for this question. The shipped 40 / 35 / 25 posture biases toward speed; your ladder may want the opposite.

Verify:

• The three enabled slots step on their own cadences and the slowest timeframe's basis holds steady for long stretches — that is the point.

• Set two of the three slots to equal weight and one to zero briefly, compute the expected blended basis by hand, and confirm the chart matches. This sanity-checks your weights and reassures you the tool is doing what you think.

Misuse to avoid: setting the 240-minute slot to On Bar Close? = OFF to "see the live value" without being explicit that historical/reloaded bars of that slot are not proof of what you would have seen at the time. If you want intrabar responsiveness on the 240, own that it is a live read, not a confirmed one.

Workflow 3 — A cross-ticker context slot, weight zero

When you want a related market's range visible on the chart symbol's price space without letting it steer your blend.

Why use it: you trade SPY, but your 15-minute read is informed by where QQQ's range currently sits; you want that visible on the SPY chart without building a second chart.

Setup:

1. Enable Slot 04.

2. Set TimeFrame: to the chart timeframe or to a higher timeframe — whichever you want the cross-ticker read at.

3. Set Optional Ticker: to QQQ.

4. Confirm On Bar Close? = ON (this is especially important for cross-ticker slots; see MTF & Repainting for why).

5. Set Blended Weight: to 0. This keeps the QQQ-scaled channel visible on the chart without contributing to the blended channel.

Verify:

• The orange (Slot 04's default color) channel lands in SPY's price space — somewhere plausible near the SPY range, not at raw QQQ prices.

• Toggle Optional Ticker: between empty and QQQ and watch the slot's channel move between the native position (a Donchian on SPY at the slot's timeframe) and the scaled position. Both should be visible; the scaled version should not look dramatically distorted.

• The blended red channel should change when you raise Slot 04's weight from 0 to, say, 30 if the scaled slot differs from the existing blend. That proves the slot would steer the composite if weighted. Set it back to 0 when you are done and confirm the blend returns.

Name the role out loud: this is a context slot, not a causal read. Read it as "here is QQQ's range, fit onto the SPY axis." Do not read it as "QQQ is leading SPY." The scaling is arithmetic, not predictive.

Misuse to avoid: giving the cross-ticker slot a large weight and then reading the blended channel as if it were a clean composite. A cross-ticker slot with weight can pull your blend toward a symbol you do not trade — which may be what you want, deliberately, but should not be an accident.

Workflow 4 — A visibility-only hidden slot

When a slot is useful in the blend but is cluttering the chart.

Why use it: your chart shows three slot stacks plus the blended channel. A fourth slot's contribution matters to your blend but its three lines are too much visual noise on a small screen.

Setup:

1. Enable Slot 04.

2. Configure its TimeFrame:, Length:, and other primary inputs.

3. Set Hide DC 04 Plot to true. The slot's lines disappear.

4. Set Blended Weight: to whatever fraction of the blend you want Slot 04 to carry. This is a non-zero weight — that is the point of this pattern.

Verify:

• Slot 04's three lines are not drawn.

• The blended channel is different from a configuration without Slot 04 enabled. Briefly disable Slot 04 entirely and watch the blended channel shift; then re-enable and hide. The hidden-but-contributing version matches the fully-enabled version, numerically.

When to use this carefully: this is a power-user pattern. A reader new to the tool should usually not hide slots that contribute to the blend, because the connection between what you see and what the blend is doing is easier to keep intact when every contributing slot draws.

Misuse to avoid: the hidden-plot trap. Three weeks later, you open the chart, notice the blend is moving in ways your three visible slots do not explain, and conclude the tool is broken. It is not broken — Slot 04 is hidden and contributing. Leave yourself a note in the slot's label or a self-chat somewhere about which hidden slots you have running, so future-you does not spend an hour debugging past-you's setup.

Workflow 5 — An alerts-only silent slot

When you want alignment alerts to cover a timeframe you do not want visible on the chart.

Why use it: you want All DC Slot Bases Uptrend to include the 240-minute slot in the alignment check, but you do not want the 240-minute lines on your 1-minute chart.

Setup:

1. Enable Slot 04 (or any unused slot).

2. Set TimeFrame: to "240", confirm On Bar Close? = ON.

3. Set Hide DC 04 Plot to true.

4. Set Blended Weight: to 0.

The slot is now invisible, does not contribute to the blended channel, and does participate in alignment alerts. It is also still counted in Active Basis Uptrend Count / Active Basis Downtrend Count / the chart-close Active Above Basis Count / Active Below Basis Count.

Verify: set a All DC Slot Bases Uptrend alert and configure your other visible slots to agree on uptrend. The alert should fire only when Slot 04 also agrees — test by forcing the 240-minute to disagree (switch symbols briefly or look during a window when the 240m basis is falling). The alignment alert will stay silent until Slot 04 agrees with the rest.

Misuse to avoid: using this pattern when you wanted the slot to not participate at all. If you want the slot out of alignment, disable it. Hiding alone does not take it out of the check.

Anti-pattern 1 — Enable everything

Turning on all ten slots "because they are available." The chart becomes a thicket of lines no reader can parse under pressure, the blend averages a dozen mildly-conflicting reads into a muddy line in the middle, and the alignment alerts become silent because ten slots almost never all agree.

Why it fails: more slots do not produce more signal. Each slot you add makes every slot quieter in the composite. The blended basis-trend vote gets fragmented; partial agreement becomes permanent. The cost of a tenth slot is ninth-slot minus the value it adds.

What to do instead: pick three to five slots that answer a specific question. Name, in plain words, what each slot is there for. If you cannot name the role, turn the slot off.

Anti-pattern 2 — OFF across the stack

Flipping On Bar Close? to OFF on every slot because the chart feels snappier, then reading the stack as if it were a confirmed HTF view.

Why it fails: OFF is not speed; it is a different contract. The live slot can redraw while the HTF bar forms, and historical/reloaded OFF bars are not a faithful record of what was available live. Alerts that fired under OFF may have fired on values that later settled elsewhere. Reading such a stack as "what the HTF picture was" is a subtle way of lying to yourself.

What to do instead: default ON on every slot. Flip OFF only on the specific slots where intrabar responsiveness is a real requirement, and only where you are working with the current value rather than with a historical bar of the slot. See MTF & Repainting for the full tradeoff.

Anti-pattern 3 — Large weight on a timeframe you do not trade

Putting a 40-weight on a 240-minute slot when you are trading on 5-minute closes. The blend becomes dominated by a timeframe whose range updates four times a day on a chart where you make decisions every five minutes.

Why it fails: weight in the blend is weight in your attention budget. If 40% of your weighted composite comes from a timeframe you do not act on, 40% of your blended channel is context you are not using. The blend becomes less useful because it is weighted by intent you do not have. Worse: the blended basis-trend vote can fire alerts driven by the 240-minute's slow rhythm, which to a 5-minute trader look like noise at an inconvenient cadence — a notification you cannot act on, about a condition on a timeframe you did not intend to weight.

What to do instead: weight the blend by how much each timeframe should influence the decision you are actually making. A discretionary 5-minute trader reading 5/15/60 with a 240 context slot probably wants most of the blend weight on the fast slots and the 240 as either zero-weight context or very small weight. A swing trader holding positions through sessions wants the opposite. A good test: if an alert from the blended channel fires at a cadence that does not match your trading horizon, your weights are probably pointing at a timeframe you are not working on.

Anti-pattern 4 — Length extremes, chasing

Pushing Length: to 3 to "capture the current swing" or to 300 to "smooth out the noise," then reading the resulting channel as if it were still a Donchian at 20.

Why it fails: the outer bounds are raw. A Length: of 3 makes the upper chase the latest fresh high directly and the lower chase the latest fresh low directly; a three-bar channel is not a range, it is a trailing extreme. A Length: of 300 flattens the channel across an arc where everything but the biggest swings is invisible. Neither is the same instrument you were reading before you changed the knob. And — critically — no amount of Basis MA Length: smoothing will hide a bad Length: setting, because basis smoothing does not reach the outer bounds.

What to do instead: choose Length: deliberately for the range you are trying to read. When the outer bounds look ragged or flat, the first knob to reach for is Length:, not the basis smoothing. If your chart asks for a longer range-read, a longer Length: plus a basis smoothing increase that actually tracks the midpoint is coherent. A short Length: plus a heavy Basis MA is trying to do two conflicting things at once.

A quick orientation table

Use the tool for one named role at a time. When the chart stops being legible, the right move is to remove a slot, not to add another.