Workflows

Three named scenarios for using the Base trim well, each with a setup, a reading, a failure mode, and an anti-pattern contrast. These are scaffolds, not prescriptions. The instruments, timeframes, and thresholds in each are examples of shape; you adapt them to whatever you actually trade. The structure is consistent across all three so you can skim diagonally: setup, read, failure, anti-pattern, mitigation.

Each workflow assumes you have already done the verification in Quick Start and have read MTF & Repainting. If you have not, the failure modes below will be harder to recognize when they happen.

A reading posture that applies across all three: you are the scientist; the pane is the instrument. Workflows are hypotheses about what the instrument will tell you under a specific setup. When the instrument tells you something that does not fit the hypothesis, the question is whether the hypothesis was wrong, the setup was wrong, or the instrument is currently outside the range where it resolves useful information. All three are real possibilities. None of them is "the tool is broken."

Workflow 1: Differentiated three-slot stack

Purpose. Use the three slots as three legitimately different observations about the same instrument, so that when the blend and the slot colors cooperate, you have more than one measurement repeated.

Setup.

• Slot 01: Source = close, TimeFrame = 5, Type = EMA, Length = 20, Slow = EMA(3), Weight = 33.3.

• Slot 02: Source = hl2, TimeFrame = 15, Type = SMA, Length = 50, Slow = EMA(5), Weight = 33.3.

• Slot 03: Source = close, TimeFrame = 60, Type = EMA, Length = 20, Slow = EMA(3), Weight = 33.3.

• Global: On Bar Close? = true, ATR Length = 14, ATR Sensitivity = 1.0, master smoothing off.

The difference between this and the shipped defaults is slot 02. You have changed slot 02's source, baseline family, baseline length, and slow length — enough that slot 02 is doing work the other two slots are not. Slot 01 is a fast read on the execution timeframe. Slot 03 is a context read on the hour. Slot 02 now sits between them with a different personality than either.

How to read.

• The blend is the headline. When it is lime and the fast line is opening away from the slow line, stretch is accelerating against its own memory. When it is lime and the two blended lines are closing, stretch is still above equilibrium but losing energy.

• Watch slot 02 as the disagreement probe. Because slot 02 uses hl2 with an SMA baseline and a longer window, it is the slot most likely to lag when the 5m and 60m are telling the same story, and most likely to lead when those two are confused. When slot 02 disagrees with both slot 01 and slot 03, ask why before you trust the blend.

• The reference band at 30 and 70 tells you the reading is in "pay attention" territory, not "reverse now." The band is useful; the instinct to trade off it is not.

Named failure mode. Slot 02 stays the same color as slot 01 for days on end. That is not confirmation. It probably means the instrument has been in a regime where hl2 on a 50-bar SMA happens to align with close on a 20-bar EMA — the slot is doing its real job, but the market is not giving it anything to disagree with. The alignment alerts will fire freely in this environment; see the next paragraph.

Anti-pattern contrast. The broken version of this workflow is three slots with identical source, length, and family, on three stacked timeframes alone. The pane looks like it has three observations. It has one observation sampled three times at different cadences. When it aligns, it tells you little; when it disagrees, the disagreement is usually just timing, not evidence. If you want a clean three-timeframe cadence read, use that configuration knowing what it is. If you want three observations, differentiate at least one of them in a structural way.

Mitigation when you are stuck. If you cannot tell whether slot 02's difference is meaningful, temporarily set Blended Weight = 0 on slot 02. The slot will continue to plot and alert, and the blend will show you what the other two slots look like alone. Compare the blend with and without slot 02. If the blend's regime decisions change, slot 02 is contributing information; if they do not, slot 02 is not currently adding.

Workflow 2: Weight-zero observer slot

Purpose. Keep a slower context read on the pane for reference and alerts without letting it steer the blend. This is the pattern for a trader who wants to see daily context on an intraday setup but does not want the daily to rewrite what the intraday blend is saying.

Setup.

• Slot 01: defaults (5m, EMA(20), weight 33.3).

• Slot 02: defaults (15m, EMA(20), weight 33.3).

• Slot 03: daily (TimeFrame = D), EMA(20) baseline, EMA(3) slow, Weight = 0, enable on.

• Global: On Bar Close? = true. Master smoothing off.

Slot 03 now plots on the pane (so you can see where the daily stretch is sitting), fires per-slot alerts, and participates in the alignment alerts (because alignment cares about enabled slots, not about weights). It does not steer the blend. The blend is a weighted summary of slots 01 and 02 alone.

How to read.

• The blend reads as an intraday stretch summary. Use it the same way you would if slot 03 did not exist.

• Glance at slot 03 (the blue line) to see whether your intraday read is aligned with or opposed to the daily context. Opposed is not wrong; it is information. Some traders use "blend up, slot 03 down" as a sign to take smaller size; others use it as a reason to wait. Pick a rule and write it down somewhere outside the tool.

• The alignment alerts will fire only when all three slots agree, including slot 03. Given slot 03 is on the daily, those alerts will be rare. That rarity is the feature, not a bug.

Named failure mode. You forget slot 03 exists. Three months later a reader hands you the chart and the blue line is on the pane, you do not remember why, and you change Blended Weight = 33.3 on slot 03 to "fix" it. The blend now tracks daily context, your intraday setup stops making sense, and you blame the tool for changing its behavior. Configuration drift is the single biggest tax on long-term users of any configurable indicator. Annotate the weight-zero intent in your own notes, in a TradingView comment, or in a screenshot kept somewhere you will actually find.

Anti-pattern contrast. The broken version is hiding the plot on slot 03 instead of setting its weight to zero. Hide-plot keeps the slot contributing to the blend; weight-zero removes it from the blend. These two buttons do almost opposite things, and readers who flip the wrong one get a silent configuration error.

Mitigation when you are stuck. If you open the chart and cannot remember why slot 03 has weight zero, go back to this workflow — and then decide, on the current instrument and the current session, whether the daily context is actually earning its place on the pane. Observer slots should be there because you use them, not out of inertia.

Workflow 3: Minimal configuration first, smoothing last

Purpose. A setup discipline for a new reader on a new instrument. The point is to get a legible read on the default blend before reaching for the knobs that flatten or sharpen what you are seeing.

Setup.

• Start with the shipped defaults on a 1m or 5m chart of the instrument you want to learn.

• Global: On Bar Close? = true, ATR Length = 14, ATR Sensitivity = 1.0, master smoothing off.

• Run this configuration for at least a few sessions before changing anything.

How to read.

• Watch the unsmoothed blend. Its color, its slope, the width of the fill between blend fast and blend slow.

• Notice where the pane spends time. Is it pinning at the bounds? Is it hovering around 50? Is the band at 30 and 70 actually useful — i.e., does the reading visit that band during moves you care about?

• Only once you can describe the pane's normal behavior on this instrument should you start adjusting. The first adjustment is almost always ATR Sensitivity. If the pane pins for long stretches, sensitivity is too high; if it hovers mid-pane and rarely reaches the reference band, sensitivity is too low. Pick values that let the pane spend useful time in the reference band during the sessions you trade.

• Master smoothing is the last thing to touch. Only enable it after you know what the unsmoothed blend looks like, and after you have tuned sensitivity. When you turn it on, run with a short length first (e.g., 5) and compare side by side with the unsmoothed blend. Every bar the smoothed blend is lime and the unsmoothed is red (or vice versa) is a bar where smoothing delayed your regime read. That delay is the cost.

Named failure mode. Sensitivity gets pushed up first because the pane "does not react enough." After pushing sensitivity up, the reading starts pinning at the bounds, which looks like "strong" behavior. The reader interprets pinning as conviction and starts trading off the pin. Boundary pinning is not intensity; it is the clamp doing what a clamp does. See Limitations & Trust Boundaries for the full argument.

Anti-pattern contrast. The broken version is enabling master smoothing on day one "because it looks cleaner." The pane looks calmer because the tool is late. A reader who builds a habit on a smoothed default and then discovers the lag during a fast regime change will blame the tool. The tool is telling the truth; the configuration prioritized calm over responsiveness, and the reader did not know that.

Mitigation when you are stuck. If you already tuned aggressively and the pane is pinning or feels unresponsive, reset to defaults for a session on the same instrument. Compare what you see at defaults to what you configured. Pick the one that leaves you with more information.

Cross-cutting habits

Three habits that apply across all three workflows and save you from a lot of later confusion.

• Write the intent down, not just the configuration. A saved indicator template captures values; it does not capture why you picked them. If slot 03 is weight zero, a note that says "slot 03 is a daily observer; do not weight unless you are rebuilding the setup" costs you a minute and saves you hours later.

• Compare deliberate changes, one at a time, on the same chart segment. Almost every confused moment with this indicator is a change-and-forget problem, not a tool problem. Every time you change a knob, give yourself a sentence answering "what should this change if it is working?" Then check.

• Keep one baseline configuration you never touch. Save a TradingView template of the shipped defaults and do not modify it. When a tuned configuration starts confusing you, load the baseline on the same chart and read the difference. The question "is this the instrument or is this my setup?" is a lot cheaper to answer when you can toggle between the two in one click.

When none of these workflows fits what you are doing

The three above are scaffolds for the most common Base setups. They are not exhaustive. If you have an approach that does not map cleanly onto any of them, the useful move is not to force-fit one of the three. It is to go back to Visuals & Logic, install the mental model cleanly, and build a workflow from the components. Use one slot for execution reads, one for a deliberate-disagreement probe, and decide case by case whether the third earns a weight or runs as an observer. The named workflows here exist as examples of honest shape, not as a menu.

What does not belong in a Base workflow at any setting: treating the reference band as entries, treating alignment as breadth, or trusting the pane in the first session after a sensitivity change. Those are failure modes regardless of which scaffold you started from.

Where to go next

• You want to understand where these workflows reliably fail in ways the pane will not tell you about: Limitations & Trust Boundaries.

• You need to diagnose something specific that went wrong: Troubleshooting.

• You want to understand the shape of the transformation you are working with: For the Geeks.