Horizon AI
Language
Italiano

XAUUSD · 2026-09-24 · 00:28 UTC · Level reached

Neither invalidation condition was met by 21:30 UTC

The reading stated in advance two conditions that would invalidate it: an hourly close above 4,318.9, or a sweep of the 4,273.8 shelf followed by a close back above 4,304.9. Neither was met by 21:30 UTC.

Test the engine All readings

Issued
2026-09-24 00:28 UTC · market hours
Outcome
Neither invalidation condition met by 21:30 UTC
Checked on
PAXGUSDT, GC=F, hourly bars
Record
Chosen with the outcome known
Updated
2026-10-02

01 — Analysis

The analysis, as published

Instrument
XAUUSD
Timeframe
H1 · H4 context
Issued
2026-09-24 00:28 UTC
Engine
Meridian Engine

1What the market did

At the time of issue XAUUSD had closed at 4,288.4, with volatility compressed to an extreme: the ATR percentile stood at 0.00 on the four-hour chart and 2.00 on the hourly.

The four-hour chart had printed three consecutive lower highs (4,396.8, 4,375.9, 4,371.1, the last of them at 16:00 UTC on 22 September), and the hourly chart repeated the same shape: a lower high at 4,318.9, then a low at 4,274.4. On 23 September the price ran the of equal lows at 4,291.3 with a 0.87 times the ATR, and went on to a lower low instead of rejecting.

2Which events moved it

No single event moved the price in the window, and, unlike the BTCUSD analysis of 9 August, no macro data was available to this reading at all. What was and was not in hand:

  • Economic calendar. Live. 17 scheduled US events inside the window, one of them still unresolved at the time of issue. The pending release was the US jobless-claims print at 12:30 UTC.
  • Macro data. None. Where the BTCUSD analysis had rates, flows and positioning, this one had nothing. It rests on structure and liquidity alone, which is a narrower base, and the difference is stated rather than hidden.
  • Structure. Three lower highs on the four-hour chart, one on the hourly, and a new low after the sweep. Aligned across both timeframes.
  • Liquidity. A pool of equal lows at 4,291.3 run and passed through, with the next pool at 4,273.8 and a cluster of three at 4,253.4.

Not all of the structure carried the same weight, and the run recorded the difference: one break was of quality, the two that followed were graded indeterminate and . On their own they decide nothing.

3Two accounts of the same facts

Deep low sweeps had been bought repeatedly. The sweep of 22 September took 4,322.4 at 0.91 times the ATR and was followed by roughly 50 points up. Compression at a multi-day low is as consistent with a base being built as with a move continuing, and the price closed at 4,288.4, back above the low it had just made, rather than accepting beneath it. The two structure breaks that extended the move down were graded indeterminate and drift: thin participation. The reading records this account as the counter-case to the continuation read.

4Where the levels sit

Relevant price levels at issue
LevelPriceWhy it is relevant
H4 lower high4,371.1Third consecutive lower high on the four-hour chart
top4,318.9Hourly lower high and high cluster; top of the 4,300.1–4,318.9 band
Snap-back reference4,304.9The level the failed breakdown of 22 September reclaimed
Close at time of issue4,288.4Reference price
Equal-low pool4,273.8Nearest pool below the price
H4 cluster4,253.4Three members, from 16 September

The low printed after the sweep, 4,274.4, sat just above the pool at 4,273.8: the nearest level below the price was less than a point away from a low the market had already made. Every level in this table comes from the run named at the foot of this document; the outcome below was checked against two public series.

5What would invalidate the reading

The reading ceases to be valid if either of two conditions is met:

  • an hourly bar closes above 4,318.9, the top of the 4,300.1–4,318.9 band, breaking the chain of lower highs;
  • the price first sweeps the equal-low at 4,273.8 and then closes back above 4,304.9: a failed breakdown, repeating the pattern of 22 September.

6What happened next

Written after the fact, at 21:30 UTC on the same day, against two public series that are not the feed this reading was produced from: Binance PAXGUSDT and COMEX gold futures. Both are quoted on their own scale; the figures here are restated on the scale of this reading, using the 23:00 bar of 23 September as the reference point. The two series agree with each other to within 0.70 on the day’s high and low.

Within the first two hours on PAXGUSDT (by the 03:00 UTC close on COMEX futures) the price reached 4,273.8; 4,253.4 was reached in the hour after 09:00 UTC, and the day’s low was 4,243. Neither of the two invalidation conditions was met. No hourly bar closed above 4,318.9: the highest close was 4,298.5, some 20 points below. The failed-breakdown condition came within 6.3 points of being met, and was not met. In the first hour after issue the price rose to roughly 4,302.

What this does not show. One reading checked against public data is not evidence about the next one. The conditions above were recorded, with a timestamp, before the outcome was known; conditions and outcome are published here together. The outcome can be checked independently on public data. The recording time cannot be proved by this page and has to be taken on trust; for that reason the conditions are published in full rather than as a summary of how they turned out. Conditions written loosely enough to fit any outcome would be worth nothing even with a timestamp.

Data and limits

Public series for checking gold: closes track the feed to within half a point, the extremes of a bar can differ by up to about four points, and every margin above is wider than that. One scheduled event inside the window was unresolved at the time of issue (economic calendar live from FXStreet). Market data from a Capital.com demo feed, bid basis; not a production feed. The levels are the levels the engine worked from; the outcome above was checked against two independent public series. No macro data was available to this reading. Two of the three structure breaks were graded indeterminate and drift: thin participation, published as such. Operational fields (direction, the run's internal operational parameters and position parameters) are omitted here, as in every published analysis.

Published by Horizon AI. Produced by Meridian Engine, run live-gold-20260924T0000Z, 2026-09-24 00:28 UTC. Outcome appended 2026-09-24 21:30 UTC. Internal operational fields omitted. No instruction to buy or sell. Not investment advice.

Terms used in this reading: Liquidity pool · Liquidity sweep · Displacement · Drift · Band · Shelf

The next readings are published when access opens. The first analysis is free with the waitlist code. Get the code →

Share this reading

02 — Other readings

The other published readings

invalidation condition price at issue hours before issue

All readings

03 — Availability

The first analysis is free with the waitlist code. The code arrives by email straight away.

Anyone who leaves an email receives a single-use code straight away, valid from the day access opens. The instrument is chosen then, from FX, metals, indices and crypto derivatives.

It is a market analysis of the chosen instrument and does not constitute investment advice: it does not consider the capital, experience or goals of whoever receives it. What one looks like, with the outcome checked against public data: the three readings in section 02.

Two messages, plus a third only if you ask for it: the confirmation with the code, one on the day access opens and, if you tick the optional box, «The weekly reading», with each new reading and then its outcome. One click unsubscribes. Questions are answered by a person, not a bot: contact@usemeridianai.com.

Form not showing? Open it in a new window.

Code conditions: one per person, single use, valid from the day access opens and for 30 days after. It covers the full price of the first analysis: nothing to pay for it. Tied to the address it was sent to, not transferable. Instrument of your choice among those covered: FX, metals, indices, crypto derivatives.

The form is operated by Tally (Belgium, EU); data is stored in Europe. The address is kept until the code expires, then deleted. Privacy notice.