Axiom MA Lite

Axiom MA Lite is for traders who want more than one moving average on the chart, but less clutter than a pile of separate overlays usually creates.

That is the real problem this indicator addresses. One higher-timeframe line is often too thin to carry bias. A stack of unrelated overlays can solve that problem and immediately create another one: the chart starts to look organized before the trader is actually clear on what is confirmed, what is weighted, and what still depends on judgment.

This script gives you a smaller workspace for that job, not a shortcut around it.

• three moving-average slots you can configure independently
• one optional blended summary line
• optional cross-ticker context on any slot
• alerts for slot state, blend state, and full-stack alignment

The value is not certainty. The value is that you can keep short, medium, and higher context on one chart in a way that is still teachable, still adjustable, and still worth verifying.

What it helps you do

• keep a three-layer MA stack readable on one chart
• compare whether your active layers agree or disagree
• use a blended line as a quick summary of weighted slot context
• add one outside symbol for context without leaving the chart first
• let alerts call you back to review instead of staring at every candle

What it does not do

• choose the right timeframes, weights, or MA types for you
• turn a blended line into proof
• make another symbol's rescaled MA equal to raw-price comparison
• decide whether live-forming higher-timeframe movement deserves trust yet

If that boundary stays visible, the tool becomes useful. If it disappears, the chart can still look neat while your read gets weaker.

Good fit

• You already think of moving averages as context, not commands.
• You want a compact stack that stays readable under pressure.
• You care about the difference between confirmed higher-timeframe behavior and still-forming higher-timeframe behavior.
• You want customization because it helps you shape a workflow, not because you are hunting for one magic preset.

Not a fit

• You want one best recipe that should work everywhere.
• You want the blend to behave like a trade engine.
• You do not want to think about timeframe compatibility, weighting decisions, or trust boundaries.
• You are really looking for a backtest or automation system rather than an interpretation tool.

Before you trust the first chart

Most misuse starts here, before alerts, presets, or deeper customization. These checks matter because the stack can look clean before it is being read correctly.

1. Every enabled slot has to respect the chart timeframe

The default stack starts at 5 / 15 / 60. That works well on a 1m or 5m chart, but it is not chart-timeframe-neutral. If any enabled slot is below your chart timeframe, the script throws a runtime error until you raise or disable that slot.

2. On Bar Close? is global in this build

This version uses one timing switch for the whole stack. When you change On Bar Close?, you are changing how all three slots handle higher-timeframe timing. That matters enough to treat as a workflow decision, not a cosmetic preference.

3. The blend is a summary, not a verdict

The blended line only reflects active slots with non-zero weight. It is there to compress the stack into something you can read faster, not to overrule the rest of the chart.

4. Optional ticker is context mapping, not confirmation

If you load another symbol into one slot, the script rescales that MA into the current chart's price region so it stays readable. That can be useful. It is still not the same thing as proving direct comparability or market leadership.

Why traders keep this on the chart

This indicator tends to earn its place when the trader wants structure without the overhead of a much larger surface. It is often most useful for the trader who keeps reaching for one more overlay, then realizes the chart is getting harder to trust instead of easier to read.

Common uses:

• building a same-symbol 5 / 15 / 60 bias ladder
• keeping one slot visible for diagnostics while the blend listens to the others
• adding one related symbol for context without turning the screen into a second dashboard
• using alerts as review prompts once the stack logic makes sense

What usually goes wrong is not the feature list. It is over-trust. A clean stack can feel more certain than it is, especially when weights, timeframes, and live-forming higher-timeframe data are all in play.

Start here

If you want the shortest honest path, read these pages in order:

1. Quick Start
2. MTF and Repainting
3. Settings
4. Visuals and Logic
5. Limitations and Trust Boundaries

Then use the supporting pages when the next question actually appears:

• Alerts
• Workflows
• Cross-Ticker Scaling
• For the Geeks
• Troubleshooting
• FAQ

Visual placeholder: Annotated chart showing the default 5 / 15 / 60 stack, the blended line, and a short label for the chart-timeframe rule plus the global timing switch.