Workflows
This page is about using the indicator in ways that stay explainable under pressure.
Written By AxiomCharts
Last updated About 2 hours ago
Workflows
This page is about using the indicator in ways that stay explainable under pressure.
The script is flexible enough to support many layouts. That does not mean every layout is equally useful. Good workflows give each slot a job, keep the blend honest, and make verification easier instead of harder.
If a workflow needs more complexity than you can explain in plain language, it probably needs less complexity.
How to choose a workflow
Workflow 1: the same-symbol baseline ladder
Use this when you are learning the tool or when you want a clean momentum stack without outside-market context.
Setup
- Keep
MACD 01,MACD 02, andMACD 03enabled. - Keep their
TimeFrame:values at5,15, and60, or adapt them upward if the chart timeframe requires it. - Leave
Optional Ticker:blank on all active slots. - Keep
On Bar Close?on for all active slots. - Keep the active slot weights equal.
- Leave master smoothing off.
What this workflow is good at
- giving you a compact short, medium, and slower context ladder
- teaching the slot-versus-blend relationship without cross-symbol noise
- making alerts easier to interpret because the active slots share one timing posture
What to verify
- each active slot is legal on the chart timeframe
- each slot color change still makes sense when you inspect the chart
- the blend changes when one slot weight changes, then returns when the weight is restored
What to avoid
- enabling extra slots before the first three are understandable
- mixing MA families before the baseline ladder has a stable role
Workflow 2: staged slot expansion
Use this when the three-slot ladder already makes sense and you need one more context layer.
Setup
- Start from the baseline ladder.
- Enable one expansion slot only.
- Give that slot a specific job before you touch the settings.
- Choose the timeframe, symbol, and timing posture for that job.
- Start with a conservative weight.
- Watch how the new slot affects the blend before you add another.
Examples of reasonable slot jobs:
- an extra higher-timeframe context layer
- a faster diagnostic layer for a specific market condition
- an alternate-symbol context slot kept outside the blend at first
What this workflow is good at
- adding capability without losing the thread
- making each new slot earn its role
- keeping the blend readable while the stack grows
What to verify
- you can explain the new slot's job in one sentence
- the slot's timing posture matches that job
- the slot improves the read for a reason you can point to, not just because the pane looks fuller
What to avoid
- turning on several expansion slots at once
- adding slots because uncertainty feels uncomfortable
Workflow 3: the zero-weight diagnostic slot
Use this when you want a slot to be visible and useful without letting it steer the blend yet.
Setup
- Enable the new slot.
- Set its
Blended Weight:to0. - Keep the slot visible at first.
- Compare its behavior to the existing blend and alignment states.
- Add blend influence only after the slot proves it deserves a role in the summary.
What this workflow is good at
- testing a new timeframe or symbol without quietly changing the blend
- comparing local slot behavior to the current summary
- separating curiosity from commitment
What to verify
- the slot still alerts as expected
- the slot still affects alignment while it remains enabled
- the blend ignores the slot until the weight is raised
What to avoid
- forgetting that
weight = 0is not the same as turning the slot off - leaving diagnostic slots active forever without remembering why they are there
Workflow 4: the confirmed-versus-live comparison
Use this when you want to understand what On Bar Close? is really buying or costing.
Setup
- Duplicate one active slot's symbol, timeframe, and MACD settings onto another slot.
- Keep both slots on the same symbol and timeframe.
- Leave one slot with
On Bar Close?on. - Turn
On Bar Close?off on the duplicate slot. - Watch them during a building higher-timeframe bar.
What this workflow is good at
- making the timing tradeoff visible instead of theoretical
- showing how mixed confirmation can affect the blend
- helping you choose earlier feedback versus steadier behavior on purpose
What to verify
- the live-forming slot can move while the confirmed slot stays steadier
- the difference matters most while the requested higher-timeframe bar is still open
- chart-bar-close alerts do not erase that timing difference
What to avoid
- calling the live-forming slot "better" because it moved earlier
- mixing timing postures across important slots before you understand the cost
Workflow 5: the multi-ticker context check
Use this when another symbol might add useful context, not when you want it to settle the trade for you.
Setup
- Start from a same-symbol baseline you already trust.
- Add one alternate-symbol slot only.
- Keep that slot's
Blended Weight:at0first. - Match the slot timeframe to the question you are asking.
- Compare the outside symbol on a separate chart before you decide the slot is useful.
What this workflow is good at
- checking whether another market is broadly supportive or diverging
- seeing timing and structural agreement without constantly switching charts
- bringing outside context into the stack without overcommitting to it
What to verify
- you can explain why that symbol belongs in the stack
- the alternate slot adds context, not only persuasion
- the workflow still works if you temporarily remove the alternate slot
What to avoid
- treating outside agreement as automatic confirmation
- letting the outside slot dominate the blend before it has proved it belongs there
Workflow 6: blend-first review after slot literacy
Use this when the stack is already familiar and you want a faster review pass.
Setup
- Build the slot ladder first.
- Confirm which slots truly belong in the blend.
- Confirm their weights make sense.
- Use the blended pair and histogram as the fast scan layer.
- Drop back to the slots whenever the summary looks persuasive but unclear.
What this workflow is good at
- reducing review load once the stack is mature
- giving you one quick summary without losing the slots underneath
- pairing blended events with local slot inspection
What to verify
- the blend still reflects the slot roles you think it reflects
- alignment and blend state still part ways when you would expect them to
- master smoothing, if enabled, is calming the summary rather than hiding confusion
What to avoid
- using the blend as a shortcut around slot inspection
- assuming a clean summary means the stack is internally clean
A short anti-pattern list
- enabling all ten slots because the script offers them
- mixing confirmed and live-forming slots without naming the reason
- pushing weights around until the blend tells the preferred story
- adding alternate symbols before the same-symbol ladder makes sense
- using master smoothing to quiet uncertainty instead of to refine a stable design
A good closing check
Before you call a workflow stable, ask:
- What job does each active slot serve?
- Which active slots are shaping the blend?
- Which active slots are confirmed, and which are live-forming?
- If I removed one slot, would I know what capability I lost?
If those answers are clean, the workflow is probably carrying its own weight. If they are not, reduce the stack until they are.
Visual placeholder: Workflow comparison sheet showing the baseline same-symbol ladder, one zero-weight diagnostic slot, one confirmed-versus-live comparison pair, and one alternate-symbol context slot with its job labeled.