10 NOVEMBER 2026 · HAZEM 5M SELL · OHLC ORDER UNRESOLVED
A TP3 Report in a Two-Sided Minute: The Hazem Stop–Target Ambiguity
The indicator reports its third target 35 seconds after activation. The retained one-minute candle contains both the original stop and all three targets. That distinction must remain visible: the message is documented, while an independent target-before-stop outcome is not established.

Open CyGuru Gold Terminal — inspect original plans and reported event trails →
The report and the unresolved question
The selected production signal is a 66-HAZEM-V1 CHoCH SELL for OANDA:XAUUSD on the five-minute timeframe. Creation is timestamped 10 November at 13:25 UTC / 17:25 Dubai. The source reports activation at 13:29:40.646 UTC and TP3_HIT at 13:30:15.658 UTC / 17:30:15.658 Dubai. There are no individual TP1_HIT or TP2_HIT messages in the retained lifecycle.
The public-feed observation cutoff is 13:43:35.210 UTC / 17:43:35.210 Dubai on 10 November. Three original production events are retained for this identity, with no reported stop-loss, cancellation or invalidation. That establishes the contents of the indicator's reference report. It does not resolve whether the underlying price touched the original stop before a target inside the volatile minute.
This is a selected favorable indicator report with an ambiguous nominal OHLC outcome, not an independently verified trading success. Missing messages or an unrecorded intraminute path cannot be replaced with a favorable assumption.
Full signal ID: 66-HAZEM-V1|OANDA:XAUUSD|5|1794317100000
Freeze the original plan before examining the result
| Field | Reference price | Distance from entry | Distance / R |
|---|---|---|---|
| Entry | 4,072.767 | Reference | — |
| Stop | 4,078.435 | 5.668 above | 1.000 |
| TP1 | 4,066.356 | 6.411 below | 1.131 |
| TP2 | 4,061.111 | 11.656 below | 2.056 |
| TP3 | 4,054.395 | 18.372 below | 3.241 |
All three messages repeat the five original prices exactly. Signal ID, engine, symbol, timeframe, direction, setup, creation timestamp and expiry are also consistent. The expiry is 11 November at 06:40 UTC / 10:40 Dubai. No later target is substituted into the creation record to improve the appearance of the outcome.
The delivered engine/version identifier is 66-HAZEM-V1 and schema_version is 1. A Pine source hash and full indicator input configuration are unavailable. CHoCH is the setup label supplied by the source; this audit does not reconstruct every internal structure or filter decision. Consistent event fields demonstrate stable reported levels, not continuous access to the script's internal state.
Thirty-five seconds is a report interval
| Event | Source UTC | Source Dubai | Receiver UTC |
|---|---|---|---|
| SIGNAL_CREATED | 10/11/2026, 13:25:00.000 | 10/11/2026, 17:25:00.000 | 10/11/2026, 13:25:04.053 |
| Activation reported | 10/11/2026, 13:29:40.646 | 10/11/2026, 17:29:40.646 | 10/11/2026, 13:29:40.782 |
| TP3_HIT | 10/11/2026, 13:30:15.658 | 10/11/2026, 17:30:15.658 | 10/11/2026, 13:30:44.872 |
Activation follows creation by 4 minutes 40.646 seconds. TP3 follows activation by 35.012 seconds, and follows creation by 5 minutes 15.658 seconds. These differences describe source-event timestamps. They are not verified order execution times or a measured duration for earning a return.
Activation arrives at 13:29:40.782 UTC, 0.136 seconds after its source time. TP3 arrives at 13:30:44.872, a gap of 29.214 seconds. This longer delivery gap is preserved rather than hidden; neither clock provides the missing tick order or a system latency guarantee.
The TP3 message contains no exact TP1 or TP2 touch times. A higher milestone can be reported without separate lower-target messages. The correct record keeps those times unavailable; it does not divide the 35-second interval into imagined stages. The FILL suffix in the activation ID is the script's label and does not establish a broker fill.
The one-minute replay reaches an ambiguity boundary
The signal-specific audit endpoint returns 139 consecutive one-minute bars, with zero missing clock slots in the requested window, declared as OANDA:XAUUSD. The source is the site's direct TradingView collector. This is nominal OHLC from the same reporting infrastructure, rather than independently authenticated external price evidence. Complete minute coverage does not recover tick order.
| Minute | Open | High | Low | Close |
|---|---|---|---|---|
| 13:29–13:30 | 4,071.765 | 4,073.625 | 4,070.825 | 4,072.035 |
| 13:30–13:31 | 4,072.050 | 4,081.005 | 4,039.720 | 4,050.505 |
| 13:31–13:32 | 4,050.415 | 4,059.480 | 4,047.595 | 4,055.140 |
The partial activation minute contains neither the original stop nor TP1. The next minute has a high above the 4,078.435 stop and a low below TP1, TP2 and TP3. Its opening price lies between the stop and first target. Both stop-first and target-first paths are compatible with those four OHLC values. The close below TP3 does not choose between them.
The explicit replay rule for a SELL is low at or below a target for a nominal target touch, and high at or above the original stop for a nominal stop touch. A stop in an earlier bar would contradict a target-first claim. When both levels occur in the same bar, as here, the outcome is ambiguous unless finer verified observations establish the order. This article awards neither a target-first success nor a stop-first failure from that bar.
The TP3 source report occurs 15.658 seconds into the minute. The completed candle describes the whole minute, including prices that may have occurred after the report. Neither its high nor its low can be placed before that timestamp from OHLC alone. The following minute's lower range also cannot erase a possible earlier stop. No interpolation, imagined intrabar path or assumption that the target was first is permitted.
The indicator may apply rules that differ from a fixed original-stop replay, but the delivered record does not document enough internal state to reproduce such a difference. It would be speculation to explain the discrepancy with a moved stop, a particular fill convention or a news cause. Finer timestamped prices and the applicable script rules remain the evidence needed to resolve the issue.
Overlapping records keep the sample in context
A separate five-minute PULLBACK BUY, ID ending 1794314400000, was created at 12:40 UTC, reports activation at 13:02:15.506 and TP1 at 13:06:15.505. It remains a separate active reference record at the feed cutoff, with no reported TP3 in that snapshot. Its direction differs from the selected SELL, and its earlier TP1 is not evidence for this SELL's targets.
A fifteen-minute PULLBACK SELL, ID ending 1794317400000, was created at 13:30 UTC and has no activation message at the cutoff. It is not counted as a completed trade. Both proposals overlap the selected lifecycle in clock time. Shared market and indicator exposure make them dependent observations; selecting the favorable TP3 message establishes no overall win rate or independence.
Reference geometry cannot establish money earned
The original entry-to-stop distance is 5.668. The nominal target-distance ratios are approximately 1.131R, 2.056R and 3.241R. Here R is a price distance only. In particular, a 3.241R target printed in a report is not a realized account return when the stop-versus-target order is unresolved.
Position size, executed entry, partial exits and actual stop handling are unavailable. Broker fills, commissions, spread, slippage, financing and P&L remain unverified. No earning claim, future-profit claim or causal explanation for the price movement is made.
Why Gold Terminal helps even when the answer is unresolved
CyGuru Gold Terminal retains original plans and event identities so the reader can ask a harder question than whether a green TP3 badge appears. Its practical benefit here is the ability to compare the reported milestone with the original stop, source time, receiver time and retained candle evidence.
Use Signal Explorer to inspect the wider retained population and the Hazem dossier for related cases. The Strategy Lab framework requires an explicit ambiguity treatment. Preserving an unresolved answer is part of a useful audit, because it states exactly which additional evidence could change the conclusion.
Sources and preserved evidence
Primary sources are the production signal feed, matching production receiver rows read through Sites database access, and the signal-specific stored OHLC response. The sanitized snapshot retains every available original event for this identity, receiver times, full IDs, observation cutoff, overlapping records and raw collector response. Synthetic tests and unrelated archived CY66 data are excluded; credentials and private information are not published.
Inspect the dated sanitized evidence JSON → · Production signal feed →
Selected indicator-reported outcome. Nominal OHLC ordering unresolved; execution and costs unverified. Not a current trading instruction.

