9 NOVEMBER 2026 · HAZEM 5M · SELL · CHoCH
From CHoCH to TP3: Auditing a Hazem Gold SELL in 20 Minutes
A fixed risk plan, a reported activation and three separately timestamped targets: this selected Hazem SELL record shows how the CyGuru Gold Terminal turns a target label into an inspectable event trail.

Open CyGuru Gold Terminal — inspect signals, reference levels and event history →
What the production record actually establishes
The receiver stored a 66-HAZEM-V1 proposal for OANDA:XAUUSD, 5 minutes, SELL, CHoCH, created at 16:30 UTC / 20:30 Dubai on 9 November 2026. Its subsequent history contains an activation report and individual TP1_HIT, TP2_HIT and TP3_HIT events. TP3 was reported at 16:50:50.427 UTC / 20:50:50.427 Dubai. This is a favorable indicator-reported reference outcome, not a verified broker trade.
The fixed observation cutoff is 17:19:45.425 UTC / 21:19:45.425 Dubai, 9 November 2026. The available five-event history contains no stop-loss, invalidation or conflicting outcome for this identity. That describes the retained record at the cutoff; it does not prove that every possible script message was delivered.
| Field | Level | Entry distance |
|---|---|---|
| SELL entry | 4,116.647 | Reference |
| Stop loss | 4,119.587 | 2.940 above entry |
| TP1 | 4,113.170 | 3.477 below entry |
| TP2 | 4,110.621 | 6.026 below entry |
| TP3 | 4,107.006 | 9.641 below entry |
Source time and receiver time are different clocks
All five timestamps below belong to 9 November 2026. Source time is supplied by the indicator; receiver time is when CyGuru stored the message. The activation message arrived about 10.372 seconds after its source timestamp, while the TP3 message arrived 0.117 seconds later. These observed gaps are not a general latency benchmark and do not establish broker execution speed.
| Event | Source UTC | Source Dubai | Receiver UTC |
|---|---|---|---|
| SIGNAL_CREATED | 16:30:00.000 | 20:30:00.000 | 16:30:05.991 |
| Activation reported | 16:30:25.436 | 20:30:25.436 | 16:30:35.808 |
| TP1_HIT | 16:46:02.966 | 20:46:02.966 | 16:46:06.500 |
| TP2_HIT | 16:48:57.926 | 20:48:57.926 | 16:48:58.811 |
| TP3_HIT | 16:50:50.427 | 20:50:50.427 | 16:50:50.544 |
The source interval from activation to TP3 is 20 minutes 24.991 seconds. The final two targets were reported less than two minutes apart. This describes the event sequence, not every intervening market tick. The word FILL in an event identifier remains a script activation label; it is not a broker fill confirmation.
The freeze check: no moving targets in the preserved history
I compared Entry, SL, TP1, TP2 and TP3 in the creation message with the corresponding fields in every later message. All five levels match across all five events. Direction, symbol, timeframe, setup, creation time and expiry also agree. The source expiry is 10 November 2026 at 09:45 UTC / 13:45 Dubai; the TP3 event precedes it.
This consistency matters because changing targets after a favorable move would weaken the evidential value of the result. Here the stored messages preserve the original plan. The narrower conclusion is important: matching messages do not prove that the script never changed internally between reports, and no executable Pine revision hash or input configuration accompanies these events. The available engine identity is 66-HAZEM-V1, schema version 1.
Reference distance is not money earned
The original stop distance is 2.940. Dividing the target distances by that amount produces approximately 1.183R, 2.050R and 3.279R for TP1, TP2 and TP3. These are nominal price-distance ratios. They neither imply a position size nor tell us whether a trader exited partially, paid a particular spread, or obtained the reference entry.
There is no basis here for a cash-profit figure. Broker fills, commissions, spread, slippage, financing and P&L are unverified. A strategy-level claim would also need the complete eligible population, including losses and unresolved setups, assessed under fixed rules.
Where independent OHLC verification stops
No complete matching OHLC sequence was retrieved for independent replay in this publication. The current source includes an audit-history route and a collector health endpoint; endpoint availability alone is not evidence that a complete matching dataset has been verified. The result remains indicator-reported reference evidence. No historical candles have been generated to stand in for missing data.
A separate replay should match OANDA:XAUUSD and the signal window, establish activation without using later information, then test whether a target occurred before SL. For a SELL, a low at or below a target and a high at or above SL inside the same unresolved candle must be marked ambiguous unless finer verified observations establish ordering. Gaps must remain gaps. Even a successful OHLC replay would describe nominal price touches, not broker execution.
Selection and overlapping setups
This case was selected because it reported TP3 after the fixed initial boundary of 14:30 UTC on 9 November. It is not a random sample or an overall win-rate study. A separate Hazem five-minute proposal was created at 16:45 UTC while this case was still progressing; their evaluation windows overlap. They must not be counted as independent market experiments or added together as account returns.
Why the terminal is useful in practice
CyGuru Gold Terminal combines a chart workspace with signal identity, original reference levels and reported milestones. The useful innovation is the review path: move from a green TP label to the underlying signal history, compare the original plan with later updates, and preserve a dated record instead of relying on an undated screenshot.
For this record, that process reveals a stable plan and a complete reported target progression. It also keeps the limits visible. Readers can monitor later signals in Signal Explorer, examine the Hazem research dossier, and use the Strategy Lab for broader comparisons. One favorable example cannot establish independence or predict future profit.
Preserved primary evidence
Source: CyGuru Gold production receiver storage, read through the Sites database tools at the cutoff above. The current /api/terminal/signals source reads this same production table. Direct HTTP access returned 403 in this environment, so this article does not claim a successful public-API readback. All 700 available rows were scanned; archived unrelated CY66 records and synthetic tests were excluded. The public snapshot retains this signal’s original sanitized event objects and individual receiver times without credentials.
Full signal ID: 66-HAZEM-V1|OANDA:XAUUSD|5|1794241800000
Download the dated evidence JSON → · Public production feed →
Historical educational research. No verified fills, costs or P&L; no current trade instruction.

