13 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M BUY · SWEEP
A Gold SWEEP Reached Reported TP3 After a $0.264 Stop Clearance
A Hazem SWEEP BUY reported TP3 after a 39-minute active window. The retained low stayed just $0.264 above its original stop, while a separate TP2 report time remained absent.
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 66-HAZEM-V1, payload schema 1, OANDA:XAUUSD, 5-minute timeframe, BUY and SWEEP were recorded. A separate script build hash was unavailable.
Signal ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794536400000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794536400000|1794538860175|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 | 3907.864 | — | — |
| Original SL | 3904.471 | 3.393 adverse | 1.000R |
| TP1 | 3911.680 | 3.816 favorable | 1.125R |
| TP2 | 3916.760 | 8.896 favorable | 2.622R |
| TP3 | 3919.362 | 11.498 favorable | 3.389R |
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 40 OANDA:XAUUSD one-minute bars. The audited window has no missing minute slots. For a BUY, a high at or above a target counts as a nominal touch and a low at or below 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 activation minute opens 174 milliseconds before the activation report and reaches neither TP1 nor the original stop. Forty retained bars run from 02:22 through 03:01 UTC inclusive. The final minute includes prices after the TP3 source report; the first TP3 threshold is in the preceding completed 03:00 bar.
The minimum retained low in that window is 3904.735, above 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 | 2026-11-13 02:32 | 3912.055 | 3908.135 |
| TP2 | 2026-11-13 03:00 | 3920.420 | 3915.745 |
| TP3 | 2026-11-13 03:00 | 3920.420 | 3915.745 |
A narrow stop clearance before the targets
The five-minute SWEEP BUY was proposed at 02:20 UTC and reported active at 02:22:00.174. The lowest retained price in the replay window was $3,904.735 in the 02:28 minute: only $0.264 above the original $3,904.471 stop. That was $3.129 below the $3,907.864 reference entry, approximately 0.922 of the original risk distance. The path therefore came close to the proposal’s invalidation boundary before its later target reports. A terminal outcome label alone would conceal this part of the sequence.
The clearance is a comparison within the retained OANDA:XAUUSD series. It cannot establish what a particular broker quoted or whether an order survived its spread. The original $3.393 stop distance remains the denominator throughout this review. TP3 is $11.498 above entry, about 3.389R in reference distance; this is not money earned or a verified trade return.
Why the missing TP2 time must stay missing
TP1 was reported at 02:35:00.175 UTC, thirteen minutes and one millisecond after activation. TP3 was reported at 03:01:00.175, exactly twenty-six minutes after TP1 and thirty-nine minutes and one millisecond after activation. The event chain contains no separate TP2_HIT. Reaching the higher reported milestone does not manufacture an intermediate source timestamp.
The first collector minute whose high includes TP1 opens at 02:32, earlier than the 02:35 source report. TP2 and TP3 first appear together in the 03:00 minute, whose open, high, low and close are $3,915.815, $3,920.420, $3,915.745 and $3,919.630. These are bar boundaries and threshold observations, not exact touch or fill times. A one-minute bar does not tell us the intraminute path between its extrema. The absence of a stop touch removes a target-versus-stop conflict in this retained window, but it does not supply the missing TP2 event.
Separate the source clock from receipt and price collection
The creation message reached the gateway 5.061 seconds after its stated source time. Activation arrived 0.641 seconds after its source time, TP1 after 1.063 seconds and TP3 after 3.396 seconds. These differences measure recorded source-to-receiver timestamp gaps; they are not a measurement of order latency, and clock synchronization has not been independently validated.
The completed 03:00 collector bar was received at 03:01:03.917 UTC, 0.346 seconds after the TP3 event reached the gateway at 03:01:03.571. The report and bar are two retained records from related TradingView inputs. Their agreement is useful for auditability, but neither is an independently authenticated execution confirmation.
Use the terminal to compare plans before comparing outcomes
The terminal makes the original plan, setup identity and subsequent reports available in one place. That allows a reader to check whether levels moved after activation, distinguish a later target message from an original proposal, and see exactly which milestone timestamps are absent. For this identity, every retained message repeats the same entry, stop, three targets, creation time and expiry time; no freeze check relies on the final card alone.
No other same-symbol record with an explicit activation report overlaps the 02:22:00.174–03:01:00.175 active window in this feed snapshot. Records lacking activation cannot be assigned invented active windows. The later Hazem PULLBACK proposal was created at 03:40 UTC, after this TP3 report, so it is not an overlapping active setup. Absence of a measured overlap in this one window does not establish statistical independence across the wider strategy or turn this selected example into a performance sample.
The snapshot preserves 0 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 →
66 Hazem Signal dossier · Research methodology · Gold trading journal guide · Gold Intelligence · Follow Research Lab