Onboarding Checklist¶

A seven-day guide to reading the Signal Pilot indicators. It runs from installing one to keeping a log of readings written before the outcome.

🎯 Overview: Your First Week Beginner Friendly¶

Daily time commitment: 30-60 minutes By end of week: Able to read the five events and record what each one showed Recommended pace: Master each day before moving on

📅 Day 1: Setup & Installation Beginner Friendly¶

Morning: Account Setup (30 minutes)¶

Check: TradingView subscription is active
Log into TradingView
Note which plan you are on: Free holds three indicators per chart, paid tiers hold more
If not yet upgraded: Consider upgrading
Check: Signal Pilot access granted
Check email for confirmation
If no email after 24h: Contact support
Verify: your TradingView username is correct
Test: indicator access
Open TradingView
Click "Indicators" button
Search for "Signal Pilot" or "Pentarch"
Pentarch v1.0, or whatever the latest version is, should appear in the list
If not visible: Check access status

Afternoon: First Indicator Install (30 minutes)¶

Add Pentarch to a chart
Open Bitcoin (BTCUSD) chart
Set Daily timeframe
Click "Indicators"
Search for "Pentarch"
Click "Pentarch v1.0" to add
Look around the indicator
See the 5 signal types on chart
Identify TD, IGN, WRN, CAP, BDN labels
Scroll back through history
Watch how the signals fall
Customize visual settings (optional)
Click indicator name → Settings
Adjust colors in "Style" tab if needed
Keep calculations on default
Save your setup
Navigate to top menu → "Layouts"
"Save as..." → Name it "BTC Pentarch Daily"

✅ Day 1 complete Your first indicator is on the chart.

⚠️ Common First-Day Mistakes

Don't worry if you experience any of these - they're completely normal!

😰 "I don't see any signals yet"

This is NORMAL. On Daily timeframe, you may need to wait a few days to see your first live signal. Signals appear more frequently on lower timeframes (1H, 15m) and on the Daily they are rarer, each covering more ground. Use the time to observe historical signals by scrolling back through the chart - you'll see dozens of them in the past 3-6 months.

👻 "The signal disappeared!"

This is EXPECTED behavior. Signals update in real-time during the current bar but only confirm when the bar closes. If you see a signal mid-bar and it disappears, that means the conditions changed before the close. Only trust signals that appear on closed bars. Set your alerts to "Once Per Bar Close" to avoid false notifications.

📊 "Too many lines on my chart"

Easy fix: If you added Janus Atlas and see 30+ lines, this is overwhelming. Go to indicator settings → Style tab → Disable most levels except the 5 core ones: Daily High/Low, Weekly High/Low, and Anchored VWAP. You can add more levels gradually as you get comfortable.

⏰ "Which timeframe should I use?"

Start with Daily. Fewer events arrive on the Daily, and each one has more bars behind it. Once you're comfortable (after Week 2-3), you can explore 4H and 1H. Avoid anything below 15-minute charts until you're an advanced user - lower timeframes have more noise and false signals.

🤔 "How long should I observe before trading?"

Minimum 2-4 weeks. Fifty events is the sample the rest of these docs asks for before judging anything, across more than one kind of market. Use this first week to learn event identification. Week 2-4 should be paper trading only. Live trading should start in Week 4+ after you've built pattern recognition skills.

📅 Day 2: Learn the 5 Events¶

Goal: Understand what each event means¶

✅ Day 2 Complete You can identify all 5 event types.

📅 Day 3: Multiple Timeframes & Markets¶

Goal: See how events appear across different contexts¶

Compare timeframes
Open Bitcoin on Daily (existing chart)
Open new chart: Bitcoin on 4H
Add Pentarch to 4H chart
Open third chart: Bitcoin on 1H
Add Pentarch to 1H chart
Compare: Notice more events on lower timeframes
Try different markets
Open Ethereum (ETHUSD) - Daily
Add Pentarch
Open S&P 500 (SPX or SPY) - Daily
Add Pentarch
Open EUR/USD - Daily
Add Pentarch
Note what differs
Note which markets have more events
Identify which are cleaner/clearer
Determine your preferred timeframes
Write down your observations
Choose your focus
Select 1-2 markets to trade
Select preferred timeframe (recommend starting with Daily or 4H)
Set up layouts for each

✅ Day 3 Complete You understand how indicators adapt to different markets.

✅ Knowledge Check (Day 1-3)

Question: After completing Days 1-3, which two Pentarch signals should you be able to identify as "Early-Cycle"?

📅 Day 4: Add Your First Alert¶

Goal: Automate event notifications¶

Create your first alert
Open your main chart (BTC Daily)
Right-click chart → "Add Alert"
Condition: Select "Pentarch v1.0"
Event: Choose "IGN Event"
Options: Set "Once Per Bar Close" (critical!)
Name: Enter "BTC Daily IGN - Potential Long"
Expiration: Set 1 month (or "Don't expire")
Actions: Check Notification
Click "Create"
Create exit alert
Right-click chart → "Add Alert"
Condition: Select "Pentarch v1.0"
Event: Choose "CAP Event"
Options: Set "Once Per Bar Close"
Name: Enter "BTC Daily CAP - Exhaustion Signal"
Create the alert
Set up mobile notifications
Download TradingView app (if not already installed)
Log into the same account
Settings → Notifications → Enable All
Phone Settings → Apps → TradingView → Allow Notifications
Test your alerts
Switch to 15m chart (signals fire more often)
Create test alert on 15m
Wait for a signal (typically happens quickly)
Check that the notification arrives
Create alerts for your watchlist
Add alerts for your 2-3 chosen markets
Configure alerts for IGN patterns (common for early-cycle monitoring)
Configure alerts for CAP/BDN patterns (common for late-cycle monitoring)

✅ Day 4 complete The signals now come to you.

📅 Day 5: Add Janus Atlas (Levels)¶

Goal: Understand where events have most confluence¶

Add Janus Atlas to your chart
Open BTC Daily chart
Click "Indicators"
Search for "Janus Atlas"
Add "Janus Atlas v1.0"
Identify level types
Levels below price, which act as support: dL and wL, the day and week lows
Levels above price, which act as resistance: dH and wH, the day and week highs
FVG zones (shaded rectangles)
Confluence zones, where several levels sit close together
Find confluence setups
Scroll through the chart
Find IGN signal AT support level
Mark 3-5 examples
Find CAP signal AT resistance level
Mark 3-5 examples
Compare the context around each
Compare an IGN that lands on a major support with one out in open space
Note which of the two had a level under it, and which did not
Notice: an event on a level gives you a reference the event alone does not
Update your trading rules
Example confluence concepts to study:
- How IGN behaves when it lands on a major support level
- How CAP and BDN behave when they land on a major resistance level
- How both differ from the same events out in open space

✅ Day 5 Complete You can tell an event on a level from one in open space.

📅 Day 6: Reading Events Against Levels Intermediate¶

Day 6: Distance, Confluence and Context (45 minutes)

⚠️ The Day That Changes the Rest

Up to here you have read one indicator at a time. Today two of them are read together, which is where most of the useful information on a chart actually lives.

Morning (25 minutes): Measuring Distance

Measure the gap between an event and the nearest level
- Find any Pentarch event on your chart and the closest Janus Atlas level below or above it
- Write down the distance, as a percentage of price and in the symbol's own points
- Do it for five events. The spread between the closest and the furthest is the thing worth knowing
Put the distance in the symbol's own units
- A 150-point gap on an index and a 150-point gap on a currency pair are not the same gap
- Divide the distance by the symbol's ATR to get a number that compares across markets
- An event half an ATR from a level and one three ATR away are different readings, and both print the same label
Notice which side of the event the level sits on
- A level below a bullish event and a level above one describe different structures
- Both are visible before anything happens, and neither is on the event's own label
- Record which, every time. It is the single cheapest piece of context on the chart

Afternoon (20 minutes): Understanding Janus Atlas Reference Levels

Identify key Janus Atlas levels
- Below current price: Janus Atlas support levels (Daily Low, Weekly Low, etc.)
- Above current price: Janus Atlas resistance levels (Daily High, Weekly High, etc.)
- Example: IGN event at $50,000 → Daily Low at $49,900 provides structural reference
- Janus levels provide objective reference points for analysis
Understand level confluence
- When multiple Janus levels cluster together = stronger structural zone
- Example: Daily Low + Weekly Low at similar price = confluence zone
- Events at confluence zones have additional structural context
- Janus levels help identify key structural areas on any timeframe
See what a chart looks like with no level nearby
- Find an event with no Janus Atlas level within an ATR of it
- That is a real state, not a failure of either indicator, and it is common
- An event in open space and an event at a three-family cluster are the two ends of the range
- Knowing which one you are looking at is the whole point of running both

📊 Worked Through: a Pentarch IGN Read Against Janus Atlas

What is on the chart:

A Pentarch IGN prints at $50,000, on a closed bar
The nearest Janus Atlas level below it is the daily low at $49,850
The symbol's ATR at the time is $400

The measurement:

Distance from event to level: $50,000 minus $49,850, so $150
In the symbol's own units: $150 ÷ $400, so 0.38 ATR
The level sits below a bullish event, rather than above it

The reading:

An IGN sitting a third of an ATR above the nearest structural level
The same IGN with the nearest level three ATR away would be the same label describing a very different chart
Neither reading says what happens next. Both say where the event sat when it printed

✅ Day 6 Complete When You Can:

Measure the distance from any event to the nearest level without thinking about it
Convert that distance into ATR so it compares across symbols
Say which side of the event the level sits on, from memory, for your last five
Recognise an event in open space and say so rather than finding a level for it
Explain why two identical labels can describe very different charts

📅 Day 7: Keep a Reading Log¶

Goal: Record what the chart showed, before it shows the rest¶

Enable paper trading
Open a note, a spreadsheet, or a page in a notebook
One row per event, with columns for the date, the symbol and the timeframe
Anything that timestamps itself will do. The point is that it is written before, not after
Wait for an event
Wait for an alert to fire
Or find one that has just printed on a chart you follow
Record these three things about it:
- Which Pentarch event printed, and whether the bar had closed
- How far the nearest Janus Atlas level sat, in ATR
- What you expect the next few bars to look like, in one sentence
Write the first reading down
The event prints, or you find one that just did
Note the regime colour on that bar
Note the distance to the nearest level, in ATR
Note which side of the event that level sits on
Write the one-sentence expectation last, and do not change it afterwards
Screenshot the chart
Capture the bar the event printed on, before more bars arrive
Alongside it, record:
- Date and time
- Event type and whether the bar had closed
- Regime colour on that bar
- Nearest level, and its distance in ATR
- Which side of the event that level sits on
- Your one-sentence expectation
- How confident it felt, on a scale of one to five
Come back to it later
Look again after five bars, not sooner
Compare what happened against the sentence you wrote
Do not edit the sentence
Note in one line whether the reading described what followed, partly or not at all
Log 3 to 5 readings
Do not rush to fill the log
Finding five events worth a careful reading can take one to two weeks
Five careful readings are worth more than twenty hurried ones
Five is nowhere near a sample. It is enough to find out whether you are reading or remembering

✅ Day 7 Complete You have a log of readings written before the outcome, which is the only kind worth keeping.

🎯 Success Milestones Checklist

Track your progress as you master Signal Pilot indicators:

Day 1

Indicator loaded on TradingView
Chart displays correctly
Saved first layout
Can navigate chart history

Day 3

Can identify all 5 signal types
Understand signal colors/meanings
Observed signals on 3+ timeframes
Tested on different markets

Day 7

Observed 10+ historical signals
Can name the five events and the phase each marks, without assuming they arrive in that order
Set up working alerts
Seen 1-3 live signals (Daily chart)

Week 2

Read 30+ events so far, historical and live, on the way to fifty
Recognize level clusters (Janus)
Found 5+ events on a level cluster, and 5+ in open space
Can say how many sources a reading has before deciding what it means

Week 4

Seen 10+ live signals across timeframes
Completed 3-5 paper trades (quality > quantity)
Built personal trade journal
Settled on the timeframes you actually read, rather than all of them

Month 2-3

Pattern recognition automatic
Confident in confluence analysis
Built consistent strategy
Reading all seven indicators without checking the reference

Remember: Everyone progresses at different speeds. Don't rush - the goal is mastery, not speed. Some users need 4 weeks to be ready, others need 8-12 weeks. Both are perfectly normal!

Week 1 Reflection

Before moving to live trading, honestly assess your progress:

Can you identify all 5 Pentarch signals (TD, IGN, WRN, CAP, BDN) on any chart?
Have you successfully configured at least one alert with "Once Per Bar Close"?
Do you understand what confluence is, an event landing on a level rather than in open space?
Have you logged at least 3 readings that combine Pentarch and Janus Atlas?
Can you state the distance from an event to its nearest level, in ATR, without a calculator?

If yes to all 5: You're ready to graduate Week 1! Continue to the Graduation Checklist below.
If no to any: Repeat the relevant day. There's no rush - mastering the basics prevents costly mistakes later.

✅ Week 1 Graduation Checklist¶

Before moving to live trading, verify YES to all:

All YES? → You can read what these indicators show. What you do with that is your decision, taken on your own risk, and nothing on this page is advice about it.

Any NO? → Spend another week on paper trading and review

🎓 Next Steps: Weeks 2-4¶

Week 2-3: Consistency¶

Log 10 to 20 more readings
Count how often you wrote the expectation before the bars printed
Count how often the well supported readings looked different afterwards from the thin ones
Notice which check you skip most
Notice which indicator you reach for first, and whether that is habit or reason

Week 4: Transition Decision¶

After twenty or so readings, look back at the log: - Were the expectations written before the bars, or after - Did the well supported readings look different from the thin ones - Were the same checks skipped every time - Could a stranger reconstruct the chart from what you wrote

If the answer to the last one is no, the log is a diary rather than a record, and the fix is to write down the four things that make a reading rather than the one that made an impression.

If the answer is yes, you have something the indicators cannot give you: a description of how you read them, in your own hand, on your own charts. Where you take it from there is outside the scope of this documentation, and is your decision alone. See Best Practices for how other readers use the suite.

📚 Continued Learning Resources¶

Essential reading: - Analysis Workflow - Complete process - Best Practices - Pro tips - FAQ - Common questions - Troubleshooting - Fix issues

Advanced topics: - Comparison Guide - Add more indicators - Glossary - Deep term definitions - Education Portal - the written curriculum

← Back to Product Get Access →

Educational only. Trading involves substantial risk of loss. Not financial advice. Past performance does not guarantee future results.