11 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M BUY · TREND
When Gold Touches TP3 Before the Indicator Reports It
The five-minute Hazem TREND BUY reported its third target at 07:37:00.205 UTC. The site’s retained one-minute ranges had already crossed that level in the 07:24 bar. Reading the two timelines together shows what the terminal can establish about this selected signal and where the evidence ends.
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|1794379800000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794379800000|1794382620205|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 | 4057.320 | — | — |
| Original SL | 4054.086 | 3.234 adverse | 1.000R |
| TP1 | 4060.905 | 3.585 favorable | 1.109R |
| TP2 | 4063.025 | 5.705 favorable | 1.764R |
| TP3 | 4066.080 | 8.760 favorable | 2.709R |
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 46 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 4056.765, 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 | 06:57 | 4061.945 | 4060.390 |
| TP2 | 07:03 | 4064.395 | 4061.615 |
| TP3 | 07:24 | 4066.535 | 4063.415 |
The plan held still as the event history grew
The proposal was created at 06:50:00.000 UTC and reported activation 2 minutes and 0.176 seconds later. The activation minute ranged from 4,056.925 to 4,057.540. That range contains the proposed entry of 4,057.320 and stays between the original stop and first target. The range supports a comparison with the planned entry. It cannot identify the precise time or terms of an execution.
All five messages preserve the original stop of 4,054.086. The entry-to-stop distance is 3.234 per troy ounce. The distance to TP3 is 8.760 per troy ounce, about 2.71 times the original stop distance. The lowest recorded low over the diagnostic window was 4,056.765, or 2.679 above the original stop. The calculation uses the original stop throughout because the evidence contains no independently established amendments to an executed order.
A target crossing and a lifecycle update answer different questions
The first collector highs above TP1 and TP2 occurred during the minutes beginning at 06:57 and 07:03 UTC. Their separate indicator messages followed at 06:58:00.176 and 07:04:00.204. After TP2, the report sequence waited another 33 minutes and 0.001 seconds for TP3. A dashboard reduced to the final status would conceal that interval.
The 07:24 minute reached 4,066.535, above the fixed TP3 of 4,066.080. Its close of 4,065.820 finished below the threshold. That difference is why the replay states explicitly that it uses the high of the bar for a BUY target. A rule requiring a close at or above the target would test a different condition. The observed high occurred somewhere in the 07:24 minute, which ended 12 minutes and 0.205 seconds before the TP3 source report. The receiver timestamp is only 0.252 seconds after that report. These are separate intervals, and the record does not identify why the report followed the range crossing.
The same market window contained another active plan
A separate 15-minute Hazem TREND BUY on OANDA:XAUUSD reported activation at 01:47:30.815 UTC and was still at TP2 in the observed feed. Its active window overlaps this five-minute case. The timeframe and full identity determine which entry, stop and targets belong to each record. The five-minute TP3 message cannot close the fifteen-minute plan.
The terminal lets a reader open the individual plan and follow its lifecycle through the event history. The dated snapshot makes it possible to compare the initial levels with the final update even after the live list changes. For this case I would preserve both the minute containing the first threshold crossing and the separate TP3 event time. Those two fields answer different audit questions without assuming a fill or explaining why the indicator reported when it did.
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