Will "Spider-Man: Brand New Day" score at least 85 on the Rotten Tomatoes Tomatometer?
| Predicted at | 2026-07-15 11:04 UTC |
|---|---|
| Prediction | 61.0% |
| Market (at prediction) | 86.0% |
| Market (live) | — |
Analysis
Trimmed mean 61% vs market 86% is a 25-pt gap, but the gap stems from a weighing dispute on an unreleased film with zero critic reviews — pure genre forecasting under high variance. I verified no late-breaking information exists that the market could be exploiting; both sides are working from the same public data. The agents likely over-anchor on the broad recent-MCU base rate relative to the much stronger franchise-specific prior (3/3 predecessors at 90%+, same creative team, positive screenings, early-review skew), and our system's documented failure mode is under-predicting YES and hedging toward 0.5. I therefore lift my fair value to ~70%. That still implies a ~16-pt NO edge, but the mandatory kill attempt did not fail on verifiable grounds, the market's implied distribution is defensible, sibling liquidity is thin (little smart-money signal either way), and this falls in our no-edge 'other' category (52% hit rate). Ambiguity is irreducible until the embargo lifts — SKIP.
Key Evidence
No reviews exist yet (embargo lifts ~week of release; resolution is 3 days post-release). Franchise prior: all 3 Holland Spider-Man films 90-93% RT; director Cretton's Shang-Chi 91-92%; same writers; test screenings 'gangbusters' with a divisive-ending caveat. Counterweight: only 2 of last ~7 MCU films cleared 85 (Thunderbolts 88, F4 87-89), with well-received entries landing 77-84. Verified no late-breaking premiere/review info that the market could be pricing in.
Risks
It's August 3 and a NO trade lost: the film reviewed like its three predecessors (~90% RT), boosted by the 3-day post-release early-review skew, and the 'divisive ending' concern from test screenings didn't materialize in critic consensus — exactly the modal outcome the franchise-specific reference class predicted.
Timestamped via OpenTimestamps · Block 958152
SHA-256: f93f55e244279b11c0f4686f5573526439e7624bcbea77de00639991937b3d40
Download content.md · Download .ots proof
Verification needs both files. Download them, confirm the text’s hash with
sha256sum content.md, then check the proof against
it — drag both into opentimestamps.org
or run ots verify content.md.ots locally. The
.ots proof anchors that SHA-256 into a Bitcoin block,
showing this analysis existed before the outcome was known.
This page is for informational and research purposes only. Nothing here constitutes financial advice. Do not make investment decisions based on these predictions.