Pentarch v1.0
Advanced Learning Guide
Master 5 Cycle Events • Reading Discipline • Decision Trees • Beginner Traps
⏱️ Reading Time: 18 minutes
🚀 Understanding Pentarch's 5-Cycle Event System
What Makes Pentarch Different
Pentarch's Unique Approach
Pentarch uses a 4-layer detection system to identify 5 distinct market cycle phases through specific events. It doesn't count candles or bars: it detects when complete cycle phase conditions are met.
The 5 Cycle Events:
- 🟣 TD (Touchdown) : Accumulation phase signal
What it means: Price extended below trend, oversold conditions detected - 🩵 IGN (Ignition) : Markup phase signal
What it means: Momentum breakout conditions met, bullish structure shift - 🟡 WRN (Warning) : Distribution phase signal
What it means: Price extended above trend, overbought regime present - 🟠 CAP (Climax) : Climax phase signal
What it means: Extreme extension detected, late-cycle exhaustion - 🔴 BDN (Breakdown) : Decline phase signal
What it means: Bearish structure break confirmed, decline phase beginning
Example: Full Cycle Pattern
- SPY drops from $460 to $445 → TD appears (accumulation phase)
- Price rallies to $450 → IGN appears (markup beginning)
- Price reaches $465 → WRN appears (distribution phase)
- Price pushes to $470 → CAP appears (climax exhaustion)
- Price breaks down to $460 → BDN appears (decline phase)
Not every cycle shows all 5 events. You might see partial patterns like TD → IGN (early cycle only) or WRN → CAP (late cycle only).
📋 The 5-4-3 Rule for Pentarch
Memorize This Framework
5 Cycle Events to Know:
- ✅ TD = Accumulation phase (downside exhaustion)
- ✅ IGN = Markup phase (bullish momentum beginning)
- ✅ WRN = Distribution phase (upside extension)
- ✅ CAP = Climax phase (extreme exhaustion)
- ✅ BDN = Decline phase (bearish structure break)
4 Detection Layers (All Must Confirm):
- ✅ Layer 1: Regime classification (bullish/bearish/neutral)
- ✅ Layer 2: Pilot Line distance (price extension from trend)
- ✅ Layer 3: the NanoFlow micro-trend crosses agree with the direction
- ✅ Layer 4: Bar close confirmation (all conditions hold at close)
3 Things to NEVER Do:
- ❌ Never read a bar that has not closed (events confirm at bar close only)
- ❌ Never re-tune after three readings (three is a run, not a measurement)
- ❌ Never ignore higher timeframe context (the event is smaller than the trend around it)
📌 Golden Rule: All 4 layers must confirm at bar close before signal appears.
Pentarch uses strict multi-layer validation, so an event on screen is a condition that held on all four layers at bar close.
🧠 Reading Discipline: When Several Readings Do Not Hold
💔 Challenge 1: Three Readings in a Row That Did Not Hold
What Happens: Three Pentarch events in a row, and on each one the chart goes on to do something the reading did not describe. A TD, then an IGN, then a WRN. The doubt arrives in a fixed order:
- "Does this indicator actually work?"
- "Did I configure something wrong?"
- "Is everyone else seeing something I am not?"
- "Should I change the settings? Try different timeframes?"
These questions are normal. Acting on them after three readings is the part that costs you, because three readings cannot tell them apart.
How long a run has to be before it means anything:
| Share of readings that hold | Chance of three in a row not holding | So it turns up roughly |
|---|---|---|
| 6 in 10 | 6.4% | once in every 15 to 16 readings |
| 5 in 10 | 12.5% | once in every 8 readings |
| 4 in 10 | 21.6% | once in every 4 to 5 readings |
What that table is for: whatever share of your own readings hold, the run of three you just met sits inside the range that same share produces on its own. It is arithmetic about sequences, not a figure about Pentarch. We publish no accuracy figures for Pentarch, and the numbers above are not one.
What to do with the three readings:
- Leave the chart for a day. Close TradingView. A chart you go back to hourly will hand you a fourth reading built out of the first three
- Write the three down before you judge them. For each one: which event printed, on which bar, and what the four layers said at close. Do this from the chart, not from your memory of how it felt
- Separate the reading from the outcome. For each of the three, note the regime, the distance from the Pilot Line, and whether the higher timeframe agreed. Three thin readings that did not hold is a different case from three well supported ones that did not, and only one of the two is about the indicator
- Go back to reading before you change anything. Spend a week marking events and writing down, before the following bars print, what you expect them to look like. That rebuilds the skill the run shook, which is reading, and it changes no settings while it does
Worth writing at the top of the log: "Three in a row is a run, not a measurement. I write the three down, then read for a week before I change anything."
😰 Challenge 2: Reading an Event Hours After It Printed ("I Missed the IGN!")
What Happens: An IGN prints at $50 while you are away from the desk. You open the chart three hours later and price is $53, six percent above the event bar. The reaction runs in a fixed order:
- Regret: "Why wasn't I watching?!"
- Urgency: "It's going to $60, I should be reading this now!"
- Rationalisation: "It's still early in the move, right?"
- The arithmetic: the gap between the event bar and the current price is now most of the move the event described
- The pullback: price is back at $51 the next day, and the event bar sits well below it
- Frustration: "Of course it turns the moment I look"
What the chart is actually telling you:
- The event has an age, and the age is on screen. An IGN three hours old describes a condition from three hours ago. That is not a worse reading, it is a reading about a different bar
- Distance from the event bar is the honest measure. Once price has travelled a large part of what the event described, the reading it supports is "this already happened", not "this is starting"
- The next event is a new reading. Pentarch keeps marking the cycle, so a later WRN or CAP is the same instrument revising itself, on a bar you can actually watch close
- Set alerts so the next one arrives on time. TradingView alerts on "Once Per Bar Close" for every Pentarch event put the reading in front of you at the moment it becomes readable
Worth writing at the top of the log: "I read this one late. The event describes its own bar, not this one. The next event is the next reading."
🌳 How Much Support Does This Reading Have?
┌──────────────────────────────────────────────────┐
│ PENTARCH EVENT PRINTS (TD, IGN, WRN, CAP or BDN) │
└───────┬──────────────────────────────────────────┘
│
▼
┌───────────────────────────┐
│ Has the bar closed, or │
│ is it still forming? │
└──┬──────────────────┬─────┘
│ │
STILL FORMING CLOSED
│ │
▼ ▼
Not a reading yet Read on
│
▼
┌──────────────────────────────┐
│ Confluence: Janus level, │
│ volume, Pilot Line distance? │
└──┬─────────────┬─────────────┘
│ │
0-1 of 3 2 or 3
│ │
▼ ▼
Thin reading Read on
│
▼
┌────────────────────────────┐
│ Higher timeframe agrees? │
└──┬───────────────────┬─────┘
│ │
NO YES
│ │
▼ ▼
Conflicted reading Read on
│
▼
┌───────────────────────┐
│ Regime and the event │
│ point the same way? │
└──┬──────────────┬─────┘
│ │
NO YES
│ │
▼ ▼
Mixed reading Well supported reading
✅ A Reading Log for Your First Ten Events
Write the reading down before the next bars print
For each event, record what the chart showed:
Event #_____ (Date: ______) Type: _______
- ☐ Event type (TD, IGN, WRN, CAP or BDN)
- ☐ Bar had closed when the label appeared
- ☐ All four layers confirmed (regime, distance, momentum, close)
- ☐ Higher timeframe agreed, disagreed, or was flat
- ☐ Confluence present (Janus level, volume, or Pilot Line distance)
- ☐ Regime colour on the bar the event printed on
- ☐ What you expected the next few bars to look like
After ten events, read the log back:
- Did the well supported readings look different afterwards from the thin ones? _______
- Which of the four layers did you skip checking most often? _______________
- Which event type did you find hardest to read? ___________
- Did you write the expectation before the bars printed, or after? Y / N
What the log is for: ten events is nowhere near a sample you can draw a conclusion from, and it is not meant to be one. It is a record of whether you are reading the chart or remembering it, which is worth knowing before anything else matters.
🚫 Top 5 Beginner Mistakes That Kill Pentarch Traders
Mistake #1: Not Waiting for Bar Close ⚠️ critical
What Happens: An IGN looks like it is forming mid-bar at 2:30 PM on a 1-hour chart. You read it there and then and write it down. By 3:00 PM bar close the conditions no longer hold, and IGN never prints. The reading you recorded describes a chart that did not happen.
Why Wrong: Pentarch requires ALL 4 layers to confirm at bar CLOSE. What looks like a signal at 50% bar completion can disappear by 100% completion. Entry before bar close = guessing, not signal-based trading.
The Fix:
- Set alerts to "Once Per Bar CLOSE" (not "Once Per Bar")
- Wait for bar to 100% close before entry
- If signal appears at 4:00 PM bar close, entry at 4:01 PM is fine
- On 1H chart: Wait for :00 close (9:00, 10:00, 11:00, etc.)
Exception: None. Always wait for bar close. No exceptions.
Mistake #2: Treating Events as Immediate Action Triggers
What Happens: TD event appears. You act immediately without checking anything else. Analysis fails because you didn't verify confluence, higher timeframe alignment, or proper context.
Why Wrong: Pentarch events show cycle PHASE identification, not precise entry timing. A TD event means "accumulation phase conditions detected," not "buy right now at market price." You still need confluence confirmation.
The Fix:
- Understand events identify PHASES, not exact entry points
- Always check confluence: Janus levels, volume, Pilot Line distance
- Verify higher timeframe trend alignment
- Wait for proper entry setup (pullback, structure break, etc.)
- Use events as "phase awareness" + look for tactical entries within that phase
Mistake #3: Ignoring Higher Timeframe Context
What Happens: An IGN prints on the 15-minute chart and you read it on its own. The daily chart is in a strong downtrend, which you never opened. Price continues lower, and the 15-minute event was a countertrend reading the whole time.
Why Wrong: Cycle events are more reliable when aligned with higher timeframe trend. Counter-trend signals fail more often than aligned ones. Track the two separately in your own journal and you will see the gap yourself.
The Fix - Required Timeframe Checks:
- 15m chart: Check 1H trend alignment
- 1H chart: Check 4H or Daily trend alignment
- 4H chart: Check Daily or Weekly trend alignment
- Daily chart: Check Weekly trend alignment
If the higher timeframe points the other way, that is a conflicted reading, and it is worth writing down as one rather than resolving it in the event's favour.
Mistake #4: Reading an Event Without Its Context
What Happens: A TD prints and the reading stops there. No Janus level checked. No volume checked. No Pilot Line distance measured. What you have written down is the label, not the reading.
Why Wrong: The label is one layer. The three checks below are three more, and each one either agrees with the event or does not. A reading built on one layer and a reading built on four look identical on the chart and say very different things.
The Fix - Required Confluence Checks:
- Janus Level Within 1%: Is there support/resistance within 1% of current price?
- Volume spike: is the Volume Oracle spike threshold met, a z-score of 2.0 by default?
- Pilot Line Distance: Is price significantly extended from Pilot Line?
Two of the three agreeing is two sources. All three agreeing is three, and that is the most the chart can show.
Mistake #5: Reading the Label Instead of the Chart
What Happens: a CAP prints. You read the word Climax, decide the top is in, and stop looking. You never check what the regime says, how far price sits from the Pilot Line, or whether the weekly chart is doing anything at all. The label has become the entire reading.
Why Wrong: the label is the output of four layers, not a substitute for them. Two CAPs on the same symbol can sit in completely different contexts, one at the end of an extended run in a bullish regime with the weekly stretched, the other mid-range in a flat regime with nothing behind it. The word on the chart is identical. The reading is not.
What to look at instead, every time a label appears:
- The regime colour on that bar, which says whether the event agrees with its own context or argues with it
- The distance from the Pilot Line, which is how extended price was when the event printed
- The higher timeframe, which is the fastest way to find out you are reading a countertrend event
- What else is on the chart at that price, whether a level, a volume shelf, or nothing
Four checks, about thirty seconds. The label tells you an event was detected. These tell you what kind of chart detected it.
❓ Top 10 Questions from New Users
Quick Answers to Common Confusion
Q1: A TD appeared. Is the reading finished?
A: Not yet. Three things are still outstanding: (1) has the bar closed, (2) is there confluence from a Janus level or from volume, (3) does the higher timeframe agree. TD reports an accumulation phase it detected. It does not report a reversal.
Q2: What's the difference between TD and IGN?
A: TD = Accumulation phase (downside exhaustion, oversold). IGN = Markup phase (bullish momentum beginning, structure shift). TD often precedes IGN in full cycle pattern.
Q3: Three readings in a row did not hold. Is the indicator broken?
A: Three readings cannot answer that. A sequence where six readings in ten hold still produces three misses in a row about once in every 15 to 16, purely from how sequences work. Write the three down, check whether each was well supported or thin, and read for a week before changing anything.
Q4: What does a TD mean inside a choppy range?
A: Less than the same TD after an extended move. The event detects downside exhaustion, and inside a range there was no extended move to be exhausted by. The reading is thin, and the chart says so through the Pilot Line distance.
Q5: How do I know if all 4 layers confirmed?
A: If the event appears on your chart at bar close, all 4 layers confirmed. Pentarch does not print an event unless all layers align, which is what the validation is for.
Q6: What timeframes work best for Pentarch?
A: All timeframes from 15m to Daily work. For beginners: Daily/4H charts (clearest patterns, fewest false signals). Advanced: 1H/15m (more signals, requires stricter filtering).
Q7: Does Pentarch mark exact tops and bottoms?
A: No. It reports which cycle phase it detected: accumulation, markup, distribution, climax or decline. That tells you where in the cycle the chart is, not where the extreme will be.
Q8: Is every event worth a close reading?
A: The question is really about how many events are worth a close reading, and the answer is fewer than print. A well supported reading needs bar close confirmation, higher timeframe agreement, confluence from a level or from volume, and a regime that agrees with the event. On most charts, four or five events in every ten fail at least one of those, and knowing which is the reading.
Q9: An IGN printed and price went nowhere. What did the event actually say?
A: That the markup-phase conditions were met on that bar. Everything outside the indicator, from news to higher timeframe resistance to thin volume, sits outside what it measures. Confluence and context are how you tell a well supported IGN from a bare one.
Q10: My own tracked results are worse than I expected. Where do I look first?
A: At the readings, before anything else, and in this order. Were the events read after the bar closed, or while it was still forming? Was confluence checked, or assumed? Did the higher timeframe agree, or was it never opened? Was the regime colour on the event bar noted at the time? Those four are where a reading goes wrong, and they are the only part of the process this indicator is involved in.
📄 Printable Quick Reference Cheat Sheet
┌───────────────────────────────────────────────────────────────┐
│ PENTARCH (5 CYCLE EVENTS) QUICK REFERENCE │
│ (Save or Print This) │
├───────────────────────────────────────────────────────────────┤
│ │
│ 📊 THE 5 CYCLE EVENTS: │
│ 🟣 TD (Touchdown) = accumulation phase │
│ 🩵 IGN (Ignition) = markup phase │
│ 🟡 WRN (Warning) = distribution phase │
│ 🟠 CAP (Climax) = climax phase │
│ 🔴 BDN (Breakdown) = decline phase │
│ │
│ ✅ A WELL SUPPORTED READING: │
│ • Bar closed (not mid-bar) │
│ • 4 layers confirmed (regime, distance, momentum, close) │
│ • Higher timeframe agrees │
│ • Confluence present (Janus level, volume, or distance) │
│ • Regime colour agrees with the event │
│ │
│ ⚠️ A THIN READING: │
│ • Mid-bar (the bar has not closed yet) │
│ • It runs counter to the higher timeframe │
│ • No confluence (an isolated label) │
│ • Regime colour argues with the event │
│ │
│ 📍 WHAT THE LABEL FIXES: │
│ The bar: the event belongs to the bar it printed on │
│ The price: the event bar's own high and low │
│ Neither moves afterwards, which is what makes a │
│ reading you took last month worth comparing today │
│ │
│ ⏱️ TIMING: │
│ • Wait for the bar to close (required) │
│ • All 4 layers must confirm at the same time │
│ • Do not read ahead of the close (the bar can change) │
│ │
│ 🎓 THE 5-4-3 RULE: │
│ 5 events: TD, IGN, WRN, CAP, BDN │
│ 4 layers: regime, distance, momentum, close │
│ 3 never: mid-bar, re-tune after 3, ignore the HTF │
│ │
│ 📈 WHAT A RUN OF MISSES MEANS: │
│ • We publish no accuracy figures: track your own │
│ • 3 in a row turns up about every 16 readings │
│ • A run is a run, not a measurement │
│ • Read 50 events or more before judging anything │
│ │
│ 🧠 AFTER SEVERAL READINGS DO NOT HOLD: │
│ Once three in a row have missed: │
│ 1. Leave the chart for a day │
│ 2. Read the last 10 back against the checklist │
│ 3. Well supported on 9 of the 10? Keep reading │
│ 4. Well supported on fewer than 7? Fix the reading │
│ │
└───────────────────────────────────────────────────────────────┘
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 identify TD, IGN, WRN, CAP, BDN signals
- ✅ You understand the 5 cycle phases (accumulation → decline)
- ✅ You wait for bar close before reading anything
- ✅ You understand 4-layer detection system
- ✅ You know a run of 3 misses says nothing on its own
📅 Week 2-4: Reading Phase
- ✅ You wait for bar close without having to remind yourself
- ✅ You check higher TF alignment on every reading
- ✅ You're comfortable leaving four or five signals in every ten unread (filtering)
- ✅ You don't re-tune the settings after 2 or 3 readings miss
- ✅ You're judging what you see over fifty readings, not five
📅 Month 2+: Mastery Phase
- ✅ Your readings stop swinging week to week and settle into a steady standard
- ✅ You understand runs (3 misses in 16 readings is ordinary)
- ✅ You're combining Pentarch with Janus, Volume, Harmonic for confluence
- ✅ You can tell an event with confluence behind it from the same event alone
- ✅ You come back from a run of misses without it costing you days
- ✅ You recognize full cycle patterns (TD → IGN → WRN → CAP → BDN)
🚨 Warning Signs (You Need to Review the Guide):
- ❌ You're reading unclosed bars regularly
- ❌ You changed the settings after 3 to 5 readings missed
- ❌ You don't understand the 5 cycle events (TD, IGN, WRN, CAP, BDN)
- ❌ You're not checking higher TF alignment
- ❌ You're reading every signal the same way, without filtering
- ❌ Your readings are still thin across more than fifty events
Remember: Pentarch is a 5-event cycle detection system using 4-layer validation. It identifies market phases (accumulation, markup, distribution, climax, decline), not exact reversals. Wait for bar close confirmation, where all 4 layers must align. A run of three misses is ordinary and tells you nothing on its own. Read in order, check for confluence, and give any judgement about the indicator at least fifty events to stand on.
🔗 Synergy: Pairing Pentarch with Other Indicators
🎯 High Synergy Combinations ("The Trinity")
- + Janus Atlas: Pentarch cycle events + level clusters = precise timing at key support/resistance. You know WHICH phase you're in (Pentarch) and WHERE price may react (Janus).
- + Volume Oracle: Pentarch signals + regime confirmation = volume-confirmed cycle phase transitions. Ensure volume is confirming (Volume Oracle) when cycles shift (Pentarch).
- + Harmonic Oscillator: A Pentarch event with an oscillator consensus is a cycle reading and a momentum reading on the same bar. Two sources rather than one.
🎲 Common Trading Combinations
- Pentarch TD + Janus support cluster → Accumulation phase signal at tested level
- Pentarch WRN + Volume Oracle Flow red → Distribution phase with selling pressure confirmation
- Pentarch IGN + Harmonic bullish consensus → Markup phase with momentum confirmation
- Pentarch CAP + Janus resistance cluster → Climax phase at key resistance zone
💡 Why These Pair Well
Pentarch provides cycle phase identification (WHEN and WHICH phase). Janus adds WHERE price may react (levels). Volume Oracle confirms WHO is acting (institutions). Harmonic confirms momentum state.
Reading cycle phases (Pentarch) alongside levels (Janus), volume (Volume Oracle) and momentum (Harmonic) is four sources describing one bar: the right phase, at the right price, with the right participants, at the right momentum state.
📚 Related Learning Guides
Continue your trading education with these complementary guides:
- OmniDeck Learning Guide : Master multi-system trading, the 3-2-1 rule, and avoid analysis paralysis when combining multiple indicators
- Harmonic Oscillator Learning Guide : Understand 7-oscillator voting consensus, divergence psychology, and overbought/oversold strategies
- Janus Atlas Learning Guide : Learn level cluster identification, bounce vs break patterns, and support/resistance strategies
- Volume Oracle Learning Guide : Master volume flow analysis, regime detection, and institutional participation signals
Educational only. Trading involves substantial risk of loss. Not financial advice. Past performance does not guarantee future results.