12 NOVEMBER 2026 · CYGURU SAFE SIGNAL · 15M SELL · PULLBACK
CyGuru Safe Reported TP3 With No Separate TP2 Event
The noon CyGuru Safe PULLBACK SELL recorded activation, TP1 and TP3. Its separate TP2 message is missing. Thirty closed one-minute ranges show where the price crossed that level while preserving the distinction between a price threshold and an indicator event.
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-SAFE-V1, payload schema 1, OANDA:XAUUSD, 15-minute timeframe, SELL and PULLBACK were recorded. A separate script build hash was unavailable.
Signal ID CYGURU-SAFE-V1|OANDA:XAUUSD|15|1794484800000
TP3 event ID CYGURU-SAFE-V1|OANDA:XAUUSD|15|1794484800000|1794487500000|TARGET
Production feed observed through .
All 4 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 | 3946.396 | — | — |
| Original SL | 3950.185 | 3.789 adverse | 1.000R |
| TP1 | 3942.121 | 4.275 favorable | 1.128R |
| TP2 | 3938.623 | 7.773 favorable | 2.051R |
| TP3 | 3933.958 | 12.438 favorable | 3.283R |
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 | ||
| TP3_HIT |
Separate TP2 source timestamp unavailable. The retained event sequence supplies the times shown above.
Replay of the site’s retained one-minute ranges
The signal-specific collector audit returned 30 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. The audit includes the 30 fully closed minutes from 12:15 up to the 12:45 TP3 report boundary. The 12:15 bar contains the first nominal TP1 touch. The first TP3 touch is in the 12:40 bar.
The maximum retained high in that window is 3948.520, 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:15 | 3943.855 | 3942.115 |
| TP2 | 12:33 | 3939.085 | 3937.350 |
| TP3 | 12:40 | 3935.700 | 3933.840 |
The middle price threshold has a bar and no separate report
The collector first reached the 3,938.623 TP2 threshold in the 12:33 UTC bar, with a low of 3,937.350. The production event history jumps from TP1 at 12:30:00.000 to TP3 at 12:45:00.000. The 12:33 minute belongs in a replay column. It cannot supply a source or receiver timestamp for a TP2 message.
The 12:40 bar first reached TP3 at 3,933.958, with a low of 3,933.840. The bar closed at 12:41 and its row reached the site at 12:41:02.613. The indicator’s TP3 reached the gateway at 12:45:05.974. The observed gap comes from the retained records. The cause of the gap and the reason for the absent TP2 message are unverified.
The first price touch was in the activation minute
Activation was reported at the 12:15 boundary. The 12:15 bar recorded a low of 3,942.115, only 0.006 through TP1. The separate TP1 report came at 12:30:00.000. The bar supplies a range after the reported activation boundary. It cannot locate the touch to a specific second or establish an execution price.
The highest high in the audited window was 3,948.520 at 12:19, 1.665 below the original 3,950.185 stop. The original 3.789 risk distance and 12.438 TP3 distance give a reference multiple of approximately 3.283. All four production messages kept the same original levels.
Use the engine name and the complete signal ID
The noon Hazem pullback had a similar ladder and a separate TP2 alert at 12:33:18.216. Its TP2 alert cannot fill the blank for Safe. The two identities used slightly different levels, activated at different times and reported TP3 at different times while sharing part of the same price move.
Gold Terminal allows a reader to compare the original plans and follow each lifecycle separately. Match the engine, symbol, timeframe and full signal ID before attributing a target to a plan. The dated evidence includes the source and receiver clocks, the collector rows and the four overlapping records.
The snapshot preserves 4 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 →
CyGuru Safe Signal dossier · Research methodology · Gold trading journal guide · Gold Intelligence · Follow Research Lab