Level 11 · Lesson 6
The Executive Summary
CIPHER's Priority Waterfall
17 conditions. One output. The header has already resolved every conflict in the Command Center before you finish reading the first row.
First — Why This Matters
The most watched cell in the Command Center is also the most misunderstood.
The CIPHER PRO header row — the always-on row at the top of the Command Center — is the only row that can never be turned off. It reads every other row simultaneously and outputs a single plain-English verdict: the single most important action on this bar. Not an average. Not a vote. The single highest-priority true condition from a 17-state cascade evaluated top to bottom.
Most operators glance at it, note the color, and move to the rows below to “verify.” This is backwards. The header is the synthesis. The rows are the evidence. When Momentum is teal and Tension is magenta and the header is amber, the header has already resolved that conflict using a deterministic priority system baked into the Pine source. You do not need to resolve it manually.
This lesson teaches you to read the header first, use the rows for nuance, and trust the cascade that CIPHER runs 17 conditions deep on every bar.
⭐ 01 — Groundbreaking Concept
The Single Most Urgent Truth
Every bar, CIPHER asks one question: what is the single most important thing this operator needs to know right now? Seventeen possible states compete for that slot. The first true condition in the priority cascade wins. Everything below it is blocked.
FROM THE CIPHER PRO HEADER TOOLTIP
“This row reads ALL intelligence below and shows the single most important action right now. Rows below are the evidence — they show different dimensions of the market (trend, energy, stretch, volatility). When rows show different colors, the header has already resolved the conflict for you. Green = go. Amber = caution. Red = danger.”
Five scenes from your actual Command Center. Watch the priority cascade list on the right: as each scene loads, the active priority lights up and all higher priorities dim as “blocked.” Scene 1: RIDE IT fires at priority 9 — priorities 1–8 are all false, spread is expanding and health is above 50. Scene 2: TREND CURVING fires at priority 6, blocking TREND AGING at 7 even though both are true. Scene 3: TREND AGING fires at 7 when CURVING is false. Scene 4: SNAP ZONE at priority 10 fires despite Momentum SURGING at priority 15 — tension outranks momentum. Scene 5: FADING fires in bright red at priority 11 — rows show mixed colors, header has resolved the conflict.
⭐ THE OPERATOR'S READ ORDER
1. Header action color — teal/amber/red/magenta tells you urgency before you read a word. 2. Header action text — the specific state tells you what to do. 3. Header state cell — the regime and direction context. 4. Evidence rows — for nuance and stop/size decisions. Never for overriding the header.
02 — The Header State Cell
Four states. Regime + direction in one cell.
The header's middle cell (col 2) is not the same as the Regime row's state cell. It combines regime classification with ribbon direction to give you a richer context label. There are exactly four possible outputs, each with its own color locked by CIPHER enforces this.
Watch the four states cycle. ▲ BULL TREND: TREND regime with pulse_dir = bull — teal, the most confident positive state. ▼ BEAR TREND: TREND regime with pulse_dir = bear — magenta, directional trend but against the bull bias. ⚡ VOLATILE: VOLATILE regime — magenta, the highest-risk state regardless of direction. ↔ RANGING: RANGE regime — amber, the undirectional state.
WHY BEAR TREND IS MAGENTA, NOT RED
Magenta in CIPHER means “bearish or volatile structural condition” — not danger-tier urgency (that is bright red #FF1744). A bearish trend is a valid market state with its own playbook. It is not a capital-risk signal. The distinction between magenta (structural) and bright red (danger) is precise and intentional.
THE DIRECTION DRIVER
Bull vs. bear in the header is driven by pulse_dir— the ribbon's directional state — not by the regime race or by ADX alone. A chart can show TREND regime (ADX-driven) with ▼ BEAR TREND if the ribbon is stacked bearish. The regime says “trending”; the direction says “which way.”
03 — The Color Grammar
Read the color before you read the word
The header action cell uses four distinct colors, each encoding an urgency tier. You should be able to identify the tier within one second of glancing at the header — before your brain has processed the text. This is the color grammar, locked by Pine line 3090.
Four tiers cycle. Teal is the go tier: RIDE IT, BREAKOUT ▲, ENTRY ZONE. Execute. Amber is the caution tier: AGING, CURVING, SNAP ZONE, COILING. Prepare. Bright red is the danger tier: FADING, EXIT SOON, REVERSAL NEAR. Protect capital. Magenta is the volatile/structural tier: REDUCE SIZE, BREAKOUT ▼, DOUBLE COIL. Regime-specific alert.
THE MAGENTA VS RED DISTINCTION
Magenta (#EF5350) and bright red (#FF1744) are two separate danger signals. Magenta = VOLATILE regime or bearish structural condition. Bright red = active health deterioration or imminent exit condition. A bright red header demands immediate capital protection action. A magenta header demands regime-appropriate caution (reduce size, widen stops). They are not interchangeable.
CYAN \u2014 THE FIFTH COLOR
There is a fifth color: cyan (#00BCD4), used exclusively for → BUILDING when TREND regime and momentum is in the BUILDING phase. It is distinct from teal — a lighter, more cautious positive. BUILDING means the trend is gaining energy but not yet at full RIDE IT strength.
04 — The Two-Cell Brief
Full operator context in two cells
The header's state cell and action cell together form the minimum viable CIPHER read. State tells you the market character; action tells you what to do about it right now. In a time-constrained situation — news event, fast market, mid-meeting — two cells deliver a complete, valid operator decision. The rows below add nuance for stop placement and sizing, but they do not change the core verdict.
Four brief combinations cycle, each drawn from real Command Center states. State cell gives you regime + direction. Action cell gives you the resolved verdict. The operator action box shows what that two-cell read implies in practice — no additional rows required.
THE READ ORDER IN PRACTICE
Step 1: Look at the action cell color. Teal = go, amber = prepare, red = protect, magenta = regime alert. Step 2: Read the action cell text. Confirms the specific condition. Step 3: Read the state cell for regime + direction context. Step 4: Scan evidence rows for stop distance and sizing nuance. Never use evidence rows to override the header.
WHEN THE HEADER IS WHITE/DIM
→ WAIT renders in dim white and is the cascade fallback — all 17 conditions above it are false on this bar. It is not a negative signal; it means the market has no urgent condition worth flagging. Stand by. Reduce activity until a colored state appears.
THE CONFLICT RESOLUTION GUARANTEE
When the rows below the header show different colors simultaneously — one teal, one amber, one red — that is not a problem to solve. It is information. The header has already processed all of it through the priority cascade and output the single most urgent truth. Your job is to read the header, not to re-run the cascade manually.
05 — Regime Gating
Some states can only fire in specific regimes
Not all 17 header states are available on every bar. Several are regime-gated — they can only output when a specific regime is active. This is hardcoded into the cascade conditions on The cascade logic, not a setting you control.
Three regime panels cycle. TREND unlocks RIDE IT, TREND AGING, TREND CURVING, TREND HOLLOWING, and BUILDING — five states that cannot fire in RANGE or VOLATILE. RANGE unlocks COILING (vol_ratio_atr < 0.8 in RANGE only) but blocks all five TREND states. VOLATILE has the narrowest unlocked set: REDUCE SIZE is its exclusive state and cannot fire in any other regime.
CROSS-REGIME STATES
Several states fire regardless of regime: SNAP ZONE (any regime, just requires tension > ts_min_tension), FADING (any regime, requires spread_contracting or health_critical), ENTRY ZONE and EXIT SOON (any regime, driven by mom_next). These are the “pure condition” states that the market can reach from any starting point.
WHY THIS MATTERS FOR READING
If you see → RIDE IT in the header, you already know the regime is TREND without reading the state cell — RIDE IT is impossible in RANGE or VOLATILE. Similarly, if you see → REDUCE SIZE, you know VOLATILE is active. The action cell encodes the regime implicitly for certain states.
06 — The Full Cascade, in Order
17 conditions. Top to bottom. First true wins.
The full cascade from The cascade logic, visualized as an animated waterfall. When the market bar closes, CIPHER evaluates each condition from priority 1 downward. The first condition that evaluates true immediately outputs its state and blocks all remaining conditions from being evaluated. The cascade stops at that point.
Three scenarios demonstrate different stopping points. When RIDE IT fires at priority 8, priorities 9–18 are never reached — even if their conditions are true. When the cascade reaches WAIT at the bottom, it means all 17 named conditions above it were false on this bar: no squeeze, no divergence, no projection convergence, no aging stack, no tension breach, no health deterioration, no momentum extreme. A quiet bar with no urgent signal.
THE FULL PRIORITY ORDER
1. BREAKOUT ▲/▼ → 2. BREAKOUT LOADING → 3. DOUBLE COIL → 4. TREND HOLLOWING → 5. TREND CURVING → 6. TREND AGING → 7. RIBBON COILED → 8. RIDE IT → 9. SNAP ZONE → 10. FADING → 11. BUILDING → 12. COILING → 13. REDUCE SIZE → 14. ENTRY ZONE → 15. EXIT SOON → 16. REVERSAL NEAR → 17. SNAP LIKELY → 18. WAIT
WHY BREAKOUT IS PRIORITY 1
A squeeze breakout is the highest-conviction event in CIPHER — compressed energy releasing directionally. When it fires, nothing else matters. The cascade opens with this check because any other signal during a live breakout is subordinate. Even TREND HOLLOWING (internal deterioration) is less urgent than a live squeeze releasing.
07 — RIDE IT — The Teal Signal
The most sought-after header state — and why it is rare
→ RIDE IT is the most unambiguous operator signal in CIPHER. Teal, priority 8, three simultaneous conditions required. When it appears, the cascade has already confirmed that no squeeze, no divergence, no coiling, no hollowing, no curving, and no aging override it. The trend is structurally clean and actively expanding.
Three scenarios. All three true — RIDE IT fires. Spread not expanding — blocked, cascade continues past priority 8. Health below 50 — blocked, cascade continues. The requirement that all three be true simultaneously is what makes RIDE IT relatively rare and highly reliable when it does appear. A trend with low ribbon health will never show RIDE IT regardless of how strong the trend looks on the candles.
THE THREE CONDITIONS
regime == "TREND"
AND spread_expanding // ribbon width actively growing
AND health_smooth > 50 // adaptive health above midpoint
WHAT TO DO ON RIDE IT
Run the TREND playbook at full conviction. Ride pullbacks to the Pulse or Flow line. Do not fade. Do not take early partials unless the Regime row is showing FORMING. RIDE IT means the trend is healthy, expanding, and not yet aging. It is the “stay in the trade” signal.
08 — Conflict Resolution in Practice
When rows disagree, the header has already decided
The most common operator confusion is seeing two rows with contradicting signals and trying to resolve them manually. The tooltip says it explicitly: “When rows show different colors, the header has already resolved the conflict for you.” The cascade ran all conditions on this bar and output the single highest-priority true one.
Three real conflict pairs cycle. Conflict 1: Tension warns (SNAP LIKELY) while Momentum surges (HOLD POSITION) — header outputs SNAP ZONE because tension at priority 9 outranks any momentum-derived state at priority 14+. Conflict 2: health failing while Momentum is strong — header outputs FADING (bright red) at priority 10. Conflict 3: CURVING and AGING both true simultaneously — header outputs CURVING because priority 5 beats priority 6.
THE RULE
Never manually average, vote, or synthesise conflicting rows. The header has already done this with a deterministic algorithm. Use the header action as the verdict. Use the conflicting rows as evidence for stop distance, position sizing, and risk management — not for overriding the verdict.
09 — The Operator Read Discipline
Four steps. Always in this order.
The header is designed to be read in a specific order that extracts maximum information in minimum time. This four-step discipline applies every time you open CIPHER — whether you have 2 seconds or 2 minutes.
Watch the highlight sweep through each step. Step 1: action cell color — urgency tier before you read a word. A teal header means you can proceed; a red header means stop and protect. Step 2: action cell text — the specific condition. Step 3: state cell — regime and direction context. Step 4: evidence rows — nuance for execution decisions. The evidence rows are step 4, not step 1.
THE 10-SECOND GLANCE READ
In a fast market: glance at the header action color (1 second). If teal — run your playbook. If amber — what specifically? (read text, 2 seconds). If red — protect capital now. Full four-step read takes 10 seconds once the discipline is installed. The goal is to reach step 4 (evidence rows) on every bar without skipping steps 1–3.
THE WAIT STATE
→ WAIT (dim white) is the cascade fallback. All 17 named conditions are false. This is not a negative signal — it means the market has no urgent condition worth flagging on this bar. Reduce activity. Wait for a colored action cell to appear before entering new positions. WAIT is information: the market has nothing urgent to say right now.
10 — TREND HOLLOWING vs TREND CURVING
Both amber. Very different warnings.
Two of the most misread amber states share a surface similarity — both appear during a TREND regime and both are amber. But their causes and implications are completely different, and their priorities reflect that: → TREND HOLLOWING sits at priority 4, → TREND CURVING at priority 6. When both are true simultaneously, HOLLOWING wins because it is the more urgent condition.
Panels alternate highlight. TREND HOLLOWING fires when rd_active is true — the ribbon divergence detector has identified that price is making a new structural extreme while the ribbon's internal spread is weakening. The trend is dying from inside before the candles show it. This is the most valuable early warning in CIPHER. TREND CURVING fires when proj_converging is true — the ribbon's projected trajectory is bending back. Not yet deteriorating; just losing momentum. Two bars of difference in urgency.
THE OPERATOR DIFFERENCE
HOLLOWING: tighten stops immediately, no new entries in trend direction, watch for SHIFTING. CURVING: tighten stops, watch for escalation to HOLLOWING, can still ride existing position. The word “hollowing” means the interior structure is failing — even if the outside looks fine.
11 — FADING vs REDUCE SIZE
Two danger colors. Two different crises.
The two non-amber danger states are the most commonly confused pair in the Command Center. → FADING renders in bright red (#FF1744) and means the ribbon engine's internal health or spread is failing. → REDUCE SIZE renders in magenta (#EF5350) and means the VOLATILE regime is active. Same urgency tier visually, completely different causes and playbooks.
FADING fires in any regime when spread_contracting or health_critical is true. It is a ribbon health signal, not a regime signal. A ranging market with a failing ribbon produces bright red FADING. REDUCE SIZE fires only in VOLATILE regime — a pure regime gate. The color difference encodes this: bright red = active health crisis, magenta = structural/regime condition.
FADING PLAYBOOK
Stop all new entries. If you have open positions, tighten stops or close. The ribbon is losing the energy required to sustain any directional move. FADING in a TREND regime often precedes a regime flip to RANGE.
REDUCE SIZE PLAYBOOK
VOLATILE regime is active — ATR has spiked above 1.5× ATR_slow. Reduce position size 50–100%. Do not fade the spike. Do not run the RANGE mean-reversion playbook. Wait for VOLATILE to resolve before new standard entries.
12 — The Header in Full Context
Five real states from your Command Center
The header always sits above the evidence rows. Each of the five states below is drawn from a real screenshot of CIPHER PRO in a live session. Watch how the header action cell changes as market conditions shift — and notice how the evidence rows below sometimes show mixed colors while the header has already resolved the single most important verdict.
Scene 1 (RIDE IT): all rows teal, perfect alignment, full conviction trade. Scene 2 (TREND CURVING): Ribbon amber, Momentum magenta, Regime amber — three different conditions, header picks CURVING at priority 6. Scene 3 (TREND AGING): similar to scene 2 but proj_converging is false this bar, so stack_aging at priority 7 fires instead. Scene 4 (SNAP ZONE): Tension magenta warning vs Momentum teal surge — header picks tension. Scene 5 (FADING): Ribbon magenta, Momentum teal, Regime amber — header fires bright red FADING at priority 11. Mixed rows, resolved verdict.
13 — The WAIT State
When the cascade has nothing to report
→ WAIT is the cascade fallback. It appears in dim white when all 17 named conditions above it evaluate false on this bar. No squeeze, no divergence, no projection convergence, no aging, no coiling, no tension breach, no health failure, no momentum extreme. The market is quiet enough that the Priority Waterfall has nothing urgent to report.
The animation shows the cascade with all conditions struck through as false, ending at WAIT in dim pulsing white. WAIT is not a bearish signal and not a malfunction. It is the absence of urgency — the market equivalent of a quiet room. When you see WAIT, reduce activity, avoid new entries until a colored action cell appears, and use the time to study the evidence rows for setup preparation.
WAIT IS INFORMATION
A market that consistently produces WAIT has no squeeze building, no divergence, no tension, no aging trend. It is genuinely undecided and unexciting. This is the correct time to stand aside. When WAIT flips to any colored state, the cascade has found the first true condition — that is your signal to re-engage.
14 — Six Common Mistakes
The Narrative Reader Operator's error log
These are the six errors operators make when reading the Executive Summary row.
MISTAKE 01 — Reading the evidence rows before the header
The header is the synthesis; the rows are the evidence. Starting with rows and working up to the header is backwards. The cascade has already processed all rows. Read header first: color, then text, then state. Rows are step 4.
MISTAKE 02 — Trying to manually override the header with a majority vote from rows
If Momentum is teal, Tension is amber, and Volume is amber, that is not "2 against 1 = amber." The header runs a priority cascade, not a vote. One high-priority condition can fire over multiple lower-priority conditions. Trust the cascade.
MISTAKE 03 — Confusing FADING (bright red) with REDUCE SIZE (magenta)
Two different colors, two different crises. Bright red = ribbon health or spread failing (any regime). Magenta = VOLATILE regime active. The playbooks are different. The color tells you which crisis you are in before you read the word.
MISTAKE 04 — Assuming TREND CURVING and TREND AGING are the same signal
Both amber, both in TREND. But CURVING (priority 6) means the projection is bending back. AGING (priority 7) means the stack has outlasted its historical average. CURVING is an earlier, more structural warning than AGING. When CURVING appears, AGING is blocked.
MISTAKE 05 — Treating WAIT as a bearish signal
WAIT means all 17 named conditions above it are false on this bar. The market has nothing urgent. It is not bearish — it is quiet. Standing aside during WAIT is correct. Forcing trades during WAIT is how operators manufacture setups that are not there.
MISTAKE 06 — Missing regime-gated states because you are on the wrong regime
RIDE IT requires TREND regime. COILING requires RANGE. REDUCE SIZE requires VOLATILE. If you are expecting RIDE IT but the regime is RANGE, it cannot appear. The cascade will never output a regime-gated state when that regime is inactive, regardless of how strong the other conditions are.
15 — Cheat Sheet
Narrative Reader Operator reference
COLOR GRAMMAR
Teal — Go: RIDE IT · BREAKOUT ▲ · ENTRY ZONE
Amber — Caution: AGING · CURVING · HOLLOWING · SNAP ZONE · COILING · BREAKOUT LOADING
Bright Red #FF1744 — Danger: FADING · EXIT SOON · REVERSAL NEAR
Magenta #EF5350 — Volatile/Structural: REDUCE SIZE · BREAKOUT ▼ · DOUBLE COIL
Cyan #00BCD4 — Building: BUILDING (TREND + mom_now BUILDING only)
FULL PRIORITY ORDER
1 BREAKOUT → 2 BREAKOUT LOADING → 3 DOUBLE COIL → 4 TREND HOLLOWING → 5 TREND CURVING → 6 TREND AGING → 7 RIBBON COILED → 8 RIDE IT → 9 SNAP ZONE → 10 FADING → 11 BUILDING → 12 COILING → 13 REDUCE SIZE → 14 ENTRY ZONE → 15 EXIT SOON → 16 REVERSAL NEAR → 17 SNAP LIKELY → WAIT
REGIME-GATED STATES
TREND only: RIDE IT · TREND AGING · TREND CURVING · TREND HOLLOWING · BUILDING
RANGE only: COILING (vol_ratio_atr < 0.8)
VOLATILE only: REDUCE SIZE
Any regime: SNAP ZONE · FADING · ENTRY ZONE · EXIT SOON · REVERSAL NEAR
RIDE IT CONDITIONS
regime == "TREND" AND spread_expanding AND health_smooth > 50
All three must be simultaneously true. Priority 8.
FOUR-STEP READ ORDER
1. Action color (urgency tier) → 2. Action text (specific condition) → 3. State cell (regime + direction) → 4. Evidence rows (stop & sizing nuance). Never rows before header.
HEADER STATE CELL (col 2)
▲ BULL TREND — TREND + pulse_dir bull
▼ BEAR TREND — TREND + pulse_dir bear
⚡ VOLATILE — VOLATILE regime
↔ RANGING — RANGE regime
16 — Scenario Game
Read the Header Like an Operator
Five scenarios. Each puts you in a real-feeling header-reading situation. Pick the right call — explanations appear after every answer, including wrong ones.
Round 1 of 5
Score: 0/5
EURUSD 1H. The header reads: ▲ BULL TREND | → TREND CURVING (amber). Below it, the Regime row shows TREND | → TREND AGING (amber). Both amber. You were about to act on the Regime row’s AGING signal.
Why does the header show TREND CURVING instead of TREND AGING even though both conditions are true?
17 — Knowledge Check
Final Quiz — 8 Questions
Question 1 of 8
The header action cell in CIPHER PRO evaluates conditions in what order?
Question 2 of 8
What is the header action cell’s highest-priority state (first in the cascade)?
Question 3 of 8
What color does → FADING render in the header action cell?
Question 4 of 8
The header state cell (col 2) shows ⇔ RANGING. What color does it render in?
Question 5 of 8
→ RIDE IT requires which conditions to fire ()?
Question 6 of 8
You see ⇔ RANGING in the header state cell and → FADING in red in the action cell. What does this combined read tell you?
Question 7 of 8
Which header action state is regime-gated to VOLATILE only?
Question 8 of 8
The CIPHER PRO header tooltip says: "When rows show different colors, the header has already resolved the conflict for you." What does this mean operationally?