Janus Atlas v1.0
Advanced Learning Guide
Master the Art of Level Trading • Psychology • Decision Trees • Common Mistakes
⏱️ Reading Time: 15 minutes
🎯 Why Most Traders Fail at Level Trading
They trade every level touch, ignore test counts, and fight higher timeframe trends. This guide teaches you to identify which levels matter, when to trade them, and how to avoid the psychological traps that destroy level-based strategies.
🚀 Your First Reading in 5 Minutes
Never used Janus Atlas before? Start here.
Step 1: Add it to a chart
Load Janus Atlas on any timeframe (1H is the easiest to read at first). Turn on daily pivots, VWAP and session highs and lows, and leave the other families off until those three are familiar.
Step 2: Look for a cluster
Find two or more levels within 1% of each other. Turn on Confluence Zones and the indicator marks them for you, with a count of how many families agree at that price.
Step 3: Read the test count
Hover a cluster to see how many times price has already been there. A level touched once or twice is a different level from one touched six times, and they are drawn identically.
Step 4: Read the context around it
Is the higher timeframe pointing the same way price is approaching from? A cluster met with the trend and a cluster met against it are two different readings of the same lines.
Step 5: Note the width of the cluster
Three levels inside 0.4% is a narrow band. Three levels spread over 1% is a zone, not a line, and the difference matters more than the count does.
Worked through: SPY 1H chart
- Price at $450, the daily trend pointing up
- Cluster found:
- Daily pivot: $449.80
- VWAP: $450.20
- Session high: $450.10
- Three families inside 0.4%, so the band is narrow
- Test count: two touches so far today
- The reading: a narrow three-family band, lightly tested, approached with the higher timeframe rather than against it
- What it is not: a prediction. The same reading appears before prices that stop there and before prices that go straight through
Your first few readings will be rough, and that is fine. The guides below are about making them sharper.
📋 The 3-2-1 Rule for Janus Atlas
Memorize This Framework
3 Things to ALWAYS Check:
- ✅ Cluster: Minimum 2 levels within 1% (not an isolated level)
- ✅ Test Count: Less than 4 tests (fresh levels hold better)
- ✅ Higher TF Alignment: Check one timeframe higher, trend must align
2 Things to NEVER Do:
- ❌ Never trade over-tested levels (4+ tests = weakened, likely to break)
- ❌ Never fight higher timeframe trend (lower TF levels are speed bumps in larger trends)
1 Golden Rule:
📌 If you can't explain the setup in 15 seconds, skip it.
Simple setups work. Complicated setups fail. If you need 5 minutes to convince yourself, it's probably not a good trade.
🧠 Level Trading Psychology: The 3 Critical Challenges
💥 Challenge 1: "This Level Has Held 5 Times Before" Trap
What Happens: You see a support level that's been tested and held 5 times. You think "This is super strong: it's held 5 times!" You buy the 6th test. Price immediately breaks through, stops you out, and never looks back.
Why This Happens: You're confusing past strength with current strength. Each test weakens a level like cracks forming in ice. The 6th test is often the breaking point.
The Fix: Fresh levels (1-2 tests) hold better than over-tested levels (4+ tests). After 4 tests, wait for the break and trade the retest instead of the bounce.
Mental Script: "4+ tests = likely to break soon. I'll wait for the break and trade the retest, not the bounce."
⚔️ Challenge 2: Fighting the Higher Timeframe Trend
What Happens: You read 15-minute resistance at $50 as a level, because price has stalled there three times today. Price goes straight through to $52. You open the daily chart afterwards and find a strong uptrend. The 15-minute resistance was a pause inside a larger move, and the reading never said otherwise because you never asked it.
Why This Happens: You're zoomed in so far that you can't see the forest for the trees. Lower timeframe levels are speed bumps, not roadblocks, when they oppose higher TF trends.
The Fix: open one timeframe higher before you finish reading any level. A level met with the higher timeframe and the same level met against it are two different readings, and Janus Atlas draws them identically because it draws where, not which way.
Mental Script: "Is this level being approached with the higher TF or against it? Against is a counter-trend reading, and worth writing down as one."
🎯 Challenge 3: Isolated Levels vs Cluster Confusion
What Happens: You read a single Fibonacci level at $50 as significant because "Fib levels are powerful". Price goes through it. You dismiss a cluster of 3 families at $51, a pivot with VWAP and the session high, because "too many lines means confusion". Price turns there.
Why This Happens: You're prioritizing level type (Fibonacci) over level confluence (clustering). The market doesn't care about your preferred indicator: it responds to zones where multiple levels converge.
The Fix: Cluster strength matters more than level type. A cluster of 3 "weak" pivot levels is stronger than 1 isolated "powerful" Fib level.
Mental Script: "How many levels are clustered here? If just one, I need other confirmation. If 3+, that's strong confluence."
🌳 How Much Support Does This Level Have?
┌───────────────────────────┐
│ PRICE APPROACHING A LEVEL │
└───────┬───────────────────┘
│
▼
┌─────────────────────────────┐
│ Is it part of a cluster │
│ (2 or more levels)? │
└──┬────────────────────┬─────┘
│ │
NO YES
│ │
▼ ▼
Single line reading Read on
│
▼
┌────────────────────────────┐
│ How many times tested? │
└──┬───────────────────┬─────┘
│ │
4 OR MORE UNDER 4
│ │
▼ ▼
Worn level reading Read on
│
▼
┌────────────────────────────────┐
│ Higher timeframe trend agrees? │
└──┬─────────────────────┬───────┘
│ │
NO YES
│ │
▼ ▼
Countertrend reading Read on
│
▼
┌──────────────────────────┐
│ How wide is the cluster? │
└──┬─────────────────┬─────┘
│ │
OVER 1% UNDER 1%
│ │
▼ ▼
Zone, not a line Well supported reading
⚡ What each branch is telling you
- Single line: one family drew it. Nothing else on the chart agrees that this price is interesting
- Worn level: four or more touches. The level has been visited enough that whatever was resting there has largely been used up
- Countertrend: the level is being approached against the higher timeframe. It is still a level, read in a harder context
- Zone, not a line: the families agree there is something here, but disagree about where by more than a per cent
None of the four is a verdict on what to do. They are four different charts that all print a cluster, and telling them apart is what the indicator is for.
✅ Your First 3 Trades - Verification Checklist
Print This and Keep it Visible While Trading
For every level price reaches, record:
Level #_____ (Date: ______)
- ☐ Cluster or single line, and how many families ___
- ☐ Width of the cluster ___% from top to bottom
- ☐ Test count before this touch ___
- ☐ Higher timeframe agreed, disagreed, or was flat
- ☐ Which side price approached from
- ☐ Whether the label named the families or you had to guess
- ☐ You can state the reading in 15 seconds
After Your First 3 Trades, Review:
- Did I record all three before the following bars printed? Y / N
- Which line did I skip most often? _______________
- Did the narrow clusters look different afterwards from the wide ones? _______
- Did the lightly tested ones look different from the worn ones? _______
- What will I look at more carefully on the next three? _______________
Important: Don't expect perfection. If you followed the checklist and still lost, that's OK: level trades aren't 100%. Judge the process, not any single trade, and track your own results over a meaningful sample. If you're losing because you skipped checklist items, that's what we need to fix.
🚫 Top 5 Mistakes That Kill Level Traders
Mistake #1: Trading Every Level Touch
What Happens: You enable 10+ level types (Fibs, pivots, VWAP, session levels, weekly levels, monthly levels...). Your chart looks like electrical wiring. Price touches a level every few bars. You take every touch as a signal. Result: 20-30 trades per week, most lose, you're exhausted and broke.
The Fix: a touch on its own says almost nothing, because price touches something on nearly every bar. Four things separate one touch from another:
- ✅ Is it a cluster, and of how many families
- ✅ How many times it has already been tested
- ✅ Whether the higher timeframe agrees with the approach
- ✅ How wide the cluster is, which decides whether it is a line or a zone
Most touches fail at least one of the four. Reading which one is the whole exercise.
Mistake #2: Ignoring Test Count (Trading Over-Tested Levels)
What Happens: Support at $50 has been tested 6 times and held each time. You read the seventh touch as the strongest of the series. It goes through and price reaches $48. The test count was in the tooltip the whole time, and it was saying the opposite of what you read into it.
The Fix: read the test count as history rather than as a rating:
- 🟢 1-2 tests: Fresh level, trade it
- 🟡 3 tests: Acceptable, use caution
- 🔴 4+ tests: Over-tested, wait for break then trade retest
Mistake #3: Confusing Level Type with Level Strength
What Happens: You trade Fibonacci levels exclusively because "Fibs are powerful and based on sacred geometry." They fail repeatedly. Meanwhile, you skip pivot clusters because "pivots are just basic levels." Those pivot clusters work perfectly.
The Truth: The market doesn't care about your indicator religion.
The Fix: Clustering matters more than level type. 3 "weak" pivots clustered together = stronger than 1 "powerful" isolated Fib. Prioritize confluence over ideology.
Mistake #4: Using Levels on Wrong Timeframe
What Happens: You're scalping 5-minute charts but only have Weekly and Monthly levels enabled. They're so far away they're useless. Or you're swing trading Daily charts but Session levels are cluttering your chart with noise.
The Fix: Match level types to trading timeframe:
- 📊 5M-15M users: Session levels, Daily pivots, Opening Range
- 📊 1H-4H users: Daily levels, Weekly pivots, Gap Levels
- 📊 Daily users: Weekly levels, Monthly pivots
Enable what's relevant for your timeframe. Disable everything else.
💡 Pro Tip: Enable Killzones to see the session windows (London, NY AM and the rest) as background shading, so the hour a level was touched in is on the chart.
Mistake #5: Reading a Cluster as a Line
What Happens: You write down a support cluster as "$50". Price trades to $49.95 and then to $51.50. Reading the log later, you cannot tell whether the level held or broke, because you recorded a number and the cluster was a band.
Why This Happens: the label prints one price, so the cluster looks like one price. It is not. Three families rarely land on the same tick, and the distance between the outermost two is the width of the thing you are reading.
The Fix: record the edges, not the midpoint. A cluster whose families sit at $49.90 and $50.20 is a band three tenths of a per cent wide, and price visiting $49.95 is inside it, not through it. Written down that way, next month's log can be compared with this month's.
❓ Top 10 Questions from New Users
Quick Answers to Common Confusion
Q1: Why did the level break right after I entered?
A: Check test count. 4+ tests = weakened level, likely to break. Also verify you checked higher TF: if you're trading against a larger trend, levels break easily.
Q2: Should I trade every cluster I see?
A: Most clusters are worth reading and few are worth much attention. The three that separate them are whether the higher timeframe agrees with the approach, how many times the level has already been tested, and how wide the cluster is. A cluster that fails all three is still a cluster, drawn identically to one that passes all three.
Q3: How long should I wait for price to react at a level?
A: Set a time limit. If no reaction in 5-10 bars (for your timeframe), exit. Don't hope. If the level was strong, price would have reacted quickly.
Q4: What if price gaps through my stop?
A: Gaps happen, especially around news, and a level cannot stop a market from opening somewhere else. What the indicator can tell you afterwards is whether the gap opened above or below the cluster, and whether price came back to it, which is the part worth reading.
Q5: Can I use Janus Atlas for scalping (1M-5M charts)?
A: Yes, but use Session levels, Intraday pivots, and Opening Range. The OR high/low from the first 15-30 minutes creates great breakout levels for scalpers. Weekly/Monthly levels are too far away.
Q6: Why do some clusters work better than others?
A: Three things, all visible before anything happens: how many families landed there, whether the higher timeframe agrees with the approach, and how many times the level has already been tested. A three-family cluster tested once, approached with the Daily trend, with volume agreeing, is the most agreement the chart can show at that price.
Q7: Should I enter on first touch or wait for confirmation?
A: Depends on risk tolerance. Aggressive: first touch with tight stop. Conservative: wait for rejection candle (wick rejection + close away from level). Both work; pick your style.
Q8: What if I'm stopped out and then the level holds?
A: Levels aren't walls. They're zones. If your stop was placed beyond the level (0.3-0.5% buffer) and you still got stopped, the level temporarily failed. Don't revenge trade. Wait for next setup.
Q9: Can I combine multiple Janus indicators (pivot + VWAP + Fib)?
A: Absolutely. That's the whole point. When 3+ different level types cluster together, that's confluence = stronger zone.
Q10: How do I know if I'm improving?
A: Track how often you recorded the reading before the following bars printed rather than after, and how often you checked all four lines rather than the two you like. If you are recording after the fact more than one time in five, that is what to fix first, and it has nothing to do with the levels.
Q11: How do I use the new Fibonacci Levels feature?
A: Enable Fib Set 1 or 2 in Group 12 settings. Choose an anchor (Daily H/L, Weekly H/L, etc. - 19 options). The indicator auto-draws retracement levels (0.236, 0.382, 0.5, 0.618, 0.786, 0.886). Key levels are 0.382, 0.5, 0.618 (golden ratio). You can show two Fib sets simultaneously with different anchors/colors for multi-timeframe confluence.
📄 Printable Quick Reference Cheat Sheet
┌──────────────────────────────────────────────────────────────┐
│ JANUS ATLAS QUICK REFERENCE │
│ (Save or Print This) │
├──────────────────────────────────────────────────────────────┤
│ │
│ ✅ A WELL SUPPORTED READING: │
│ • Cluster (2+ families within 1% of each other) │
│ • Test count < 4 (the level is still lightly worn) │
│ • Higher TF agrees with the approach │
│ • The cluster is narrow, so it is a line not a zone │
│ • You can state the reading in 15 seconds │
│ │
│ ⚠️ A THIN READING: │
│ • One family drew it, nothing else agrees │
│ • Tested 4+ times, so most of what rested there is gone │
│ • Approached against the higher timeframe │
│ • The families disagree by more than a per cent │
│ • You need 5 minutes to describe what you are seeing │
│ │
│ 📍 WHERE THE LEVEL SITS: │
│ • A cluster is a band, not a line, and has a width │
│ • Its edges are the outermost families in the cluster │
│ • Example: families at $99.60 and $100.30 make a │
│ 0.7% band, not a level at $100 │
│ │
│ 🧮 READING THE TEST COUNT: │
│ • 1-2 tests: 🟢 lightly worn │
│ • 3 tests: 🟡 getting used up │
│ • 4+ tests: 🔴 heavily worn │
│ • The count is history, not a rating │
│ │
│ 📊 TIMEFRAME MATCHING: │
│ • 5M-15M: Session levels, Daily pivots │
│ • 1H-4H: Daily levels, Weekly pivots │
│ • Daily: Weekly levels, Monthly pivots │
│ │
│ 🎓 THE 3-2-1 RULE: │
│ 3 Always Check: Cluster, Test count, Higher TF │
│ 2 Never Do: Read a 4th test as the first, Ignore HTF │
│ 1 Golden Rule: Explain in 15 sec or skip │
│ │
└──────────────────────────────────────────────────────────────┘
Keep this visible on your second monitor while reading!
🎓 Your Learning Journey - Success Milestones
You're Progressing When You See These Signs
📅 Week 1: Recognition Phase
- ✅ You can spot clusters within 10 seconds of looking at a chart
- ✅ You instinctively check test count before considering entry
- ✅ You're starting to ignore isolated levels automatically
- ✅ You remember to check higher TF without needing a reminder
- ✅ Your stops are placed BEYOND levels, not AT them
📅 Week 2-3: Execution Phase
- ✅ Your stop placement is consistent (0.3-0.5% buffer every time)
- ✅ You check higher TF before every trade (it's a habit now)
- ✅ You're comfortable letting most signals go (filtering is natural)
- ✅ You can explain your setups clearly in under 15 seconds
- ✅ You're tracking trades and noticing patterns in your mistakes
📅 Month 1+: Mastery Phase
- ✅ Your reading of a cluster stops changing when you look at it again the next day
- ✅ You're combining Janus with other indicators naturally (Pentarch, Volume Oracle, etc.)
- ✅ You can teach the 3-2-1 rule to someone else from memory
- ✅ You're spotting over-tested levels before entering (saving money)
- ✅ You trust your checklist more than your emotions
🚨 Warning Signs (You Need to Review the Guide):
- ❌ You still cannot say, without checking, how many families drew your last ten clusters
- ❌ You're taking 15+ level trades per week (too many = not filtering)
- ❌ You can't remember the 3-2-1 rule without looking it up
- ❌ You're still reading a wick through a level as a level that broke
- ❌ You're reading against higher TF trends without noting that you are
Remember: Mastery takes time. Don't compare your Week 1 to someone's Month 6. Focus on: (1) following the checklist, (2) reading back the readings that did not hold, (3) gradual improvement. If you're making fewer mistakes in Week 3 than Week 1, you're on the right path.
🔗 Synergy: Pairing Janus Atlas with Other Indicators
🎯 High Synergy Combinations
- + Pentarch: Level clusters + Exhaustion Counter signals = precise reversal timing at key levels. You know WHERE (Janus) and WHEN (Pentarch).
- + OmniDeck: A level cluster with several systems agreeing on the same bar. The count of agreeing systems is what the reading rests on, and it is on screen.
- + Volume Oracle: Support/resistance levels + volume analysis = level strength validation. See if volume is confirming or rejecting the level.
🎲 Common Trading Combinations
- Janus support cluster + Pentarch Count 9 Buy → Reversal at tested level with cycle confirmation
- Janus resistance + OmniDeck Count 13 Sell + Regime red → Multi-layer resistance confluence
- Janus level + Volume Oracle trapped signal → Trapped trader zones at key levels
💡 Why These Pair Well
Janus Atlas identifies WHERE price may react (spatial analysis: levels and zones). Pentarch/OmniDeck identify WHEN to enter (temporal analysis: timing and cycles). Volume Oracle confirms flow direction (volume analysis: accumulation vs distribution).
Combining spatial + temporal + participant analysis creates a complete picture: the right place, at the right time, with the right players.
Ready to apply what you've learned?
← Back to Janus Atlas DocumentationEducational only. Trading involves substantial risk of loss. Not financial advice. Past performance does not guarantee future results.