Significance
18 measured / 18 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 18 events
Connected Situation / Through 2026-10-03
Russian-Ukrainian Strikes and Kyiv Claims
- stories
- 32
- events
- 18
- entities
- 120
- connections
- 32
Evidence so far on 2026-10-03 UTC · updated 2026-10-03 17:24 UTC · analysis as of 2026-10-03 00:29 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On October 1, Russian Armed Forces drones struck 11 locations in Ukraine, an Event linked to “Explosions heard in Kyiv overnight into September 2.” A separate October 1 Event describes a Russian drone attack near Ukraine’s Romanian border. The report “Possible drone crashes near Plauru, Romania, sparking fire by Ukrainian border” is also linked to an October 2 Event coding a Russian drone crash near Plauru, Romania. [event/story refs] On October 2, Russian forces struck the Kyivska substation in Kyiv Oblast, while “Russian strikes hit Kyiv high-rise, setting it ablaze and closing city bridges” describes damage and disruption in Kyiv. [event/story refs] Ukraine’s Special Operations Forces struck the Samara oil dispatch station on October 2, as reported in “Russia strikes Kyiv power grid as Ukraine hits Russian oil infrastructure.” [event/story refs] Volodymyr Zelensky said Russia aimed to drive residents from Kyiv; the Event captures his statement, and “Zelensky says Putin is trying to drive Ukrainians out of Kyiv” reports the allegation. [event/story/entity refs] Other October 2 accounts describe a Russian night attack damaging an enterprise in Rivne Oblast and evacuations, and a drone attack setting a Volgograd residential building ablaze and injuring one person. [story refs]
Footnotes[14][1][16][6][15][2][13][5][17][8][18][10]Assessment
The dated Events and linked Stories establish reported Russian attacks in Ukraine and Ukrainian strikes on Russian infrastructure, but do not establish that either caused the other. Zelensky’s account of Russia’s aims is an attributed allegation, not independent proof of intent. The Kyiv overnight coverage includes a report of one death and two injuries, while the linked Events report zero fatalities for the 11-location strike and the Kyivska substation strike; these differently scoped accounts do not provide a reconciled toll. The headline “Explosions heard in Kyiv overnight into September 2” conflicts with its October 2 Story date and its linked October 1 and October 2 Event dates.
Footnotes[14][15][1][17][8]Explanation originally captured 2026-10-03 · Evidence through 2026-10-03 UTC · Source edition sed_abe3cefdacc215ea1bd5b09e0eb45ba6
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 4-day Situation represented by 18 coded Events carried across 32 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (10) and IN02 · Transport Disruption (2).
- Prominent subjects
Volodymyr Zelenskyy is prominent in the retained actor and relationship evidence.
- Entity coverage
120 canonical Entities are linked to this edition.
Metric coverage. 18 coded Events · 7 CAMEO+ · 11 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3
min 2max 4
Systemic importance0.22
min 0.1max 0.52
Propagation potential0.34
min 0.24max 0.48
Market sensitivity0.06
min 0.05max 0.1
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 8 scores, distributions & definitions
How the coder scored the full retained Event set
18 coded events — 7 CAMEO+ (3 political) · 11 conflict
- Significance · 180.31min 0.2max 0.43
- Magnitude · 73min 2max 4
- Systemic · 70.22min 0.1max 0.52
- Propagation · 70.34min 0.24max 0.48
- Market · 70.06min 0.05max 0.1
- Goldstein · 14-7.4min -10max 3
- Fatalities · 110min 0max 0
- Confidence · 180.73min 0.27max 0.91
Quad class over those 14 events · Material Conflict 11 · Verbal Cooperation 2 · Verbal Conflict 1. 4 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 7 CAMEO+ events only; the 11 conflict events have no such column.
Magnitude
7 measured / 7 eligible · 0 missing · 11 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
7 measured / 7 eligible · 0 missing · 11 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
7 measured / 7 eligible · 0 missing · 11 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column
Market
7 measured / 7 eligible · 0 missing · 11 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
14 measured / 14 eligible · 0 missing · 4 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 14 of 18 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
11 measured / 11 eligible · 0 missing · 7 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 11 of 18 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
18 measured / 18 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 18 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day4 reporting days · click a day to open or close it
2026-10-03from the recordslatest
Russian forces target Kyiv’s North Bridge in air attack
11 Stories and 3 coded Events (-7 / -5 against the day before). Widest coverage: Russian strikes hit Kyiv bridge for second day amid infrastructure campaign (114 articles).
- 11-7
- Stories · vs day before
- 3-5
- Events · vs day before
- 290
- articles
The lay of the land
Situation timeline
Threads
All 4 daysarticlesstoriesevents
09-3010-0110-0210-03
Loading Situation timeline…
What kind of event · 8 coded types
over 18 coded events on this edition
- Conflict11
- AIR/DRONE STRIKE10
- SHELLING/ARTILLERY/MISSILE ATTACK1
- Infrastructure3
- IN02 · Transport Disruption2
- IN05 · Deliberate Infrastructure Sabotage1
- Political3
- 016 · Deny Responsibility1
- 02 · Appeal1
- 111 · Criticize or Denounce1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystRussian attacks in Ukraine
This thread brings together the 11-location drone strike, the Kyivska substation strike, reports of Kyiv damage and bridge closures, and accounts of attacks in Rivne Oblast and on a school in Kyiv.
- core
AnalystUkrainian strikes and reported effects beyond Ukraine
The linked Samara Event identifies a strike by Ukraine’s Special Operations Forces; separate Stories report a Volgograd residential fire and power outages across Crimea. The ammunition-depot and additional Russian-facility claims remain attributed to Stories rather than established by an Event included here.
The linked Samara Event identifies a strike by Ukraine’s Special Operations Forces; separate Stories report a Volgograd residential fire and power outages across Crimea. The ammunition-depot and additional Russian-facility claims remain attributed to Stories rather than established by an Event included here.
Footnotes[13][5][4][9][12][11] - development
AnalystZelensky’s statements about Russia’s aims
Zelensky’s statement that Russia aims to drive residents from Kyiv is represented by an Event; his separate allegation that Putin ordered disregard for the rules of war appears in a Story without a linked Event.
Key actors
- VZ
Key Events
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
reports the Kyivska substation strike · reporting linkAnalystRussian strikes hit Kyiv high-rise, setting it ablaze and closing city bridges → Russian forces strike Kyivska substation in Kyiv Oblast
The Story is linked to the Event describing the substation strike.
reports the Samara oil dispatch station strike · reporting linkAnalystRussia strikes Kyiv power grid as Ukraine hits Russian oil infrastructure → Ukraine’s Special Operations Forces strike Samara oil dispatch station
The Story is linked to the Event describing the strike on the Samara station.
Transneft is mentioned in the Samara and Kyiv power-grid Story · reporting linkAnalystTransneft → Russia strikes Kyiv power grid as Ukraine hits Russian oil infrastructure
Transneft is a mention in this Story, with no supporting Event participation shown.
How a Situation is put together32 Stories · 18 Events · 32 membership connections · 410 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 120 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.