5-minute NIFTY shows BUY+ at probability 0.79 — strong, clean, all three engines aligned. The same instant, 1-hour shows SELL. 4-hour also SELL. Daily neutral. The 5-minute row looks like a green-light. The other rows say otherwise. What does the engine actually do? It doesn't pretend the conflict isn't there. It doesn't cancel the 5-minute either. It tempers — conflicting timeframes push back with a fraction of their normal weight, and the scanner's MTF column resolves to one of three states based on that pushback. This lesson is how to read that state correctly and what to do when you see MIXED.
Conflicting timeframes don't cancel
This is the central idea. Lesson 21 covered why higher timeframes weigh more than lower ones — they're less noisy, they represent more aggregated price action. When all timeframes agree, those weights compound and you get a high-MTF-confluence signal.
But what happens when they don't agree? Two naive options exist, and both are wrong:
Option A — ignore the higher timeframe. "I'm trading 5-minute, I don't care what 1-hour says." This works exactly until the 1-hour move actually plays out and your 5-minute long gets steamrolled by a higher-timeframe move you ignored.
Option B — cancel the lower timeframe. "1-hour says SELL, so the 5-minute BUY is invalid." This throws away genuinely useful intraday timing — most institutional entries DO start at lower timeframes before higher ones catch up.
The engine does neither. A 1-hour SELL when the 5-minute is BUY contributes a small fraction of its normal weight, but in the opposite direction. The MTF score moves — meaningfully but not catastrophically — toward the conflict. The engine is telling you: "your 5-minute setup is real, but higher timeframes disagree, so don't size this like a max-conviction trade."
⚠ IMPORTANT CATCH
Conflict is information, not noise. A higher-timeframe disagreement is the market telling you something real — institutions on a slower horizon see a different setup than the one your 5-minute fired on. Sometimes the 5-minute wins (lower timeframes lead). Sometimes the 1-hour wins (higher timeframes are slow but right). The engine's job is to flag the disagreement so you can position-size accordingly. The decision is yours.
The three MTF states — ALIGNED, MIXED, OPPOSED
The engine computes a multi-timeframe alignment score after applying the weight ladder (lesson 21) and the conflict contribution (above). That score crosses the engine's MTF score boundary into one of three states the scanner directly surfaces:
i
ALIGNED
Most timeframes agree on the same direction. The conflict contribution is small or zero; the weighted alignment score clears the engine's threshold comfortably. This is the strongest MTF state — a setup with structural support across the timeframe ladder. Position size accordingly.
ii
MIXED
Some timeframes agree, some disagree or are neutral. The alignment score is meaningful but below the threshold for full alignment. The setup is real but partial — your 5-minute is genuine, but higher timeframes aren't all on your side. The conventional response is smaller position size, tighter stops, or wait for the next bar to see if MIXED resolves to ALIGNED.
iii
OPPOSED
Conflicting timeframes dominate. The alignment score has been pushed past the conflict boundary in the opposite direction of your signal. The 5-minute is firing, but the weight of higher-timeframe disagreement says the market structure is against you. Most disciplined traders skip OPPOSED signals entirely — the headline is misleading and the structural read is bearish for a BUY (or vice versa).
The anchor example — NIFTY 14:00 IST
NIFTY 5m at 14:00 IST. 5m: BUY+ at probability 0.79. 15m: BUY at 0.64. 1h: SELL at 0.60. 4h: SELL at 0.58. 1d: NEUTRAL.
Read it row by row. Two timeframes (5m, 15m) agree on BUY. Two timeframes (1h, 4h) agree on SELL. One (1d) is neutral. The 1-hour and 4-hour disagreements aren't ignored — they push back with their fractional contribution, weighted by the timeframe ladder (and 1h and 4h carry more weight than 5m and 15m).
The math nets out: the MTF alignment score lands well below the ALIGNED threshold and meaningfully into the MIXED zone. The scanner labels the row's MTF column as MIXED. Even though the 5-minute headline reads BUY+ with strong probability, the engine is telling you the rest of the timeframe ladder is not on the same page.
A disciplined Pro trader does one of three things here:
Skip. "Headline strong, structure weak — not my trade."
Size down. Take the trade but at 1/3 or 1/2 the position you'd take on an ALIGNED BUY+.
Wait for resolution. Watch the next 2–3 bars. If the 1h flips back to BUY or NEUTRAL, MIXED can resolve to ALIGNED quickly. If it deepens to SELL+, you avoided a bad entry.
What you do not do is take this row at max position because the 5-minute number looks good. The MTF column exists specifically to prevent that.
Why higher-timeframe conflict carries more pushback
The weight ladder from lesson 21 cuts both ways. A 1-hour BUY confirms a 5-minute BUY with meaningful weight. A 1-hour SELL pushes back against a 5-minute BUY with the same meaningful weight (multiplied by the conflict-contribution fraction). A 1-minute SELL pushes back too, but with a small fraction of what 1-hour does — because the 1-minute is the noisiest timeframe and the engine knows it.
This is why a 5m BUY + 1h SELL is a much louder conflict than a 5m BUY + 1m SELL. The higher-timeframe disagreement is structurally more credible. The scanner doesn't show you these contributions directly — it surfaces the resolved MTF state. But knowing the mechanism is what separates "I see MIXED" from "I understand why MIXED, and what to do about it".
The trader behaviour change
For three lessons (21 + this one + the strategy lab lesson coming next) the practical lesson is: filter on MTF state. Strategy Lab can constrain to "MTF = ALIGNED only" as a filter. Historically this is one of the most powerful single filters available — it shrinks trade count but the remaining trades are systematically higher-quality than the same headline signal without MTF alignment.
The corollary: when you see MIXED or OPPOSED on a row you'd otherwise be excited about, that's the engine doing the work you'd have to do manually otherwise. It's saved you from taking a setup that looks clean on one timeframe but is structurally compromised across the rest.
PRACTICE
Test the MTF filter
Open Strategy Lab. NIFTY50, 5m timeframe (entry trigger), last 60 days.
Run baseline: minProb 0.65, minConf 3, no MTF filter. Note trade count and win rate.
Add filter: MTF state = ALIGNED only. Rerun.
Compare. Trade count will drop — sometimes by 40–60%. Win rate should climb.
Now try MTF state = MIXED. Same baseline filter. The trade count and win rate of MIXED rows is the mirror of what you saved by filtering on ALIGNED.
Conflicting timeframes don't cancel — they push back. Each conflicting TF contributes a small fraction of its normal weight in the opposite direction. Higher timeframes carry more pushback than lower ones.
The MTF column resolves to three states: ALIGNED, MIXED, OPPOSED. Surfaces the engine's already-resolved multi-timeframe alignment score against the engine's threshold.
MIXED means partial setup. Real but not max-conviction. Size down, wait for resolution, or skip — never take it like an ALIGNED.
OPPOSED means the structural read is against your headline. Most disciplined traders skip OPPOSED entirely.
MTF ALIGNED is one of the strongest single filters in Strategy Lab. Fewer trades, systematically higher quality.
With this lesson, the multi-timeframe layer is fully covered. Next up: Lesson 23 — Strategy Lab basics. Three lessons closed Wyckoff. Two lessons closed MTF. Now the place where every Foundations and Playbooks concept actually becomes a testable filter — Strategy Lab. The product becomes operational here.
See it live
📊 Show it live
MTF confluence — weighted timeframe vote
TF
Weight
Direction
Contrib
Weighted
1d
3.0
+1.00
+3.000
4h
2.5
+1.00
+2.500
1h
2.0
+0.40
+0.800
15m
1.5
0.00
0.000
5m
1.0
-1.00
-1.000
1m
0.5
-1.00
-0.500
—
10.5
Σ weighted ÷ Σ weight
—
+4.800
BUY · mtfCat = +0.457
Threshold ±0.05. Weighted vote lands clearly on the BUY side.
MTF threshold is ±0.05. CONFLICT bars contribute 0.4× weight in their dominant direction — they aren't ignored, they're discounted. 1d carries the most weight (3.0) so a strong daily can outweigh a noisy 5m disagreement. This widget defaults CONFLICT to +0.4 for simplicity; the live engine uses the dominant sign from that TF's per-engine breakdown.
5-minute NIFTY पर BUY+ है probability 0.79 पर — strong, clean, तीनों engines aligned। उसी instant 1-hour SELL दिखा रहा है। 4-hour भी SELL। Daily neutral। 5-minute row green-light की तरह दिखती है। बाक़ी rows कुछ और कह रही हैं। Engine actually क्या करता है? वो pretend नहीं करता कि conflict नहीं है। वो 5-minute को cancel भी नहीं करता। वो temper करता है — conflicting timeframes अपनी normal weight का एक fraction लेकर push back करते हैं, और scanner का MTF column उस pushback के basis पर तीन states में से एक पर resolve होता है। यह lesson बताता है उस state को correctly कैसे पढ़ें और जब MIXED दिखे तो क्या करें।
Conflicting timeframes cancel नहीं करते
यह central idea है। Lesson 21 ने cover किया कि higher timeframes lower से ज़्यादा weigh क्यों होते हैं — वो कम noisy हैं, ज़्यादा aggregated price action represent करते हैं। जब सब timeframes agree करते हैं, वो weights compound होते हैं और तुम्हें high-MTF-confluence signal मिलता है।
लेकिन जब वो agree नहीं करते? दो naive options हैं, दोनों ग़लत:
Option A — higher timeframe ignore कर दो। "मैं 5-minute trade कर रहा हूँ, 1-hour क्या कहता है मुझे फ़र्क़ नहीं पड़ता।" यह exactly तब तक काम करता है जब तक 1-hour move actually play out न हो जाए और तुम्हारा 5-minute long एक ignored higher-timeframe move से steamroll हो जाए।
Option B — lower timeframe cancel कर दो। "1-hour SELL कह रहा है तो 5-minute BUY invalid है।" यह genuinely useful intraday timing throw away करता है — ज़्यादातर institutional entries lower timeframes से ही शुरू होती हैं higher catches up करने से पहले।
Engine दोनों में से कुछ नहीं करता। जब 5-minute BUY हो और 1-hour SELL — वो 1-hour अपनी normal weight का एक fraction contribute करता है, लेकिन opposite direction में। MTF score move करता है — meaningfully but catastrophically नहीं — conflict की तरफ़। Engine तुम्हें बता रहा है: "तुम्हारा 5-minute setup real है, but higher timeframes disagree करते हैं, तो इसे max-conviction trade की तरह size मत करो।"
⚠ IMPORTANT CATCH
Conflict information है, noise नहीं। एक higher-timeframe disagreement market तुम्हें कुछ real बता रहा है — slower horizon पर institutions तुम्हारे 5-minute fired setup से अलग setup देख रहे हैं। कभी 5-minute जीतता है (lower timeframes lead करते हैं)। कभी 1-hour जीतता है (higher timeframes slow but right)। Engine का काम है disagreement flag करना ताकि तुम accordingly position-size कर सको। Decision तुम्हारा है।
तीन MTF states — ALIGNED, MIXED, OPPOSED
Engine weight ladder (lesson 21) apply करने के बाद और conflict contribution (ऊपर) apply करने के बाद एक multi-timeframe alignment score compute करता है। वो score engine की MTF score boundary को cross करके तीन states में से एक पर resolve होता है जो scanner directly surface करता है:
i
ALIGNED
ज़्यादातर timeframes same direction पर agree करते हैं। Conflict contribution छोटा या zero है; weighted alignment score engine के threshold को comfortably clear करता है। यह सबसे strongest MTF state है — timeframe ladder के across structural support वाला setup। Position size accordingly।
ii
MIXED
कुछ timeframes agree करते हैं, कुछ disagree करते हैं या neutral हैं। Alignment score meaningful है but full alignment के threshold से नीचे। Setup real but partial है — तुम्हारा 5-minute genuine है, but higher timeframes सब तुम्हारी side पर नहीं हैं। Conventional response — smaller position size, tighter stops, या अगले bar का wait कि MIXED ALIGNED में resolve होता है या नहीं।
iii
OPPOSED
Conflicting timeframes dominate करते हैं। Alignment score conflict boundary को तुम्हारे signal की opposite direction में push कर दिया गया है। 5-minute fire कर रहा है, but higher-timeframe disagreement का weight कहता है market structure तुम्हारे ख़िलाफ़ है। ज़्यादातर disciplined traders OPPOSED signals पूरी तरह skip करते हैं — headline misleading है और structural read BUY के लिए bearish (या vice versa)।
Row by row पढ़ो। दो timeframes (5m, 15m) BUY पर agree। दो timeframes (1h, 4h) SELL पर agree। एक (1d) neutral। 1-hour और 4-hour disagreements ignore नहीं होते — वो अपनी fractional contribution के साथ push back करते हैं, timeframe ladder से weighted (और 1h aur 4h 5m और 15m से ज़्यादा weight carry करते हैं)।
Math net out होती है: MTF alignment score ALIGNED threshold से well below land होती है और meaningfully MIXED zone में। Scanner row के MTF column को MIXED label करता है। 5-minute headline strong probability के साथ BUY+ पढ़ने के बावजूद, engine तुम्हें बता रहा है कि बाक़ी timeframe ladder same page पर नहीं है।
एक disciplined Pro trader यहाँ तीन में से एक काम करता है:
Size down। Trade लो but ALIGNED BUY+ पर जो position लेते उसका 1/3 या 1/2।
Resolution का wait करो। अगले 2–3 bars देखो। अगर 1h वापस BUY या NEUTRAL पर flip हो जाए, MIXED जल्दी ALIGNED में resolve हो सकता है। अगर वो SELL+ में deepen हो जाए, तुमने bad entry avoid किया।
जो तुम नहीं करते — इस row को max position पर लेना सिर्फ़ इसलिए कि 5-minute number अच्छा दिख रहा है। MTF column specifically इसी को prevent करने के लिए मौजूद है।
Higher-timeframe conflict ज़्यादा pushback क्यों carry करता है
Lesson 21 का weight ladder दोनों ways cut करता है। एक 1-hour BUY 5-minute BUY को meaningful weight के साथ confirm करता है। एक 1-hour SELL 5-minute BUY के against same meaningful weight के साथ push back करता है (conflict-contribution fraction से multiplied)। एक 1-minute SELL push back करता है too, but जो 1-hour करता है उसका छोटा fraction — क्योंकि 1-minute noisiest timeframe है aur engine यह जानता है।
इसलिए 5m BUY + 1h SELL एक 5m BUY + 1m SELL से बहुत louder conflict है। Higher-timeframe disagreement structurally more credible है। Scanner यह contributions directly नहीं दिखाता — वो resolved MTF state surface करता है। But mechanism जानना यही separates "मैं MIXED देख रहा हूँ" को "मैं समझता हूँ MIXED क्यों, aur उसके बारे में क्या करना है"।
Trader behaviour change
तीन lessons (21 + यह + next coming strategy lab lesson) के लिए practical lesson है: MTF state पर filter करो। Strategy Lab "MTF = ALIGNED only" को filter के रूप में constrain कर सकता है। Historically यह available सबसे powerful single filters में से एक है — trade count shrink होता है but बचे हुए trades systematically same headline signal MTF alignment के बिना से higher-quality हैं।
Corollary: जब तुम एक row पर MIXED या OPPOSED देखते हो जिस पर तुम excited होते otherwise, वो engine वो काम कर रहा है जो otherwise तुम्हें manually करना पड़ता। उसने तुम्हें एक setup लेने से बचा लिया जो एक timeframe पर clean दिखता है but बाक़ी पर structurally compromised है।
Conflicting timeframes cancel नहीं करते — push back करते हैं। हर conflicting TF अपनी normal weight का छोटा fraction opposite direction में contribute करता है। Higher timeframes lower से ज़्यादा pushback carry करते हैं।
MTF column तीन states में resolve होता है: ALIGNED, MIXED, OPPOSED। Engine का already-resolved multi-timeframe alignment score engine के threshold के against surface करता है।
MIXED मतलब partial setup। Real but max-conviction नहीं। Size down करो, resolution का wait करो, या skip करो — कभी ALIGNED की तरह मत लो।
OPPOSED मतलब structural read तुम्हारे headline के against है। ज़्यादातर disciplined traders OPPOSED पूरी तरह skip करते हैं।
MTF ALIGNED Strategy Lab में सबसे strongest single filters में से एक है। कम trades, systematically higher quality।
इस lesson के साथ, multi-timeframe layer पूरी तरह cover हो गई। Next up: Lesson 23 — Strategy Lab basics। तीन lessons ने Wyckoff close किया। दो lessons ने MTF close किया। अब वो जगह जहाँ हर Foundations और Playbooks concept actually testable filter बनता है — Strategy Lab। Product यहाँ operational बनता है।
लाइव देखो
📊 Show it live
MTF confluence — weighted timeframe vote
TF
Weight
Direction
Contrib
Weighted
1d
3.0
+1.00
+3.000
4h
2.5
+1.00
+2.500
1h
2.0
+0.40
+0.800
15m
1.5
0.00
0.000
5m
1.0
-1.00
-1.000
1m
0.5
-1.00
-0.500
—
10.5
Σ weighted ÷ Σ weight
—
+4.800
BUY · mtfCat = +0.457
Threshold ±0.05. Weighted vote lands clearly on the BUY side.
MTF threshold is ±0.05. CONFLICT bars contribute 0.4× weight in their dominant direction — they aren't ignored, they're discounted. 1d carries the most weight (3.0) so a strong daily can outweigh a noisy 5m disagreement. This widget defaults CONFLICT to +0.4 for simplicity; the live engine uses the dominant sign from that TF's per-engine breakdown.
03
Quick Check
5 questions · best score saves
Har question ka turant feedback milega. Best score save hota hai.
Q1Jab 1h aur 4h dono SELL pe hain aur 5m BUY+ dikhata hai, toh MTF column kya state dikhayega?
Q2MIXED MTF state mein disciplined trader ka standard response kya hona chahiye?
Q3Higher-TF opposition engine ke signal display mein practically kaise dikhti hai?
Q41m SELL aur 1h SELL dono 5m BUY ke against pushback denge — kaunsa zyada pushback dega?
Q5MTF conflict handling aur 'don't trade against the daily' rule kaise related hain OptionLab Pro mein?