Scanner

Setups

Bullish and bearish scenarios from each security's preferred daily wave count: the reference level, where the count is invalidated, and the structural target. Each is checked for sane levels before it is shown.

Track record

220 setups69 held back by level checks

Ticker	Company	Setup	Close	Reference	Invalidation	Structural target	R : R	History	Risk	Conf.	Weekly	$ volume (20d)
RBRK	Rubrik, Inc. Class A	BearishCorrection complete· Intermediate	112.41	112.41	127.90	74.97	2.4	Negative recordhistory 18% · −0.29R	13.8%	70	Against	$339.5M
LYV	Live Nation Entertainment, Inc.	BearishCorrection complete· Intermediate	170.51	170.51	189.25	149.75	1.1

Page 3 of 5Previous Next

NoteResearch scenario generated from Viridia's structural model. Not a recommendation.ChecksA scenario is shown only if its reference level is within 30% of price, its invalidation within 25% and 8 ATR, its target within 100% and 25 ATR, reward/risk reconciles and sits between 1 and 10, the analysis is current, and the history shows no recent split-like jump.MethodA setup restates the preferred count as a trade: the entry (the close, or the level where the correction in progress most often ends), the stop where the count is wrong (a rule level, or the end of a finished pattern), and the count's own Fibonacci target. Reward:risk is measured from the middle of the entry range. A setup needs reward:risk of at least 1 : 1. It is research output from the wave count, not a recommendation or a forecast.Track recordEach setup kind and side is graded from its replayed trials, split at the median trial date so the two halves test each other out of sample. Positive: average at least +0.05R overall and above zero in both halves. Negative: at most −0.05R overall and below zero in both halves. Mixed: anything else. Little history: under 100 resolved cases or under 40 in either half. The replay covers a year in which U.S. stocks mostly rose, which favors bullish setups. The default order ranks by the kind's replayed average result, then Pattern Confidence.DegreeEach security's setup comes from its preferred count at intermediate degree (primary, then minor, when intermediate has none).