What it is
Support and resistance zones woh price-areas hain jahaan stock pehle ruka, reverse hua, ya consolidate kiya. Trader manual ek line khench leta hai previous high pe. Tietiy yeh same kaam ek deterministic algorithm se karta hai — taaki 437 stocks ka label same rule se aaye, har shaam same.
Analogy: zones memory of crowd hote hain. Jahaan log pehle bechh chuke ya khareed chuke, woh price emotionally important rehta hai. SR zone ka structure ek vote-count hai us crowd memory ka.
Tietiy mein har zone ek pivot point se shuru hota hai. Pivot ek bar hai jahaan price ne local high/low banaya. Zone usse paar similar prices ke "cluster" milake ban'ta hai — single price line nahi, ek band.
How tietiy computes it — TWO parallel pivot families
Yeh shayad cockpit ka sabse interesting design decision hai. Tietiy do pivot families parallel chalata hai, dono labelled, dono published:
-
lookback_n10— fractal-style pivot detection, N=10 bar lookback. Yeh exact mirror hai production scanner ke algorithm ka. Cross-source consistency is the whole point. -
zigzag— reversal-threshold algorithm, default 5% threshold (industry standard for daily stocks per StockCharts / MetaTrader convention). Visual chart-friendly. Detection close pe, stored price wick extreme pe.
Har swing_pivot primitive apna pivot_source
field carry karta hai — aap dekh sakte ho yeh kaunse family ka pivot hai.
Aur ek non-negotiable rule: last pivot of any family is always
provisional. Bar close ke baad bhi naya swing develop hone tak repaint
ho sakta hai. Scanner gates kabhi provisional pivot nahi use karte
(CI-enforced).
Zones bante hain pivots ke clustering se. Same price-band ke around multiple pivots = ek zone. Strength factors: kitne pivots cluster mein, kitna volume tha pivot bars pe, kitna recent.
The "MAJOR" rename — why multi_touch_3p exists
Originally tietiy zones ko "MAJOR" tag deta tha jab 3+ touches hote. Logic conventional tha: zyada touches = zone strong. Honest base-rate testing ne yeh refute kar diya, n=44,000+ historical zone touches par.
Result: 3+ touches wali zones break hone ki probability statistically higher nikli, not lower. Touch count strength nahi hai — fatigue hai. Har baar zone ko test kiya jaata hai, demand / supply thin hoti jaati hai. 4th, 5th touch usually break leke aata hai.
Isi liye field name change kar diya gaya — MAJOR se multi_touch_3p. Same data, honest label. Touch count ab ek
"fatigue" feature ke roop mein enter karta hai, "strength" ke roop mein
nahi.
What this site shows you
Stock page chart pe horizontal bands draw hote hain — har zone ek band, multi-touch zones thoda highlighted. Hover karke aap dekh sakte ho: pivot_source, touch count, kab last touch hua, volume profile. Each band's edge prices visible — exact entry/SL ka decision aapka.
How to read it
- Fresh zone (1–2 touches), good volume = highest probability hold in base-rate testing. "Multi-touch zones break more" rule yahaan apply nahi.
- multi_touch_3p zone = padhne ke time mein "danger zone" treat karo — base-rate says break is more likely than yet another hold.
- Trend UP mein zones ko demand zones ki tarah read karo (price pe pulled back to that band). Trend DOWN mein wahi zones supply ban jaate hain.
- Last pivot provisional. Iska matlab newest zone ki edge price thodi shift ho sakti hai next session. Decisions provisional pivot pe tightly hang karna risky hai.
- Dono pivot families dekhna chahiye — zigzag aur lookback_n10 agar same zone par converge kar rahe hain, woh zyada robust zone hai.
What this does NOT tell you
- Zone hold karega ya tootega. Yeh ek descriptive computed zone hai, outcome prediction nahi.
- Entry / stop placement. Zone edge se kitna door SL rakhna — aapka rule. Volatility (ATR), regime, sizing — sab alag layers.
- Intraday zones. v1 daily zones hain. Intraday SR is a separate problem (different lookback, different noise floor).
- Fundamental supports. Earnings floor, book value, etc. price zones se asambandhit hain.
Key honest takeaway. Conventional TA "the more touches, the stronger the level" wrong nikli hai humare 44k-sample base-rate test mein. Tietiy is data ko hide nahi karta — field name hi change kar diya. Yeh "describe, never predict" principle ka ek concrete example hai.