11 NOVEMBER 2026 · CYGURU INDICATOR · 15M SELL · TREND
When the Reference Entry Came Before the Activation Report
A fifteen-minute CyGuru Indicator TREND SELL reported activation at noon UTC on 11 November. The retained one-minute range had already crossed its reference entry. The distinction matters when reading the TP3 sequence and deciding what the terminal can establish.
Open CyGuru Gold Terminal to inspect signal plans and lifecycle events →
The production evidence
This selected favorable example is an indicator-reported reference observation. The production gateway retained a separate activation report and an actual TP3_HIT with the same signal identity. Engine CYGURU-INDICATOR-3.2-RC1, payload schema 1, OANDA:XAUUSD, 15-minute timeframe, SELL and TREND were recorded. A separate script build hash was unavailable.
Signal ID CYGURU-INDICATOR-3.2-RC1|OANDA:XAUUSD|15|1794397500000
TP3 event ID CYGURU-INDICATOR-3.2-RC1|OANDA:XAUUSD|15|1794397500000|1794404700000|TARGET
Production feed observed through .
All 5 production messages retained the same original Entry, SL and three targets, along with the same creation and expiry timestamps and setup fields. The event trail contains no earlier stop or invalidation for this identity. The receiver timestamps below come from the matching stored rows.
| Field | Level | Distance | Original risk multiple |
|---|---|---|---|
| Entry | 4050.022 | — | — |
| Original SL | 4055.029 | 5.007 adverse | 1.000R |
| TP1 | 4044.340 | 5.682 favorable | 1.135R |
| TP2 | 4039.815 | 10.207 favorable | 2.039R |
| TP3 | 4033.494 | 16.528 favorable | 3.301R |
One reference R is the absolute distance from the original entry to the original stop. Each target multiple divides the distance from entry by that fixed denominator. The ratios describe the proposal’s price levels. Broker fills, commissions, spread, slippage and P&L are unverified.
| Recorded stage | Source time | Receiver time |
|---|---|---|
| SIGNAL_CREATED | ||
| SIGNAL_UPDATED · activation | ||
| TP1_HIT | ||
| TP2_HIT | ||
| TP3_HIT |
Replay of the site’s retained one-minute ranges
The signal-specific collector audit returned 106 OANDA:XAUUSD one-minute bars. The audited window has no missing minute slots. For a SELL, a low at or below a target counts as a nominal touch and a high at or above the original stop counts as a nominal stop. An earlier stop contradicts target-first ordering. A bar touching both requires finer verified observations to resolve the order. Activation was reported on the minute boundary. The final range includes the minute opening at the TP3 timestamp, and the first TP3 touch is in the preceding minute.
The maximum retained high in that window is 4047.435, below the original stop. No stop-before-target or same-bar stop/target conflict appears in these ranges. The site’s collector and the indicator both rely on TradingView inputs. An independently authenticated matching OHLC series was unavailable, so the replay remains a diagnostic on the collector data.
| Threshold | Minute open, UTC | High | Low |
|---|---|---|---|
| TP1 | 12:02 | 4045.480 | 4044.065 |
| TP2 | 13:07 | 4041.320 | 4039.735 |
| TP3 | 13:44 | 4033.730 | 4032.175 |
The entry level and the activation timestamp
The original 11:45 UTC proposal fixed the reference entry at 4,050.022 and its stop at 4,055.029. The 11:47 UTC collector minute had a high of 4,050.340 and a low of 4,048.660, bracketing the entry. The gateway separately retained an activation report stamped 12:00:00.000, received at 12:00:06.720. The 12:00 minute remained entirely below entry, with a high of 4,045.765. Neither the earlier range nor the later message establishes a broker fill.
The retained bars from creation to the activation report also stayed below the original stop. Their highest high was 4,050.360. Keeping this earlier window in the snapshot makes it possible to check what happened before the activation clock started, without assigning a precise time to the crossing within the 11:47 minute.
Why quarter-hour reports differ from one-minute thresholds
All five source timestamps fell on quarter-hour boundaries. TP1 was first reached in the 12:02 collector bar and reported at 12:15. TP2 was first reached in the 13:07 bar and reported at 13:15. The 13:44 bar closed at 13:45 and had a low of 4,032.175, below the third reference target of 4,033.494. The source reported TP3 at 13:45:00.000 and the receiver stored it 1.194 seconds later. The boundaries are observable. The event record does not expose the alert’s internal execution rule.
The original entry-to-stop distance was 5.007 and the entry-to-TP3 distance was 16.528 per troy ounce, or 3.301 times the original reference risk. The highest high after the activation report and through the TP3 report minute was 4,047.435. In that window, the retained ranges never reached the original stop.
Read the engine field before comparing outcomes
The payload identifies CyGuru Indicator 3.2 RC1. The dossier describes a later research profile, but the event alone cannot establish the alert’s Pine build. Two Hazem CHoCH SELLs were also active on XAU/USD after noon and reported TP3 at different levels and times. Opening the individual terminal records shows how engine, timeframe, target ladder and activation history distinguish those three reports.
The snapshot preserves 8 other records with overlapping reported active windows on the same symbol. The selection and shared price exposure preclude an overall win rate, a claim of independence or an inference about future profits.
Download the dated JSON evidence and replay inputs →
Use Gold Terminal to compare the original plans, setup identities and reported outcomes →
Read the earlier five-minute Hazem TREND SELL case →
CyGuru Indicator dossier · Research methodology · Gold trading journal guide · Gold Intelligence · Follow Research Lab