In a single 15-minute window our event-monitoring layer flags 87 material-conflict events across 39 places on Earth. One sits on Iran's southeastern coast in Sistan va Baluchestan — the same maritime theatre as the Strait of Hormuz. We take that flashpoint and cross it with our orbital-observation model — how many eyes can already see it, and how often — then with our own flight-integrity feed. Three independent layers, read together, become a situation brief.
Material-conflict events, one 15-minute window
severe (Goldstein ≤ -8)elevated
EACH DOT = A PLACE WITH A MATERIAL-CONFLICT EVENT IN THE LATEST MONITORING WINDOW · SIZE = SEVERITY · ORBISPECT EVENT LAYER.
The flashpoint: Iran's southeastern coast
The open event feed places a severe event (Goldstein −10 — the Goldstein scale ranks conflict-cooperation event types from roughly −10 for the most violent to +10 for the most cooperative) on Iran's southeastern coast in Sistan va Baluchestan — the same maritime theatre as the Strait of Hormuz, the gate a fifth of the world's seaborne oil passes through. That is the "when and where". The next three rows are the "who and how exposed", each from a separate open signal:
No single feed says "crisis at Hormuz". The event feed says where the news is hot; the orbital catalogue says it is under near-continuous observation; our own flight-integrity layer says navigation is already being degraded there. The read lives in the overlap.
The orbital picture overhead
EARTH-OBSERVATION SATELLITES WHOSE ORBIT REACHES THE FLASHPOINT LATITUDE · ORBISPECT ORBITAL-OBSERVATION MODEL.
Why this is a method, not a scoop
The power here is not any single layer — it is the read: aligning an event spike with the orbital-observation picture and our own measured signals, on the same map, at the same minute. Each layer alone is ambiguous; together they resolve into a situation.
Two things turn this into a product. First, fusion — the incumbents are siloed; few, if any, routinely overlay event intensity, the orbital-observation picture, live flight tracks and maritime traffic in one frame. Second, the archive: the record of what every layer said in this exact 15-minute window is kept nowhere by default. We keep it — so tomorrow this snapshot is a baseline, and the change is the signal.
Stated plainly: the figures above are a single live snapshot for illustration, not a forecast. Geocoding is noisy and event counts are not casualties. The value is the repeatable method and the growing archive behind it, not any one dot on the map.