Workflows

Ten available slots can make experimentation feel productive long before it becomes coherent. These patterns are here to keep the stack grounded in jobs instead of curiosity alone. A good workflow gives each slot a role. A bad workflow turns the pane into a crowded argument between settings. Use these patterns as starting structures, not as universal presets. If you are still in your first few sessions with the indicator, use Workflow 1 and stop there until you can explain the baseline without opening settings.

Workflow 1: the same-symbol baseline ladder

This is the best first workflow for most readers.

What it is for

• comparing short, medium, and slower participation context in one pane
• learning how the slot layer and the blend relate before you add more complexity

How to build it

1. Keep the shipped enabled baseline: 5 / 15 / 60.
2. Keep all three active slots on the chart symbol.
3. Keep all three on On Bar Close? = true.
4. Leave Session windows alone until you have seen at least one reset.
5. Keep the equal starting weights while you learn the read.

What to verify

• each enabled slot is legal on the current chart
• the active lines stay bounded inside -100 to +100
• you can explain what each timeframe adds before you read the blend
• the blend still makes sense if you momentarily remove one slot with Blended Weight: 0

What to avoid

• adding a fourth slot before the first three have clean roles
• using the blend as your first and only read

Workflow 2: staged expansion

This is how you grow beyond the baseline without losing the plot.

What it is for

• adding one extra context layer at a time
• keeping the tool adaptable without making it chaotic

How to build it

1. Start from a baseline you already trust.
2. Enable one extra slot only.
3. Give that slot one explicit job before you change anything else.
4. Keep the new slot visible at first.
5. Re-check the blend before you enable another slot.

Useful first jobs:

• slower confirmation layer
• rolling-window contrast
• alternate-ticker context
• zero-weight diagnostic view

What to verify

• you can explain what changed in the stack after the new slot was added
• you still know which slots are blended and which are only diagnostic
• the stack did not quietly become a mix of timing assumptions you did not mean to create

What to avoid

• waking up several dormant slots in one session
• giving multiple new slots the same vague job

Workflow 3: confirmed versus live-forming comparison

This is the cleanest way to understand what earlier movement costs.

What it is for

• learning the trust tradeoff between settled and still-forming higher-timeframe reads
• deciding whether one exploratory live-forming slot is worth it in your process

How to build it

1. Duplicate one slot idea on two slots.
2. Keep the same symbol, timeframe, window, and smoothing on both.
3. Leave one slot confirmed.
4. Turn On Bar Close? off on the other slot.
5. Keep the live-forming version at modest or zero blend weight until you trust what it is adding.

What to verify

• how the live-forming slot behaves during an unfinished higher-timeframe candle
• whether the earlier motion actually helps your workflow or only feels exciting
• whether the blend still tells an honest story when one slot is exploratory

What to avoid

• treating the earlier slot like free signal improvement
• forgetting that an all-slot alignment alert can now include mixed timing postures

Workflow 4: Session versus Rolling contrast

This workflow helps when you want to compare anchored context against recent-window context.

What it is for

• seeing the difference between "since this reset" and "inside this recent stretch"
• testing whether one market condition responds better to an anchored or sliding view

How to build it

1. Keep two otherwise similar slots.
2. Leave one in Session.
3. Switch the other to Rolling.
4. Keep the same symbol and similar timing so the window behavior is the real comparison.

What to verify

• the session slot prints reset markers while the rolling slot does not
• the two slots react differently around the same price swings
• you can explain which question each slot is answering

What to avoid

• turning the session-versus-rolling choice into a "better" contest
• changing timeframes and windows at the same time, then blaming the wrong setting for the difference

Workflow 5: zero-weight diagnostic slot

This is one of the most useful Pro-only habits.

What it is for

• keeping a slot visible and alertable without letting it steer the blend
• testing a new role before it earns summary weight

How to build it

1. Enable a slot for a specific diagnostic job.
2. Keep it visible.
3. Set Blended Weight: to 0.
4. Watch the slot on its own before you decide whether it belongs in the blend later.

What to verify

• the slot still plots
• the slot can still be used for its own alert logic
• all-slot alignment can still care about it if it remains enabled

What to avoid

• assuming zero weight removed the slot from every part of the script
• forgetting to revisit whether that slot should stay enabled at all

Workflow 6: alternate-ticker context slot

Use this only after the same-symbol stack is already understandable.

What it is for

• bringing one outside market into the same participation workspace
• checking whether outside context adds something useful without leaving the pane

How to build it

1. Keep most active slots on the chart symbol.
2. Assign Optional Ticker: on one slot only.
3. Start that slot in confirmed mode.
4. Keep the slot visible.
5. Start with modest or zero blend weight.

What to verify

• the outside slot still makes sense when checked against the outside market directly
• you can explain what job the outside symbol is doing in the stack
• the workflow still makes sense if you remove that slot entirely

What to avoid

• treating outside agreement as automatic confirmation
• adding several alternate tickers before one mixed-symbol slot has earned trust

Workflow 7: blended threshold monitoring

This workflow belongs later, not first.

What it is for

• monitoring the weighted summary after the slot design already makes sense
• reducing chart checks when you care about summary transitions or threshold events

How to build it

1. Start from a stack you already trust.
2. Make sure you can name the weighted contributors.
3. Choose the blended alert family that matches the question you are actually asking.
4. Add threshold lines only if they already mean something in your process.

What to verify

• whether you wanted a state alert or a change alert
• whether the blend still deserves your trust when one contributor is removed
• whether the thresholds are helping or just decorating the panel

What to avoid

• using thresholds to replace slot understanding
• using all-slot agreement or overbought events like permission slips

A simple rule for all workflows

If a new slot or a new control makes the stack harder to explain, pause there before you keep optimizing. This tool is strongest when the stack gets more useful without becoming more mysterious.

Visual placeholder: Workflow diagram showing the default three-slot ladder, one zero-weight diagnostic slot, one alternate-ticker context slot, and arrows marking which slots do and do not feed the blend.