Workflows

This page is here to keep you from wandering through settings without a question in mind.

Written By AxiomCharts

Last updated About 2 hours ago

Workflows

This page is here to keep you from wandering through settings without a question in mind.

Axiom CVD Osc Lite is flexible enough to support several useful workflows. That flexibility becomes a liability when the stack grows faster than your reason for building it. The goal of this page is to give you a few workflows the source actually supports, plus the misuse patterns that usually make the pane look smarter than the trader using it.

Before any workflow, lock down three things first:

  • every enabled slot is legal on the chart
  • you know whether the stack is confirmed or live-forming
  • you can say why each enabled slot belongs in the setup

That preflight keeps workflow design from turning into feature collecting.

Workflow 1: the default same-symbol ladder

Use this when you want short, medium, and slower participation context on one symbol without opening several indicators.

Setup

  • keep the chart at 5 minutes or lower
  • leave the default 5 / 15 / 60 slot timeframes in place
  • keep all three slots on the chart symbol
  • leave On Bar Close? enabled
  • keep the default Session windows while you learn the rhythm

What this workflow is good for

  • seeing whether short and medium participation are leaning in the same direction
  • noticing when the faster slot shifts ahead of the slower slots
  • using the blend as a summary only after you can explain what each slot is contributing

What to verify

  • all three slots are legal on the chart
  • the blend actually reflects the slots you think it reflects
  • a daily Session reset marker appears when expected

What usually goes wrong

  • the reader treats full-slot agreement like proof
  • the blend becomes the only thing they watch
  • the default ladder is used on a higher chart timeframe and the runtime error gets blamed on the tool instead of the setup

Workflow 2: anchored versus rolling comparison

Use this when you want to compare two different kinds of pressure question:

  • "What has participation looked like since this anchor reset?"
  • "What has participation looked like inside a sliding recent window?"

Setup

  • keep one slot in Session mode
  • switch a comparable slot to Rolling
  • keep the timeframe relationship between the two slots straightforward to compare
  • hold the rest of the stack steady while you compare the window behavior

What this workflow is good for

  • learning the difference between anchored accumulation and sliding pressure
  • deciding which window model fits the decision horizon better
  • preventing the mistake of treating Session and Rolling like interchangeable flavors

What to verify

  • the Session slot shows reset markers
  • the Rolling slot does not
  • the two slots can diverge even when they share the same symbol and similar smoothing

What usually goes wrong

  • the reader changes window mode and timeframe at the same time, then cannot tell which change mattered
  • a rolling slot is judged by the same expectations as an anchored slot

Workflow 3: alternate-ticker context slot

Use this when one outside market helps you interpret the main chart, but you do not want to leave the chart every few seconds.

Setup

  • keep the main stack restrained first
  • assign one slot an Optional Ticker:
  • start with that slot at Blended Weight: 0
  • compare that slot against the source market on a separate chart before you let it influence the blend

What this workflow is good for

  • checking whether outside-market participation context lines up with the main chart
  • keeping a context slot visible without pretending it is the same thing as your main symbol
  • testing whether that outside context adds signal or just narrative comfort

What to verify

  • the alternate-ticker slot behaves differently enough to justify its place
  • the remapped context helps you think more clearly rather than just adding complexity
  • you can explain why it belongs in the stack before you give it non-zero weight

What usually goes wrong

  • the alternate-ticker slot is added because the trader feels uncertain, not because the process calls for it
  • the slot is blended in before it is verified
  • the remapped output is treated like direct price equality

Workflow 4: zero-weight diagnostic slot

Use this when you want one extra slot for learning, comparison, or alerts, but you do not want it quietly steering the summary.

Setup

  • keep the slot enabled
  • set Blended Weight: to 0
  • decide whether you want the line visible or hidden
  • leave the rest of the blend unchanged

What this workflow is good for

  • testing a new timeframe without polluting the current summary
  • keeping one slot available for slot-specific alerts
  • comparing a candidate slot to the blended view before deciding it belongs in the blend

What to verify

  • the slot still exists logically
  • the blend changed only because the slot stopped contributing to it
  • alignment alerts still count the slot if it remains enabled

What usually goes wrong

  • the trader assumes zero weight removed the slot from everything
  • the slot is hidden and then forgotten even though it is still active

Workflow 5: blended threshold monitoring after the stack already makes sense

Use this when you already trust the stack and want fewer screen checks around the blended summary.

Setup

  • keep the stack in a configuration you can already explain
  • choose threshold levels that belong to your workflow
  • add blended zero-line or threshold alerts only after the slot stack is understood

What this workflow is good for

  • reducing chart-check frequency
  • noticing when the blended summary moves into a different normalized region
  • keeping attention on a defined state change instead of constant visual monitoring

What to verify

  • the thresholds are chosen on purpose, not inherited by habit
  • the alert is answering the question you actually care about
  • the blend still reflects the slots you intend it to reflect

What usually goes wrong

  • the threshold line starts acting like a trade order
  • the trader forgets whether they wanted a state alert or an event alert

Anti-patterns to avoid

  • building a stack with no clear reason for each slot
  • mixing chart symbol and alternate-ticker slots before the same-symbol stack makes sense
  • turning On Bar Close? off because earlier feels better, then reading the pane like nothing about trust changed
  • weighting slots by intuition alone and then treating the blend like objective truth
  • hiding slots and forgetting they can still matter
  • adding more smoothing because the line feels messy instead of asking whether the workflow itself is weak

A good workflow test

  1. Can I explain why each enabled slot is here?
  2. Can I name which slots are shaping the blend?
  3. Do I know whether this stack is confirmed or live-forming?
  4. Could I tell another trader what would make this setup invalid?

If those answers are foggy, the next move is usually verification, not more tuning.

Visual placeholder: Workflow comparison board showing the default same-symbol ladder, a Session-versus-Rolling pair, and one zero-weight alternate-ticker diagnostic slot.