10 NOVEMBER 2026 · HAZEM 5M SELL · TREND

Three Targets, Two Clocks: Auditing a Hazem TREND Gold SELL

A TREND SELL reports three completed targets without a reported stop. The useful research question is why the retained one-minute bars cross two thresholds before the corresponding messages. A second SELL, stopped during the same interval, prevents this selected favorable report from becoming a claim about the whole system.

Gabriel Nicolaev — CyGuru
Published 10 November 2026 · 16:37:33 UTC / 20:37:33 Dubai (UTC+4)

Open CyGuru Gold Terminal — inspect the original plans and reported lifecycle events →

What qualifies this record for a selected evidence study

The retained production identity is 66-HAZEM-V1|OANDA:XAUUSD|5|1794321300000. Its engine is 66-HAZEM-V1, payload schema version 1, symbol OANDA:XAUUSD, timeframe five minutes, direction SELL and setup TREND. V1 is the supplied engine identifier; a separate code-build hash is unavailable. This case uses current production gateway events, not synthetic tests or the unrelated CY66 archive.

Creation is reported at 14:35 UTC / 18:35 Dubai on 10 November. Activation follows at 15:15:01.161 UTC, and an actual TP3_HIT event follows at 16:27:32.815 UTC / 20:27:32.815 Dubai. All five available messages retain the same identity, setup, original levels, creation timestamp and expiry of 11 November at 07:50 UTC. No stop, cancellation or invalidation event appears for this identity at the fixed observation cutoff, 10 November 16:30:15.374 UTC / 20:30:15.374 Dubai. A fresh duplicate and event check at 16:33:19.295 UTC found the selected event objects unchanged.

This supports publication as an indicator-reported reference observation. It does not independently authenticate source prices, prove that every upstream event was delivered, or establish a broker trade. The gateway's SUCCESS label is a reported classification, not audited investment performance.

Frozen levels: the plan before the favorable report

The denominator is the original entry-to-stop distance: 4,059.087 − 4,051.200 = 7.887. Each ratio divides a reference target distance by that same denominator. It is neither a percentage return nor money earned. Partial exits, stop adjustments, position sizing and actual executable prices are unavailable. No management rule is reverse-engineered from the favorable endpoint.

Five source messages and their receiver clock

The proposed setup waits 40 minutes 1.161 seconds for reported activation. Activation to reported TP3 is 72 minutes 31.654 seconds; creation to TP3 is 112 minutes 32.815 seconds. Separate TP1 and TP2 times are present: 15:50:05.310 and 16:18:05.305 UTC. None needs to be inferred from the final TP3 label.

The activation message arrives 11.764 seconds after its source timestamp; TP3 arrives 0.190 seconds after its source timestamp. These differences describe the retained messages, not a latency guarantee or proof of synchronized clocks. The activation event ID ends in FILL, but its payload says activation_reported. That naming convention is not an authenticated broker fill.

A reproducible diagnostic, with no favorable intrabar assumption

The signal-specific audit response retains 235 consecutive one-minute bars, with 235 expected and zero missing clock slots in its requested window. Its declared source is the CYGURU.GOLD direct TradingView one-minute collector for OANDA:XAUUSD. The raw response, bar receiver times and complete original event objects are preserved in the downloadable evidence snapshot.

The calculation is conditional on reported activation. For this SELL, a high at or above 4,059.087 counts as an original-stop touch; a low at or below a target counts as a nominal target-threshold observation. An earlier stop would contradict target-first classification. If a single bar contains stop and target, order stays ambiguous without finer verified observations. No target-first convention, interpolation or backfill is applied.

The partial activation minute, 15:15–15:16 UTC, has a high of 4,052.305 and low of 4,049.270; it contains neither original SL nor TP1. The maximum retained high after reported activation through the audit window is 4,054.165, below the original stop. Thus no nominal original-stop touch is found in that interval. This is a calculation on retained ranges, not a reproduction of the complete entry algorithm.

Why the two timelines must remain separate

The first retained TP2 threshold occurs in the 15:50 bar, whereas TP2_HIT is timestamped 16:18:05.305. The first retained TP3 threshold occurs in the 16:23 bar, whereas TP3_HIT is timestamped 16:27:32.815. These differences are observable; their cause is not established. They could require examination of script evaluation rules, feed construction or clock alignment. This evidence does not choose an explanation.

TP1 and TP2 are inside the same first threshold minute, so exact intraminute touch times are unavailable. The completed 15:50 bar also cannot prove that its eventual low occurred before the TP1 source timestamp at 15:50:05.310. Retain the bar interval and message time as different observations. The absence of a nominal stop conflict supports threshold-before-stop ordering within this series, but not exact message-to-price synchronization.

The collector shares reporting infrastructure with the signal system. No independently authenticated matching OHLC replay was available for this review. No genuine independent historical chart is supplied, and generated candles are never used as evidence. Classification remains selected indicator-reported TP3, with a nominal collector diagnostic and unresolved timing differences.

The stopped SELL inside the same observation interval

A distinct five-minute PULLBACK SELL, full identity 66-HAZEM-V1|OANDA:XAUUSD|5|1794324300000, is created at 15:25 UTC. It reports activation at 15:31:25.318 and STOP_LOSS_HIT at 15:32:35.319 UTC. Its entry is 4,049.295 and original stop 4,052.767. That stop belongs to the other identity; it must neither be attached to this TREND record nor omitted when explaining selection.

Both proposals share engine, symbol and direction and overlap in time, so they are dependent observations of the same market path. Their different reference stops help explain why a same-direction pair need not have identical reported outcomes; they do not establish a causal trading edge. Other nearby pending and earlier records are preserved in the snapshot. This selected favorable example establishes no overall win rate, independence, future-profit claim or portfolio result.

What the terminal makes practically useful

The CyGuru Gold Terminal keeps the original proposal, timeframe, setup and successive reports available together. Use the Signal Explorer to distinguish full identities rather than comparing only green target labels. This case demonstrates the practical benefit: a reported completion can be examined alongside frozen risk, receiver delays, timing discrepancies and a neighboring stopped setup.

Download the dated sanitized evidence JSON → · Evaluation methodology · Hazem indicator dossier

Continue with the gold trading journal guide, the Guides library, Gold Intelligence and Gold Trading Mastery. Before You Click addresses the decision discipline needed to avoid treating a favorable selected example as a promise. Follow the public feeds for further dated research.

Historical educational evidence study. Broker fills, commissions, spread, slippage and P&L remain unverified. This is not a current trading instruction.