11 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M BUY · TREND
After the First Target: A Hazem TREND BUY Audit
The first target report arrived minutes after activation. More than two and a half hours elapsed before the second target report. The full lifecycle puts that wait, the original stop, and the later favorable endpoint in the same record.
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 TREND were recorded. A separate script build hash was unavailable.
Signal ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794364200000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794364200000|1794374400175|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 | 4043.079 | — | — |
| Original SL | 4039.569 | 3.510 adverse | 1.000R |
| TP1 | 4046.962 | 3.883 favorable | 1.106R |
| TP2 | 4052.675 | 9.596 favorable | 2.734R |
| TP3 | 4055.323 | 12.244 favorable | 3.488R |
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 171 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 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 minimum retained low in that window is 4039.815, 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 | 02:35 | 4047.585 | 4045.395 |
| TP2 | 05:08 | 4052.895 | 4050.835 |
| TP3 | 05:15 | 4055.855 | 4052.400 |
The early report did not close the research question
The TREND proposal was created at 02:30 UTC and activation was reported 28.375 seconds later. TP1 followed at 02:36:13.344 UTC. TP2 arrived on the source clock at 05:09:00.175, 2 hours 32 minutes 46.831 seconds after TP1. The TP3 source event followed at 05:20:00.175, exactly 11 minutes after TP2. The setup’s published reference levels stayed fixed across those changes in status.
A journal that records only the creation and final endpoint hides the time during which the setup remained unresolved. A reader evaluating exposure would need a separate rule for what happens after TP1, including whether any quantity is reduced or the stop is moved. Those decisions are outside the source evidence here. I keep the original stop throughout the diagnostic so the same predeclared reference applies to all 171 minutes.
The first TP3 threshold and the TP3 message use different clocks
The 05:15 UTC collector minute has a high of 4,055.855, above the original TP3 of 4,055.323. The source TP3 report is timestamped 05:20:00.175, and the receiver stores it 0.568 seconds later. The elapsed time between the first collector minute and the report is therefore much larger than the measured source-to-receiver delay for this event.
That comparison narrows the timing question. The first minute’s eventual high does not tell us when the indicator first evaluated the level or which rule produced the later report. A comparison of the script’s evaluation settings and quote series would be needed to explain the difference. The evidence preserves the bar and both event clocks so those hypotheses can be tested.
A later BUY could stop while this BUY remained active
A separate five-minute Hazem TREND BUY proposed at 03:05 UTC reported a stop at 04:20:40 UTC. Its overlap with this case is instructive. Identical direction, engine and family do not guarantee the same risk window or levels. This earlier BUY’s reported TP3 therefore cannot be generalized to the other TREND records that shared the morning.
In a comparative audit, I would group the overlapping setups under the same market episode and retain each outcome under its full signal identity. The terminal’s plan and event views make that possible. The long wait after TP1 belongs in the evidence alongside the favorable endpoint.
The snapshot preserves 11 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