Geopolitical prediction markets: actors, events and evidence

Define the measurable event

A geopolitical headline and a resolvable market question are different objects. The headline describes a situation; the market question names an actor, an action, a location, a time zone and a deadline, then states which evidence counts. For a US-Iran ceasefire contract snapshot checked on 10 October 2026, the rule stated that the market would resolve to No only if the United States took a qualifying military action against Iran by the specified date at 11:59 PM Iran Standard Time. Otherwise it would resolve Yes. That sentence already excludes several categories: threats, authorizations, announcements of force and munitions destroyed or intercepted before impact. It documents a settlement rule, not a result.

The second structural point is that a displayed price is usually the midpoint of the best bid and ask. When the spread exceeds 0.10, the last trade is shown instead. Neither number is an executable promise: a market order walks through multiple price levels and incurs slippage, and depth matters as much as the top of the book. Treat any price you see as an observation with a date, not as a forecast you can capture.

The event matrix: 7 fields that decide whether a claim is measurable

Before reading a market as evidence about the world, fill in 7 fields for the event being claimed: actor, action, location, time zone, executed versus announced, admissible sources, and conflicting reports. If any field is missing, you have a narrative, not a measurable event. The matrix below is an illustrative reading protocol, not an empirical study, and it uses no real casualty figures or intelligence claims.

Actor: who physically initiates. In the recorded rule, the qualifying actor is the United States. Action: the specific mechanism, limited to an air strike or a surface-to-surface missile strike that directly impacts Iran. Location: the terrestrial territory of Iran, including internal waters; maritime territory and airspace are not encompassed. Time zone: deadlines run on Iran Standard Time, so an 11:59 PM cutoff is not midnight in New York or London.

Executed versus announced: the rule states that any threat, authorization or announcement of force that has not been executed does not qualify. A statement that something will happen is an input to a narrative, not an event. Admissible sources: official information from the governments and militaries of the United States and Iran, plus a consensus of credible reporting. Conflicting reports follow an additional procedure, described below.

Illustrative case: announcement and interception both fail the qualifying-impact test

The case below is hypothetical and built only to show how the matrix separates a claim from a qualifying event. It invents no intelligence, no casualty count and no prediction. Read the outcome column as rule application, not as a forecast.

Notice what the matrix does not require you to know. You do not need to judge whether the announcement was sincere, whether the interception was technically impressive or whether commentators called the episode an attack. You only need to test each field against the captured clause. The recorded rule also adds that debris, fragments or wreckage from intercepted munitions landing on Iran do not constitute a military action regardless of damage incurred.

Conflicting reports follow a timed procedure

The recorded rule does not resolve ambiguity by whoever speaks loudest. Where sources conflict on occurrence, attribution or timing, the market stays open until the earlier of 2 moments: confirmation based on a consensus of resolution sources, or 3 full calendar days in Iran Standard Time from the first credibly reported evidence of the action. If that window would extend past the end date, the market stays open so the 3 days can pass. At the end of the third day, if reports still conflict, the incident is adjudicated on the totality of information available at that time, and no single statement or denial governs where the totality contradicts it.

That is a procedure with a deadline, not a truth-finding mission. For a reader auditing a claim, the practical consequence is to log dated evidence rather than assert that a consensus of observers proves what happened. Write down what each source says, when it said it, and which of the 7 matrix fields it addresses. Uncertainty that is dated and attributed is more useful than a confident sentence with no trail. Resolution mechanics for ordinary binary markets follow the same logic of reading the actual rules: a ruleset specifies the source, the deadline and edge cases, and the title alone is insufficient. Ordinary binary resolutions pay 1 to the winning side and 0 to the losing side, while a rare unknown or 50-50 resolution can pay 0.50 each; that is not a universal refund mechanism.

Worked decision: should this headline enter your evidence log as an event?

Suppose a report says a strike was launched, a second says munitions were intercepted over Iranian territory and a third quotes an official denying any impact. Run the matrix instead of averaging impressions.

The output of this decision is a status, not a trade. Either you hold a dated, attributed entry for a potentially qualifying executed impact, or you hold entries for an announced action, an intercepted attempt or a contested report. The rules determine which status matters for the contract; your log determines whether you can explain why.

Do not convert a historical contract snapshot into a live opportunity. The clause above was retrieved on 10 October 2026 and some dates in these examples are past; it documents how a ruleset treated 1 question. Current tradability, prices and outcomes are separate questions you would have to check against the live rules and order book. The same caution applies to scope: do not generalize that every geopolitical market uses the same threshold, source set or window. Verify the actual rules before treating any resolution procedure as a template.

Match a question to its guide

Match the question you want to examine to a guide in the table. Each row points to the guide that answers that kind of question.

If you are asking what a ruleset excludes, the ceasefire guide holds the direct exclusion vocabulary; the full breakdown of qualifying and non-qualifying actions belongs with the ceasefire contract family rather than here. Read the ceasefire guide for actual exclusions and clause language.

If you are tracking actors, offices, mandates and timelines, the politics guide covers how institutional roles shape what counts as an official act, execution, or third-party verification. Read the politics guide when the actor field, not the impact clause, is your open question.

If your question is what happens once reports conflict or a market closes, the resolution guide explains ordinary binary outcomes, edge cases and why a title is not enough. Read the resolution guide before you argue about what a final price meant.

If you want to log dated evidence, uncertainty and conflicting reports as an auditable practice, the journal guide walks through that habit. Read the journal guide to keep the evidence trail separate from the conclusion.

2 limits apply to everything above. First, the ceasefire clause is a source-specific snapshot: dates, contestants and contract clauses are tied to a document checked on a particular day and must not be universalized. Second, the qualitative matrix is an author-designed reading protocol, not a measured study, so it cannot tell you how often any error occurs. Where the price guide matters, remember that midpoint and last trade are display conventions, and executable quotes, depth and observation date are what actually constrain an order.