Corrections policy
A reading that does not hold stays published with its outcome, with the same prominence as the others. An error in the text or the data is fixed on the page, and the correction is logged below with its date.
Updated 2026-10-02
When a reading does not hold
It is neither removed nor rewritten. Issue time, levels and conditions stay as published; the outcome is added below, with the time of the check and the series used. The BTCUSD reading of 9 August 2026, invalidated at 02:00 UTC by a condition stated at 00:09 UTC, is in the record like the others.
When a page contains an error
If the published text does not match the run report or the data, the page is fixed and a line is added to the log below: date, page, what changed and whether the outcome changes. Corrections never touch the issue time or the conditions stated before the outcome.
How to report an error
Write to contact@usemeridianai.com with the page and the point. Every report gets an answer; if the error is real, the correction goes into the log.
Corrections log
| Date | Page | Correction | Outcome |
|---|---|---|---|
| 2026-09-27 | BTCUSD, 9 August 2026 | The page listed four invalidation conditions; the run report contains three. The fourth was another condition of the run, not an invalidation. Removed from the text and the replay. | Unchanged: invalidated at 02:00 UTC |
| 2026-09-27 | BTCUSD, 9 August 2026 and XAUUSD, 24 September 2026 | Added that times refer to the close of the hourly bar. | Unchanged |
The next Meridian Engine readings are published with their conditions written in advance, and the outcome checked afterwards. Joining the waitlist gets you the code for a free first analysis straight away.
Get the code for your first analysis →General information only. Not an instruction to buy or sell.