A9 PREDICT

A9 Predict

Changelog

Changes associated with this build.
v0.2.0Build identifier supplied

Build date · Eastern: Oct 25, 2026, 1:41:30.352 PM EDT

Technical build details
Commit
ef695042b6cc7b8d0132bc9eb2a0a1890d123d57
Version source
Running build metadata

Build metadata does not confirm production deployment or service health.

v0.2.0 This build

Keep this round's issued prediction readable, with a separate fresh entry comparison when matching evidence is available.

Added

  • One-contract entry estimate from matching fresh forecast, quote, depth and timestamped series fees; no orders are placed.
  • Current Kalshi round, threshold, close countdown and timestamped public quotes, separate from immutable A9 forecasts.
  • Eastern-day count of unique rounds with acknowledged forecasts and saved settlement status; real trades remain unavailable without fills.

Fixed

  • Saved history stays historical, including records from an open round; it does not show a current pick or start quote refreshes.
  • An issued prediction stays visible until its round closes, with its original probability and an explicit stale-input label after freshness expires.
  • Invalid reference timestamps, conflicting records and different-round quotes cannot supply a selection or entry comparison.
  • Forecast-only pilots can use the approved budget while learning stays off.
  • Quotes retire when stale, closed, mismatched or incomplete; an old forecast is never relabeled as current.
  • Bounded response parsing and shared in-flight public reads prevent simultaneous viewers multiplying upstream work.

Changed

  • Target prices spell out At least versus Above from the contract comparison; original Kalshi wording and rules remain in Details.
  • Untracked no-pick counts and the absence of a trading connection are labeled explicitly instead of appearing as a temporary data outage.
  • Canonical ACE9 Living Glass theme, compact historical evidence, and Eastern Time throughout.
  • Accessible version dialog groups Added, Fixed and Changed notes for this exact build.
  • Page reads do not start forecast collection, learning or order execution.

Tracked question

Shipping targeted in Hormuz on September 25, 2026?

A9 gives this a 58% chance of happening. That's somewhat less likely than the betting market thinks (62%) — a 4-point disagreement. A9 researched this on the web before forecasting.

Market 62%Polymarket
A9 Predict 58%high confidence

Jev on its own said 47%

-4 pts vs market
Leans YES

Why A9 thinks this

The evidence, separated.

Web research · quality 75/100

Authoritative maritime organizations (IMO, MARAD) and UKMTO-backed reporting show an active pattern of projectile strikes and security incidents affecting commercial shipping in and around the Strait of Hormuz in mid–late September 2026. That pattern establishes elevated baseline risk for Sep 25, 2026. However, as of 2026-09-24 there is no public, credible intelligence or authoritative advisory that specifically names Sep 25, 2026 as the date of a planned strike or seizure. The single largest unknown is whether any actor has decided on Sep 25 as the specific date — that intent/timing is not visible in open-source reporting. The market would flip to 'Yes' only if multiple credible sources (e.g., UKMTO, MARAD, IMO, navies, vessel owner/operator statements, satellite/visual evidence) report a qualifying kinetic strike or forceful seizure occurring within the defined area on Sep 25 (GST).

For

Multiple credible maritime authorities and press outlets report a series of projectile strikes and security incidents in and around the Strait of Hormuz in mid–late September 2026 (e.g., reports for 16–21 Sep), establishing a recent pattern of attacks on commercial shipping in the defined area.

U.S. Maritime Administration (MARAD) has an active advisory (2026-011) warning of ongoing Iranian attacks on commercial vessels in the Persian Gulf, Strait of Hormuz and Gulf of Oman (advisory active Sep 9, 2026 – Mar 8, 2027), which documents elevated, sustained risk to commercial ships transiting the area.

The International Maritime Organization (IMO) has issued repeated statements in 2026 condemning attacks in and around the Strait of Hormuz and has publicly verified dozens of attacks since Feb 28, 2026, indicating institutional confirmation of a high-threat environment.

The United Kingdom Maritime Trade Operations (UKMTO) and multiple maritime-news outlets published incident notices in mid–late September 2026 reporting vessels hit by unknown projectiles while transiting the Strait of Hormuz (examples reported 16–21 Sep 2026), showing attacks continue to occur on short notice.

Against

As of the last available public advisories and reporting (checked Sep 24, 2026), I find no public, credible intelligence or authoritative advisory that specifically names or schedules Sep 25, 2026 as a date for a planned attack on commercial shipping in the defined area.

Authoritative warnings (MARAD, IMO, UKMTO) and maritime-traffic monitoring have been issuing frequent advisories and guidance; that elevated transparency and the active presence of naval/maritime authorities can deter or disrupt planned strikes (i.e., increased monitoring/escort reduces operational success probability).

Some recent UKMTO reports have been issued with delay or limited details; that pattern means not every actionable intent is publicly signaled in advance — absence of a public warning does not prove absence of a plan, and conversely public advisories can reflect preventive measures that reduce near-term strike likelihood.

Unknown

Whether any actor (state or non-state) has the intent and operational plan to carry out a kinetic strike or forceful seizure of a commercial ship specifically on 2026-09-25 within the Persian Gulf, Strait of Hormuz, or Gulf of Oman — this intent/timing is not publicly observable in the available open-source reporting as of 2026-09-24.

What would change A9's mind

  • UKMTO publishes an incident advisory dated 2026-09-25 reporting a commercial vessel within the defined area was struck or forcefully boarded (with time between 00:00–23:59 GST).
  • MARAD, IMO, the U.S. Navy, Royal Navy, Joint Maritime Information Centre (JMIC) or another comparable maritime authority issues a dated (2026-09-25) advisory or warning confirming a kinetic strike or seizure of a commercial ship in the defined area that occurred on Sep 25 (GST).
  • Contemporaneous corroboration on Sep 25 from multiple independent credible sources — vessel owner/operator statements, AIS track anomalies corroborated by satellite imagery, maritime authorities’ situation reports, and reputable media — that together confirm occurrence, location (inside the defined area), and timing on Sep 25 (GST).
  • Clear visual/sensor evidence (video, satellite imagery) dated Sep 25 showing a direct impact on a commercial vessel in the specified area, or footage/communications showing forceful boarding and takeover of a commercial vessel on Sep 25.

Probability history

A9 never rewrites the past.

MarketA9Me
58%Initial read

Authoritative maritime organizations (IMO, MARAD) and UKMTO-backed reporting show an active pattern of projectile strikes and security incidents affecting commercial shipping in and around the Strait of Hormuz in mid–late September 2026. That pattern establishes elevated baseline risk for Sep 25, 2026. However, as of 2026-09-24 there is no public, credible intelligence or authoritative advisory that specifically names Sep 25, 2026 as the date of a planned strike or seizure. The single largest unknown is whether any actor has decided on Sep 25 as the specific date — that intent/timing is not visible in open-source reporting. The market would flip to 'Yes' only if multiple credible sources (e.g., UKMTO, MARAD, IMO, navies, vessel owner/operator statements, satellite/visual evidence) report a qualifying kinetic strike or forceful seizure occurring within the defined area on Sep 25 (GST).

a9-predict-0.3.0 · 3c088ffc13906f87565ef4739a71d907ac4531ed73a1955a6fdffd12d6185017