10 NOVEMBER 2026 · HAZEM 15M SELL · PULLBACK

Three Timed Targets, Two Opposite Setups: A Hazem 15-Minute Gold Audit

A fifteen-minute SELL reports all three targets over 68 minutes after activation. During that interval, a separate five-minute BUY reports a stop. Keeping both identities visible makes the favorable outcome more useful as research.

Gabriel Nicolaev — CyGuru
Published 10 November 2026 · 11:49:25 UTC / 15:49:25 Dubai (UTC+4)

Open CyGuru Gold Terminal — inspect original signal plans and event histories →

A completed report with a defined evidence boundary

The production record is a 66-HAZEM-V1 PULLBACK SELL on OANDA:XAUUSD, timeframe 15 minutes. Its creation time is 10 November at 09:45 UTC / 13:45 Dubai. Activation is reported at 09:58:00.545 UTC. Separate TP1_HIT, TP2_HIT and TP3_HIT messages follow, with TP3 at 11:06:50.585 UTC / 15:06:50.585 Dubai. Individual lower-target times are available in this case.

The fixed public-feed cutoff is 11:43:48.129 UTC / 15:43:48.129 Dubai on 10 November. Five matching production receiver rows were checked subsequently, at 11:45:16 UTC. They contain no stop-loss, cancellation or invalidation for this identity. This supports a selected indicator-reported reference outcome, while leaving possible upstream message loss and broker execution unverified.

Full signal ID: 66-HAZEM-V1|OANDA:XAUUSD|15|1794303900000

The original proposal remains the measuring stick

Entry, stop and all three targets match the creation message exactly in every subsequent event. Engine, signal ID, symbol, timeframe, direction, setup, creation time and expiry also remain consistent. The source expiry is 11 November at 03:30 UTC / 07:30 Dubai, later than the final target report. No revised target is used to explain the result retrospectively.

This freeze check examines the delivered history. It does not inspect the indicator's internal state continuously. The available version identifier is 66-HAZEM-V1 and schema_version is 1; a Pine source hash and complete input configuration are unavailable. The PULLBACK label identifies the reported setup family, but cannot by itself reconstruct all structure, trend or filter decisions behind it.

The lifecycle has two clocks

Activation follows creation by 13 minutes 0.545 seconds. The reported interval from activation to TP3 is 68 minutes 50.040 seconds; creation to TP3 is 81 minutes 50.585 seconds. TP1 follows activation by 7 minutes 30 seconds, TP2 follows TP1 by 22 minutes, and TP3 follows TP2 by 39 minutes 20.040 seconds. These are differences between source-event timestamps, not independently measured execution durations.

The activation reaches the receiver at 09:58:02.908 UTC, 2.363 seconds after its stated source time. TP3 arrives at 11:06:50.748, a gap of 0.163 seconds. Those observations describe these messages and provide no latency guarantee. The activation identifier's FILL suffix is the script's naming convention; the payload reports activation, not an authenticated broker transaction.

A separate calculation on retained one-minute bars

The signal-specific audit endpoint returns 239 consecutive one-minute bars with zero missing clock slots in its requested window. The declared symbol is OANDA:XAUUSD, matching the signal. The 69 bars intersecting reported activation through the TP3 report have a maximum high of 4,088.940, below the original 4,092.126 stop. Their stored ranges therefore contain no nominal stop touch over that comparison interval.

The calculation is conditional on reported activation. For a SELL, a low at or below a target counts as a nominal threshold observation, and a high at or above the original stop counts as a nominal stop observation. A stop first would contradict target-first classification. If the same bar contains both, the result remains ambiguous without finer verified observations. No favorable intrabar order, interpolation or backfill is assumed.

The partial activation minute, 09:58–09:59, contains neither the stop nor TP1. Its unknown intraminute sequence does not decide those milestones. The later target bars occur in the same order as the target messages, without same-bar stop conflicts. This supports nominal ordering within the retained series.

Each target message occurs inside its corresponding minute, before that bar closes. The completed bar cannot certify that its eventual low occurred before the exact report timestamp. In particular, the 11:06–11:07 bar brackets a nominal TP3 observation but does not supply an independently verified touch at 11:06:50.585. Finer observations would be required for that claim.

The collector shares the terminal's TradingView reporting infrastructure. This is a computational cross-check, not independent authentication of the source prices or reproduction of the full entry algorithm. No generated or unverified historical candle chart is offered as proof. The raw collector response and receipt times remain in the public snapshot for inspection.

The opposite BUY prevents a one-sided reading

A separate five-minute SWEEP BUY, full ID ending 1794305400000, was created at 10:10 UTC. It reports activation at 10:16:00.505 and STOP_LOSS_HIT at 10:20:15.476, between this SELL's TP1 and TP2 reports. Its original reference entry is 4,082.230 and stop 4,079.892. This adverse observation belongs to a different identity and is retained as context.

A further fifteen-minute PULLBACK SELL, ID ending 1794306600000, was created at 10:30 UTC and closed at 11:30:00.390 without reported activation. An earlier fifteen-minute CHoCH SELL, ID ending 1794302100000, was created at 09:15 and closed at 10:15:00.600 without reported activation. Their proposal windows overlap the selected case; they are not counted as extra completed successes.

The selected SELL does not erase the stopped BUY or turn unactivated proposals into trades. Shared market exposure, engine and overlapping time make these dependent observations. A favorable case article supplies neither an overall win rate nor evidence that the next setup will succeed.

Reference reward is not money earned

The original stop distance is 5.012. Target distances of 5.622, 10.221 and 16.354 imply approximately 1.122R, 2.039R and 3.263R. These figures measure the geometry of the proposal, rather than a realized account return. They do not reveal position size, actual entry, partial exits or whether an order could execute at the displayed thresholds.

Broker fills, commissions, spread, slippage, financing and P&L are unverified. Even nominal target-before-stop observations cannot establish those execution details. No money earned, causal market explanation or future-profit claim is inferred from the selected record.

The practical use of Gold Terminal

CyGuru Gold Terminal brings original levels, engine identity, timeframe and reported progress into one inspectable record. Here its benefit is concrete: a reader can distinguish a fifteen-minute SELL from an overlapping five-minute BUY, compare event and receiver clocks, and check that the plan stayed fixed.

Use Signal Explorer for the wider retained population, the Hazem dossier for model context, and Strategy Lab for declared comparisons. The useful result is a reviewable hypothesis and evidence trail, rather than confidence drawn from a target badge alone.

Primary sources and preserved evidence

The sources are the production /api/terminal/signals feed, matching production receiver rows read through Sites database access, and the signal-specific /api/terminal/audit-history collector response. Synthetic tests and unrelated archived CY66 data are excluded. The sanitized snapshot preserves all five original events, full identities, receiver times, context records and raw OHLC response without credentials or private information.

Inspect the dated sanitized evidence JSON → · Production signal feed →

Selected historical reference observations. Broker execution and costs unverified. Not a current trading instruction.