11 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M BUY · CHoCH
A CHoCH BUY Across Overlapping Gold Setups
The earliest proposal in this group took about 35 minutes to report activation and more than three hours from activation to report TP3. Its longer window shows why counting multiple overlapping gold signals as independent confirmations can mislead.
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 CHoCH were recorded. A separate script build hash was unavailable.
Signal ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794360900000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794360900000|1794375180176|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 | 4041.872 | — | — |
| Original SL | 4035.469 | 6.403 adverse | 1.000R |
| TP1 | 4049.134 | 7.262 favorable | 1.134R |
| TP2 | 4055.075 | 13.203 favorable | 2.062R |
| TP3 | 4062.998 | 21.126 favorable | 3.299R |
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 204 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.685, 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 | 03:12 | 4049.135 | 4048.155 |
| TP2 | 05:15 | 4055.855 | 4052.400 |
| TP3 | 05:31 | 4063.220 | 4059.210 |
Begin the replay at reported activation
The proposal was created at 01:35 UTC. The activation report is timestamped 02:10:01.016 UTC, so 35 minutes 1.016 seconds separate the two messages. TP1 was reported at 03:16:28.345, TP2 at 05:16:00.204, and TP3 at 05:33:00.176. Activation to the final source report spans 3 hours 22 minutes 59.160 seconds. The interval before activation remains part of the proposal history and is excluded from the active stop-versus-target diagnostic.
The 02:10 collector bar includes the original entry in its range, with neither the original stop nor TP1 touched. Its minute range cannot pinpoint activation to a fraction of a second. The receiver’s activation timestamp is 3.953 seconds after the source report, while its TP3 timestamp is 0.757 seconds later than the corresponding source time. Both pairs are available for subsequent review.
Treat a near-threshold high at its reported precision
The first nominal TP1 touch in the collector is at 03:12 UTC. The high of 4,049.135 is only 0.001 above the frozen TP1 of 4,049.134. I retain that comparison at the source precision and keep it separate from the TP1 message at 03:16:28.345. Its tiny margin limits what can be carried over to another quote basis or an execution reconstruction.
The first nominal TP3 threshold occurs in the 05:31 minute at a high of 4,063.220 against the frozen 4,062.998 target. The source report follows in the 05:33 minute. None of the retained active-window lows reaches the original stop. The observation concerns the specified collector window, and a different price series should be checked against the same frozen levels before being used as corroboration.
Keep the overlap visible when comparing outcomes
The 02:30 TREND and the 05:00 PULLBACK BUY cases both report TP3 inside this record’s activation-to-TP3 window. They share the instrument and some of the underlying price path, even though each identity carries its own entry, stop and targets. A five-minute Hazem TREND BUY proposed at 04:05 UTC also reported a stop at 04:15 UTC inside the same window.
For an evaluation of the engine, I would preserve favorable, adverse and unresolved records over a declared interval, then group their overlapping active windows before analyzing the sample. Here the evidence supports one selected CHoCH observation. The terminal helps recover the full identity and timestamps that a screenshot or a count of target badges would leave out.
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