Significance
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events
Connected Situation / Through 2026-09-20
Reported strikes and military-air activity
- stories
- 8
- events
- 5
- entities
- 40
- connections
- 8
Evidence so far on 2026-09-20 UTC · updated 2026-09-20 03:25 UTC · analysis as of 2026-09-20 00:29 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 2026-09-18, a coded Event records Russian Armed Forces strikes in Ukraine with one reported fatality, an unidentified drone operator hitting a Russian nuclear plant with zero reported fatalities, and Czech Gripen jets deploying to Poland. On 2026-09-19, a coded Event names Ukraine as the source actor and Russia as the target actor in a launcher strike. Stories dated 2026-09-19 report alleged Ukrainian strikes on nuclear sites, Ukrainian strikes on targets deep inside Russia and other Russian targets, and Polish military-air activity. Volodymyr Zelenskyy and the Ministry of Defense of Ukraine are mentioned in two of the Ukrainian-strike Stories.
Footnotes[7][8][10][9][3][2][5][1][12][13]Assessment
The 2026-09-19 coded launcher Event names Ukraine as the source actor and Russia as the target actor. The nuclear-plant Event names an unidentified drone operator, has no specified target actor, reports zero fatalities and has confidence of 0.42; the associated Story reports allegations of Ukrainian involvement, so Ukrainian responsibility for that Event is not established. The Czech deployment and Polish fighter-scramble Events establish military-air activity in Poland, but do not establish why either occurred. The timeline shows three coded Events and no Stories on 2026-09-18, compared with two coded Events and seven Stories on 2026-09-19; this describes a change in retained evidence composition, not a measured change in real-world intensity.
Footnotes[9][8][3][10][11][18][19]Explanation originally captured 2026-09-20 · Evidence through 2026-09-20 UTC · Source edition sed_ddd4f9a11bb66569f766a3e5798cdffe
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 3-day Situation represented by 5 coded Events carried across 8 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (3) and OTHER (2).
- Prominent subjects
🇵🇱Poland, 🇷🇺Russia, and 🇺🇦Ukraine are prominent in the retained actor and relationship evidence.
- Entity coverage
40 canonical Entities are linked to this edition.
Metric coverage. 5 coded Events · 0 CAMEO+ · 5 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude—
Systemic importance—
Propagation potential—
Market sensitivity—
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 4 scores, distributions & definitions
How the coder scored the full retained Event set
5 coded events — 5 conflict
- Significance · 50.24min 0.11max 0.39
- Goldstein · 5-6.5min -9.5max -2
- Fatalities · 50min 0max 1
- Confidence · 50.53min 0.35max 0.62
Quad class over those 5 events · Material Conflict 3 · Verbal Conflict 2.
Goldstein
5 measured / 5 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 5 of 5 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
5 measured / 5 eligible · 0 missing · 0 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 5 of 5 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
5 measured / 5 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 5 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day3 reporting days · click a day to open or close it
2026-09-20from the recordslatest
Polish PM warns Russia plans drone strikes on Ukraine supporters
1 Story and 0 coded Events (-6 / -2 against the day before). Widest coverage: Polish PM warns Russia plans drone strikes on Ukraine supporters (1 articles).
- 1-6
- Stories · vs day before
- 0-2
- Events · vs day before
- 1
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
09-1809-1909-20
Loading Situation timeline…
What kind of event · 2 coded types
over 5 coded events on this edition
- Conflict3
- AIR/DRONE STRIKE3
- Conflict2
- OTHER2
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystAlleged strike on a Russian nuclear site and disputed attribution
The nuclear-site thread joins the 2026-09-18 event naming an unidentified drone operator with the 2026-09-19 Story “Russia accuses EU of ignoring alleged Ukrainian strikes on nuclear sites.” The event does not identify Ukraine as the source actor, while the Story describes the attribution as an allegation.
The nuclear-site thread joins the 2026-09-18 event naming an unidentified drone operator with the 2026-09-19 Story “Russia accuses EU of ignoring alleged Ukrainian strikes on nuclear sites.” The event does not identify Ukraine as the source actor, while the Story describes the attribution as an allegation.
Footnotes[8][3] - development
AnalystUkrainian claims about strikes deep inside Russia
The Story “Ukraine strikes targets deep inside Russia to erode its war machine” reports Ukrainian strikes deep inside Russia. A separate 2026-09-19 coded Event names Ukraine as the source actor and Russia as the target actor in a launcher strike.
- development
AnalystCzech deployment and Polish fighter scramble
The Story “Poland deploys military aircraft as Russian strikes hit Ukraine” is attached to Events for a Czech Gripen deployment to Poland and a Polish fighter scramble. These Events record military-air activity in Poland; they do not establish a causal explanation.
- development
AnalystClaims about Ukrainian attacks on Russian military and industrial targets
The Stories “Ukraine strikes Russian drone command posts, training ground and warehouses,” “Ukraine strikes and destroys Russian missile launcher,” and “Fire Point claims Ukrainian strikes hit 10% of Russia’s oil refineries” report Ukrainian strike claims. The launcher Event is the one that names Ukraine as the source actor and Russia as the target actor.
The Stories “Ukraine strikes Russian drone command posts, training ground and warehouses,” “Ukraine strikes and destroys Russian missile launcher,” and “Fire Point claims Ukrainian strikes hit 10% of Russia’s oil refineries” report Ukrainian strike claims. The launcher Event is the one that names Ukraine as the source actor and Russia as the target actor.
Footnotes[2][6][4][9]
Key actors
Key Events
contextAnalystRussian strikes kill teenager and injure people in Ukraine
On 2026-09-18, the Russian Armed Forces were coded as striking Ukraine; the Event reports one fatality, identified as a teenager in its title.
contextAnalystUnidentified drone operator hits Russian nuclear plant
On 2026-09-18, an unidentified drone operator was coded as hitting a Russian nuclear plant. The Event reports zero fatalities and confidence of 0.42, and does not name a target or Ukrainian source actor.
contextAnalystUkraine destroys Russian launcher in strike
On 2026-09-19, Ukraine was coded as destroying a Russian launcher in a strike. Russia is named as the target actor, with confidence of 0.62 and no reported fatalities.
contextAnalystCzech Gripen jets deploy to Poland amid Ukrainian drone activity
On 2026-09-18, the Czech Air Force was coded as deploying Gripen jets to Poland amid Ukrainian drone activity.
contextAnalystPoland scrambles fighter jets
On 2026-09-19, the Polish Armed Forces were coded as scrambling fighter jets. The Event reports no fatalities and has confidence of 0.35.
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
supports the coded report of an unidentified drone strike on a Russian nuclear plant · reporting linkAnalystRussia accuses EU of ignoring alleged Ukrainian strikes on nuclear sites → Unidentified drone operator hits Russian nuclear plant
The nuclear-site Story is the supporting Story attached to the nuclear-plant Event, but its headline describes alleged Ukrainian strikes rather than an established attribution.
supports the coded report that Ukraine destroyed a Russian launcher · reporting linkAnalystUkraine strikes and destroys Russian missile launcher → Ukraine destroys Russian launcher in strike
The launcher Story is attached to the Event titled “Ukraine destroys Russian launcher in strike.”
covers the Czech Gripen deployment to Poland · reporting linkAnalystPoland deploys military aircraft as Russian strikes hit Ukraine → Czech Gripen jets deploy to Poland amid Ukrainian drone activity
The Story “Poland deploys military aircraft as Russian strikes hit Ukraine” is attached to the Czech deployment Event.
covers the Polish fighter scramble · reporting linkAnalystPoland deploys military aircraft as Russian strikes hit Ukraine → Poland scrambles fighter jets
The same Story is attached to the Event titled “Poland scrambles fighter jets.”
mentions Volodymyr Zelenskyy in coverage of Ukrainian strikes · reporting linkAnalystUkraine strikes Russian drone command posts, training ground and warehouses → Volodymyr Zelenskyy
Volodymyr Zelenskyy is listed as a mention in “Ukraine strikes Russian drone command posts, training ground and warehouses”; he has no supporting Event here.
How a Situation is put together8 Stories · 5 Events · 8 membership connections · 56 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 40 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.