CyGuru Indicator
Does the structural setup agree with the confirmed higher-timeframe context?
The research profile
The registry describes an adaptive structure, sweep and pullback model. The v3.3 research profile adds confirmed 1H alignment, quality and volatility filters. The existing engine identifier is retained for routing; a version label alone does not prove that an alert was recreated with the latest script.
What to review
Identify the Pine version and alert configuration, then retain the original levels, creation time and evaluation deadline. Distinguish an initial proposal from a later activation report. Compare conflicting setups using the same source window.
Evidence and limits
The linked case preserves the production event trail and site collector ranges. Matching independent OHLC and broker execution are unverified. A quiet feed is not evidence of disconnection or proof that filtering improves results.
Registry and available archive reviewed 7 November 2026. A registered contract does not confirm the user’s current TradingView alert configuration. These pages describe implemented research profiles; no proprietary formula or current performance statistic is inferred.
Preserved event timelines
No preserved native-event trail is linked for this indicator yet. Source captures in a case article retain their own evidence classification.
Selected published articles
When the Reference Entry Came Before the Activation ReportSelected reported TP3 · frozen original levels · collector replay · broker execution unverifiedContinue the investigation
Engine identity and integration
CYGURU-INDICATOR-3.2-RC1The identifier connects this profile with its own signal history. Custom Pine runs in TradingView; the hosted chart supplies a separate market view.
Supported alert contract →