11 NOVEMBER 2026 · 66 HAZEM SIGNAL · 15M SELL · PULLBACK
The TP3 Alert Arrived Before the One-Minute Bar Closed
On 11 November a 15-minute Hazem PULLBACK SELL reported TP3 roughly halfway through the 14:37 UTC minute. The terminal preserved the alert before the collector stored the completed bar. The two records answer different timing questions.
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, 15-minute timeframe, SELL and PULLBACK were recorded. A separate script build hash was unavailable.
Signal ID 66-HAZEM-V1|OANDA:XAUUSD|15|1794404700000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|15|1794404700000|1794407850824|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 | 4035.839 | — | — |
| Original SL | 4041.338 | 5.499 adverse | 1.000R |
| TP1 | 4029.667 | 6.172 favorable | 1.122R |
| TP2 | 4024.617 | 11.222 favorable | 2.041R |
| TP3 | 4013.635 | 22.204 favorable | 4.038R |
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 52 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 window runs from the activation minute through the TP3 report minute. The activation minute is partial relative to the event clock and contains neither the stop nor TP1.
The maximum retained high in that window is 4038.400, 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 | 14:09 | 4030.820 | 4029.530 |
| TP2 | 14:33 | 4026.170 | 4021.415 |
| TP3 | 14:37 | 4018.125 | 4010.790 |
What the alert clock can establish
Hazem created the SELL plan at 13:45 UTC and reported activation at 13:46:15.845. The 13:45 collector high of 4,035.770 was below the 4,035.839 reference entry. The next minute opened at 4,035.865, just above it, and the 13:47 range bracketed the entry. The minute ranges leave the exact crossing between these observations unresolved. The activation time comes from the production event, and the broker fill remains unverified.
The entry and targets were fixed when the plan was created. The original stop sat 5.499 per troy ounce above entry. TP3 was 22.204 below entry, or 4.038 times the original reference risk. The distance from TP2 to TP3 was 10.982, the largest gap between successive targets. Yet only 3 minutes and 45.009 seconds separated the TP2 and TP3 reports, compared with 23 minutes and 7.470 seconds between TP1 and TP2. These intervals compare report clocks. They do not measure the speed of execution or the time a position spent at a price.
Why the final candle cannot time the touch
The collector first reached TP1 in the 14:09 minute and TP2 in the 14:33 minute. Its first TP3 threshold range opened at 14:37. The low was 4,010.790 against the 4,013.635 target. The source stamped TP3 at 14:37:30.824 and the receiver saved it at 14:37:30.953. The collector stored the closed minute at 14:38:07.054. The complete range shows that the threshold was reached sometime in the minute. It cannot show whether the touch preceded the alert to the second.
The highest high in the 52-minute collector window was 4,038.400, which was 2.938 below the original stop of 4,041.338. Even the range of the final minute stayed below the stop. That rules out a same-minute stop and target conflict in the retained ranges.
A nearby PULLBACK SELL reported a stop
A separate five-minute Hazem PULLBACK SELL activated at 13:56:00.205 UTC and reported a stop at 13:58:00.175, while this fifteen-minute plan remained active. In the terminal, the individual signal view makes it possible to match each original plan to its activation and outcomes. Filtering only by direction and setup would put the two plans together while hiding the levels and timeframe that distinguish them.
The snapshot preserves 1 other record 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