10 NOVEMBER 2026 · HAZEM 5M SELL · CHoCH

Seven and a Half Minutes: Hazem’s Overnight TP3 Evidence

The five-minute SELL reached reported TP3 in just under seven and a half minutes after activation. A fifteen-minute BUY was being stopped during the same interval. The contrast makes signal identity, rather than a green label alone, the essential unit of this audit.

Gabriel Nicolaev — CyGuru
Published 10 November 2026 · 01:59:09 UTC / 05:59:09 Dubai (UTC+4)

Open CyGuru Gold Terminal — compare reference plans and reported event histories →

The selected result, precisely stated

The production receiver retained a 66-HAZEM-V1, OANDA:XAUUSD, 5-minute SELL, CHoCH proposal created on 10 November at 00:05 UTC / 04:05 Dubai. Activation was reported at 00:10:30.476 UTC. Separate TP1_HIT and TP2_HIT messages precede an actual TP3_HIT at 00:18:00.475 UTC / 04:18:00.475 Dubai. All are source-event timestamps, not broker confirmations.

The fixed observation cutoff is 10 November 2026, 01:45:59.381 UTC / 05:45:59.381 Dubai. The scan covered 779 stored event rows. This signal’s five available messages contain no contradictory stop-loss, cancellation or invalidation. Missing messages cannot be ruled out merely because none is retained. The result is a selected favorable indicator-reported reference observation.

A timeline with three clocks

Creation, activation and target reporting are distinct events. The table preserves the indicator’s UTC and Dubai timestamps alongside the receiver’s UTC arrival times. Dubai is UTC+4. Millisecond precision describes the retained messages; it does not independently certify the source clock.

Activation follows creation by 5 minutes 30.476 seconds. TP3 follows activation by 7 minutes 29.999 seconds, and follows creation by 13 minutes 0.475 seconds. TP1 to TP2 takes 2 minutes 59.971 seconds; TP2 to TP3 takes 1 minute 44.998 seconds. Individual lower-target times are available in this case, so no intermediate milestone has been assigned an invented timestamp.

The activation message arrived 0.113 seconds after its source time; TP3 arrived 1.782 seconds after its source time. Those two gaps are observations for these messages, not a system latency guarantee. The FILL suffix in the activation event ID describes the script’s report, not an authenticated broker fill.

What the freeze check verifies

Entry, stop and all three target prices match the creation message in every later event. Symbol, timeframe, direction, setup, creation time and expiry also agree. The source expiry is 17:20 UTC / 21:20 Dubai on 10 November, later than TP3. This is evidence of stable reported levels across the preserved lifecycle, not a continuous inspection of internal script state.

The available engine/version identifier is 66-HAZEM-V1, with schema version 1. A Pine source hash and complete indicator input configuration are not supplied. This limits reproduction: the article can audit the delivered plan and event consistency, but cannot reconstruct every internal rule that generated the proposal.

The overlapping BUY is part of the context

A different record, 66-HAZEM-V1|OANDA:XAUUSD|15|1794266100000, was a fifteen-minute PULLBACK BUY created at 23:15 UTC on 9 November. Its activation was reported at 23:31:38.016 UTC and its STOP_LOSS_HIT at 00:15:38.015 UTC on 10 November. That stop falls between this SELL’s TP1 and TP2 reports. The context record is preserved separately in the JSON snapshot.

These are different hypotheses with different identities and timeframes. The BUY’s stop does not invalidate the SELL’s retained TP3 sequence; the SELL’s favorable outcome does not erase the BUY’s adverse observation. Their active windows overlap, so they are not independent experiments. Neither selecting the favorable record nor combining opposite proposals supplies an account return or an overall win rate.

Reference geometry, without an earnings claim

The stop distance of 2.036 gives nominal target-distance ratios of approximately 1.294R, 2.028R and 3.283R. The target distances are not equally spaced, so assuming that TP1, TP2 and TP3 always mean 1R, 2R and 3R would misdescribe this plan. Here R is only the original price distance from entry to stop.

No position size, actual entry, partial exit or executed stop is established. Broker fills, commissions, spread, slippage, financing and P&L remain unverified. A small reference stop can make a ratio look attractive while execution costs consume a material share of that distance; this record contains no verified cost estimate.

A separate replay of retained one-minute OHLC

The matching production collector records were retrieved after the event scan. Their symbol is OANDA:XAUUSD, timeframe 1 minute, confirmed flag true. All 16 minutes from 00:04 through 00:19 UTC are present, with valid high/low ranges and consecutive one-minute boundaries. The raw bars and receiver timestamps are preserved in the same evidence JSON. This is a computational cross-check of stored nominal OHLC, not an independently authenticated external data feed.

The replay is conditional on the reported activation at 00:10:30.476 UTC. The partial 00:10 candle has high 4,139.170 and low 4,137.000, containing neither SL nor TP1, so it introduces no target-versus-stop conflict. Later eligible bars have a maximum high of 4,139.190, below the original 4,139.681 stop. No nominal stop touch appears before any of the three target observations.

The target bars occur before their corresponding indicator report timestamps. That distinction matters: the time a target event is reported is not necessarily the first price-touch instant. One-minute OHLC brackets the touch within a bar and does not recover its exact tick time. Here the reported order is supported by the retained bar sequence, but the script’s complete entry algorithm has not been reproduced.

The explicit rule is low at or below a SELL target for a nominal target touch, and high at or above the original stop for a nominal stop touch. A stop occurring first would contradict a target-first outcome. A candle containing both levels would remain ambiguous unless finer verified observations resolved the order. No TP-first preference, interpolation or gap filling is allowed. This case has no such same-bar conflict. The collector shares the terminal’s reporting infrastructure, so this is not independent source authentication, a broker fill audit or a P&L calculation.

The practical value of Gold Terminal

CyGuru Gold Terminal makes this comparison possible by keeping the original levels, engine, timeframe and reported progress together. Its useful role is to make the reader ask which signal a target belongs to, when activation was reported, and whether the later messages retain the original plan. That is more informative than an isolated BUY, SELL or TP3 badge.

Use Signal Explorer to compare the wider retained population, the Hazem dossier for the model’s research context, and Strategy Lab for defined comparisons. This selected success does not establish independence, validate the whole engine or predict future profit.

Primary source and preserved evidence

The source is CyGuru Gold’s production receiver table, read through Sites database access at the fixed cutoff. Current /api/terminal/signals source reads this same production table. Public HTTP access returned 403 in this environment; a successful public-feed readback is not claimed. Synthetic tests and unrelated archived CY66 history are excluded. The sanitized snapshot retains every available original event object for this signal, full IDs, individual receiver times and the overlapping BUY context, without secrets.

Full selected signal ID: 66-HAZEM-V1|OANDA:XAUUSD|5|1794269100000

Inspect the dated original event snapshot → · Production feed →

Selected historical research. Nominal reference observations; no verified broker execution or P&L. Not a current trade instruction.