Prediction evidence
neutralPolicy v1.0Source post
Published 8 Sept 2026, 14:35 UTC · fetched 13 Oct 2026, 05:55 UTC
Michaël van de Poppe
@CryptoMichNL
Quoting · 8 Sept 2026, 11:35 UTC · context given to the AI
I'm looking at a test at $78,000 for #Bitcoin. This is a zoomed out chart, meaning that if the $78,000 level is lost, I'm expecting to see a deeper correction taking place towards the $74,000 regions. That's going to be a phenomenal opportunity across the board. https://t.co/svQn6jhkgVThat's the test of #Bitcoin which I wanted to see here. Expecting to see that we're not losing this level and, as a matter of fact, are going to see another leg upwards towards the highs. If this is lost, $74,000 is next. https://t.co/7VkJ1JrRla https://t.co/u3T5n3ERidView original on X ↗
How this was scored
Deterministic: the same prices and policy always give the same result
- Baseline: first BTC price at or after publication, $78,539 at 8 Sept 2026, 15:00 UTC.
- Evaluation: price at the end of the 24 hours horizon, $78,942 at 9 Sept 2026, 15:00 UTC.
r = 78941.83 / 78538.62 − 1 = +0.51%- Direction d = +1 (bullish), so
d × r = +0.51%against a neutral band of ±1.00% → neutral
Only the end-of-horizon price counts. A brief move followed by a reversal is not a success. Read the methodology
AI interpretation
Uses only text available at publication time
- Asset
- Bitcoin (BTC)
- Direction
- ▲ Bullish
- Intent
- explicit
- Horizon
- 24 hours (default, none stated)
- Evidence span
- “Expecting to see that we're not losing this level and, as a matter of fact, are going to see another leg upwards towards the highs.”
- Confidence
- 80%
- Review state
- auto accepted
- Model / prompt
- gemini-3.1-flash-lite · prompt-v1
Outcome record
- Status
- neutral
- Baseline price
- $78,539
- Evaluation price
- $78,942
- Move
- +0.51%
- Neutral threshold
- ±1.00%
- Price provider
- coinbase
- Evaluated at
- 13 Oct 2026, 06:11 UTC
- Policy version
- v1.0
Request a correction
Think the interpretation or outcome is wrong? Sign in with X to request a correction, so reviewers know who is asking.
Sign in to request a correction