XAU / USD PROVIDER QUOTE

“Understand the forces behind gold.
Let discipline guide every decision.”

Gabriel Nicolaev - CyGuru
Gabriel Nicolaev - CyGuru
GLOBAL EDITION / ENGLISHGold market intelligenceIndependent intelligence by Gabriel Nicolaev – CyGuru
Explore CYGURU GOLD Menu +
Research Lab / Selected production evidence

13 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M SELL · PULLBACK

A Gold Pullback Reported TP3 Four Minutes After Its First Collector Range

A five-minute gold PULLBACK SELL retained separate activation and all three target reports. Its ten-minute reported lifecycle also shows why the first collector threshold, the source message and the receiver timestamp must remain distinct.

A gold precision caliper frames three descending golden steps on midnight navy stone.
Conceptual editorial illustration.

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, SELL and PULLBACK were recorded. A separate script build hash was unavailable.

Signal ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794573600000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794573600000|1794575700176|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.

Original SELL levels and reference distances in USD per troy ounce
FieldLevelDistanceOriginal risk multiple
Entry3891.494——
Original SL3892.9851.491 adverse1.000R
TP13889.8161.678 favorable1.125R
TP23888.4433.051 favorable2.046R
TP33886.7604.734 favorable3.175R

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.

Source and receiver times, UTC
Recorded stageSource timeReceiver 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 11 OANDA:XAUUSD one-minute bars. The audited window has no missing minute slots. For a SELL, a low at or below a target counts as a nominal touch and a high at or above 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 maximum retained high in that window is 3892.755, below 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.

First collector minutes containing each target threshold
ThresholdMinute open, UTCHighLow
TP12026-11-13T13:07:00+00:003890.2503888.680
TP22026-11-13T13:08:00+00:003889.6703888.270
TP32026-11-13T13:11:00+00:003887.8303886.270

Twenty-five minutes waiting, then ten minutes of reported activation

The proposal was created at 12:40 UTC on 13 November 2026. Activation was reported at 13:05:00.176, 25 minutes and 0.176 seconds later. TP1 followed at 13:08:00.204, TP2 at 13:10:00.204 and TP3 at 13:15:00.176. Unlike an incomplete target sequence, this case preserves a distinct source event for every target. The activation-to-TP3 interval is exactly ten minutes on the source clock.

The waiting period matters because a proposal and an active reference observation describe different states. A chart spanning creation through completion could include movements that preceded the reported activation. This audit therefore freezes the plan at creation but starts its ordering diagnostic in the activation minute. The retained minute begins 0.176 seconds before activation; its range contains neither the original stop nor TP1, so that partial-minute uncertainty does not create a stop/target ordering conflict.

Three clocks, with different questions

The first collector minute containing TP1 opens at 13:07 UTC; TP2 first appears in the 13:08 minute and TP3 in the 13:11 minute. Those are completed one-minute ranges, not exact touch timestamps. The source reports arrive at 13:08, 13:10 and 13:15 respectively. In particular, TP3 has a four-minute difference between the first containing minute’s opening and its report. That does not establish a four-minute network delay.

The receiver column measures when each source message was stored. A completed collector bar answers whether a threshold was inside that minute’s range; the indicator event answers when that script reported its milestone. Explaining their difference would require the original script settings and evaluation logic. Neither the shared engine name nor this successful endpoint establishes the cause of the timing difference.

The narrow clearance deserves as much attention as TP3

The original SELL risk distance is 1.491 dollars per troy ounce. The three favorable reference distances are 1.678, 3.051 and 4.734, approximately 1.125R, 2.046R and 3.175R. The highest collector price after the activation-minute boundary is 3892.755, just 0.230 below the original stop at 3892.985. That margin is about 15.4% of the original risk distance. The observed clearance is a property of this retained quote series, not a guarantee that an executable ask price or another feed would have stayed below a stop.

All five messages preserve the same entry, stop, targets and identity fields. Keeping those original levels prevents a later target result from silently changing the denominator used to describe the plan. It does not establish a realized return: position size, partial exits, actual execution prices and transaction costs remain unavailable. The collector’s first TP3-containing bar at 13:11 has a low of 3886.270, while the original TP3 is 3886.760.

An opposing SWEEP was active in the same price episode

A separate 15-minute Hazem SWEEP BUY, signal 66-HAZEM-V1|OANDA:XAUUSD|15|1794574800000, reported activation at 13:09:50.314 UTC. Its entry was 3887.474, stop 3884.723 and TP3 3897.515. At the observation cutoff it remained active without a target report. Its reported active window overlaps the final part of this SELL case. The SELL reaching TP3 does not decide the BUY outcome, and the two setups should not be counted as independent experiments.

The terminal is useful here because it keeps each plan attached to a full identity, timeframe and event sequence. A reader can compare conflicting directions, inspect unchanged levels and separate an active setup from a completed reported observation. For review, preserve both identities in the same market episode and use a consistent inclusion rule across favorable and adverse outcomes. This article deliberately selects one favorable case; it supplies no population win rate or forecast.

The snapshot preserves 1 other record 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

WRITTEN BYGabriel Nicolaev — CyGuru