Quick Start

This page is about the shortest correct first run, not the smartest custom stack you might build later.

The goal is to get one clean chart state running, understand why it is valid, and leave with a baseline you can actually verify. If you do that first, the later settings pages become much easier to use without drifting into random tweaking.

Pick one path before you start

- If your chart timeframe is 5m or lower, use Option A. - If your chart timeframe is above 5m, use Option B.

Do not mix both paths on the first pass. Choose the one that fits your chart, get one stable result, then stop.

Check this before you add the indicator

Look at your chart timeframe first.

The shipped defaults enable:

• MA 01 on 5
• MA 02 on 15
• MA 03 on 60

Every enabled slot must stay at or above the chart timeframe. If your chart is above one of those values, fix that conflict before you expect the script to run normally.

If you skip this check, the rest of the page turns into cleanup work.

Option A: use the default stack as intended

Use this path when your chart timeframe is 5m or lower.

1. Add Axiom MA Lite to the chart.
2. Confirm that three slot lines and one blended line appear.
3. Open settings and confirm On Bar Close? is enabled.
4. Confirm the active slot timeframes are still 5, 15, and 60.
5. Change one slot's Blended Weight: for a moment and watch the blended line react.
6. Change the weight back after the check.

What you should understand before moving on:

• the default layout is a same-symbol three-layer stack
• the blend responds to slot weights, not to a separate hidden signal
• confirmed higher-timeframe mode is still on across the whole stack
• you do not need alerts or Optional Ticker: yet to learn the baseline

Option B: adapt the stack to your chart first

Use this path when your chart timeframe is above 5m, or when you already know the default ladder is not the right fit.

1. Add the indicator.
2. Open settings immediately.
3. Compare each enabled slot's TimeFrame: to the chart timeframe.
4. Raise any conflicting slot timeframe, or disable that slot.
5. Confirm the runtime error is gone.
6. Leave On Bar Close? enabled while you learn the stack.
7. Stop there and read the chart once before you start adding complexity.

That slower path is usually better than forcing the defaults onto a chart they do not fit. The point is not to preserve the shipped ladder. The point is to reach one legal stack you can explain.

First sanity checks

Run these quick checks before you build alerts or workflows around the indicator.

If one of those checks surprises you, pause there. That is useful information, not a failure.

A sensible first configuration

Keep the first session narrow:

• use no more than the default three active slots
• keep all slots on the same symbol first
• leave On Bar Close? on
• start with one MA type across the stack before mixing styles
• add alerts only after you can explain what each slot is doing
• leave Optional Ticker: blank until the same-symbol stack feels boring in a good way

Before you move on

You are ready for the next page when you can answer these without guessing:

• Which enabled slot has the lowest timeframe on your chart?
• Is the whole stack confirmed or live-forming right now?
• Which active slots are shaping the blend?

If you cannot answer those yet, do not optimize the stack. Go read the timing page first, then come back.

From here, go to MTF and Repainting, then Settings, then Visuals and Logic.

Visual placeholder: Settings capture showing one slot group, the default 5 / 15 / 60 ladder, and the single global On Bar Close? control highlighted.