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-18
Ukraine–Russia Conflict and Operation Vivaldi Reporting
- stories
- 6
- events
- 5
- entities
- 44
- connections
- 6
Evidence so far on 2026-09-18 UTC · updated 2026-09-18 07:23 UTC · analysis as of 2026-09-18 03:28 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 2026-09-16, Andriy Biletskyi made a public statement about Operation Vivaldi, as described in “Ukrainian commander Biletskyi outlines strategic aim of Operation Vivaldi”; the coded Event gives him no specified target. On 2026-09-17, Ukrainian forces were coded as routing Russian forces in Donetsk, linked to the same Story. On that date, Russian Armed Forces were coded as destroying a Ukrainian UAV command post near Kharkiv in “Russian tank crews destroy Ukrainian UAV command post near Kharkiv.” Also on 2026-09-17, an Unidentified Armed Group was coded as conducting a drone attack that knocked out power in four Rostov-on-Don districts and as damaging a Russian military airfield, both linked to “Mass drone attack sparks major fire at military airfield in Rostov, Russia.” “Ukraine claims strikes destroy Russian An-12, two An-26 aircraft and helicopters” is a separate Story treated in the source connections as a same-incident/duplicate report of the Ukrainian strike and airfield damage; it attributes the strikes to Ukraine as a claim, but no corresponding coded Event or recorded Event participant is supplied for that Story.
Footnotes[10][2][7][9][3][6][8][1][5]Assessment
The retained situation establishes a shift in the selected dated material from Biletskyi’s political statement on 2026-09-16 to four coded material-conflict Events on 2026-09-17, including reciprocal Ukrainian and Russian Armed Forces action and two Russia-based drone Events attributed only to an Unidentified Armed Group. The Rostov Story has substantial article breadth and links to two coded Events, but the supplied Events do not identify Ukraine as the attacker; the same-incident aircraft-and-helicopter report remains an unlinked claim rather than an independently matched coded participation. The conflict Events report zero fatalities, while the absence of a specified target for Biletskyi’s statement and the lack of coded links for the reported Russian aircraft and helicopter strikes limit what can be established about operational responsibility or outcomes.
Footnotes[18][19][10][7][9][6][8][1][5][17]Explanation originally captured 2026-09-18 · Evidence through 2026-09-18 UTC · Source edition sed_16eea9a1ab0a2125756a72e5488989f5
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 6 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (1) and AIR/DRONE STRIKE (1).
- Prominent subjects
🇺🇦Ukraine and 🇷🇺Russia are prominent in the retained actor and relationship evidence.
- Entity coverage
44 canonical Entities are linked to this edition.
Metric coverage. 5 coded Events · 1 CAMEO+ · 4 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3
min 3max 3
Systemic importance0.2
min 0.2max 0.2
Propagation potential0.36
min 0.36max 0.36
Market sensitivity0.05
min 0.05max 0.05
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
5 coded events — 1 CAMEO+ (1 political) · 4 conflict
- Significance · 50.29min 0.23max 0.31
- Magnitude · 13min 3max 3
- Systemic · 10.2min 0.2max 0.2
- Propagation · 10.36min 0.36max 0.36
- Market · 10.05min 0.05max 0.05
- Goldstein · 5-7.8min -10max 0
- Fatalities · 40min 0max 0
- Confidence · 50.66min 0.35max 0.84
Quad class over those 5 events · Material Conflict 4 · Verbal Cooperation 1. The four CAMEO+ scores are over the 1 CAMEO+ events only; the 4 conflict events have no such column.
Magnitude
1 measured / 1 eligible · 0 missing · 4 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 1 of 5 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
1 measured / 1 eligible · 0 missing · 4 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 5 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
1 measured / 1 eligible · 0 missing · 4 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 5 events coded in the CAMEO+ family; the conflict family has no such column
Market
1 measured / 1 eligible · 0 missing · 4 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 5 events coded in the CAMEO+ family; the conflict family has no such column
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
4 measured / 4 eligible · 0 missing · 1 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 4 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-17analystlatest
Conflict Events and associated Stories
On 2026-09-17, the selected material includes four coded conflict Events and five reported Stories. The Stories include the Rostov drone-attack report, the Biletskyi Operation Vivaldi report, the Kharkiv report, the aircraft-and-helicopter claim, and the Bilyi Kolodiaz report. The four coded Events are linked to the Rostov, Biletskyi, and Kharkiv Stories; the aircraft-and-helicopter claim and the Bilyi Kolodiaz report have no linked coded Event in the supplied selection.
- 5+4
- Stories · vs day before
- 3+2
- Events · vs day before
- 100
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
09-1509-1609-17
Loading Situation timeline…
What kind of event · 5 coded types
over 5 coded events on this edition
- Conflict2
- ARMED CLASH1
- GOVERNMENT REGAINS TERRITORY1
- Conflict2
- AIR/DRONE STRIKE1
- SHELLING/ARTILLERY/MISSILE ATTACK1
- Political1
- 01 · Make Public Statement1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystUkraine–Russia material conflict
This thread joins the Donetsk battle, the Russian strike near Kharkiv, and the two Russia-based drone Events on 2026-09-17. It captures the directly coded armed actions rather than the separate unlinked claims about aircraft and helicopters.
- development
AnalystOperation Vivaldi public statement
This thread contains Andriy Biletskyi’s 2026-09-16 public statement and the 2026-09-17 Story that also links to the Donetsk battle Event.
- unresolved
AnalystReported Ukrainian strikes in Russia
This thread contains the Story claiming that Ukrainian strikes destroyed Russian aircraft and helicopters, but it has no linked coded Event; the Security Service of Ukraine is mention-only in that Story.
Key actors
Key Events
contextAnalystUkrainian forces rout Russian offensive in Donetsk region
On 2026-09-17, Ukrainian forces were coded as routing Russian forces in a Donetsk battle.
On 2026-09-17, Ukrainian forces were coded as routing Russian forces in a Donetsk battle.
Footnotes[7]
contextAnalystRussian tank crews destroy Ukrainian UAV command post near Kharkiv
On 2026-09-17, Russian Armed Forces were coded as destroying a Ukrainian UAV command post near Kharkiv.
On 2026-09-17, Russian Armed Forces were coded as destroying a Ukrainian UAV command post near Kharkiv.
Footnotes[9]contextAnalystconflict_96e242ec60a08d24
On 2026-09-17, an Unidentified Armed Group was coded as conducting a UAV attack that knocked out power in four Rostov-on-Don districts.
On 2026-09-17, an Unidentified Armed Group was coded as conducting a UAV attack that knocked out power in four Rostov-on-Don districts.
Footnotes[6]
contextAnalystDrone strike damages Russian military airfield
On 2026-09-17, an Unidentified Armed Group was coded as damaging a Russian military airfield; the target was bound to a Russian Armed Forces entity identifier, but the source actor remained unidentified.
On 2026-09-17, an Unidentified Armed Group was coded as damaging a Russian military airfield; the target was bound to a Russian Armed Forces entity identifier, but the source actor remained unidentified.
Footnotes[8]contextAnalystAndriy Biletskyi outlines Operation Vivaldi strategy
On 2026-09-16, Andriy Biletskyi was coded as making a public statement about Operation Vivaldi with no specified target.
On 2026-09-16, Andriy Biletskyi was coded as making a public statement about Operation Vivaldi with no specified target.
Footnotes[10]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Story reports the public statement by Andriy Biletskyi about Operation Vivaldi. · reporting linkAnalystUkrainian commander Biletskyi outlines strategic aim of Operation Vivaldi → Andriy Biletskyi outlines Operation Vivaldi strategy
The Story explicitly links to the coded political Event dated 2026-09-16.
The Story is linked to the coded Donetsk battle Event. · reporting linkAnalystUkrainian commander Biletskyi outlines strategic aim of Operation Vivaldi → Ukrainian forces rout Russian offensive in Donetsk region
The Story’s linked Event describes Ukrainian forces routing Russian forces in Donetsk on 2026-09-17.
The Story reports the Rostov-on-Don UAV attack Event. · reporting linkAnalystMass drone attack sparks major fire at military airfield in Rostov, Russia → conflict_96e242ec60a08d24
The Story is explicitly linked to the Event describing power loss in four Rostov-on-Don districts.
The Story reports the Russian military airfield damage Event. · reporting linkAnalystMass drone attack sparks major fire at military airfield in Rostov, Russia → Drone strike damages Russian military airfield
The Story is explicitly linked to the Event describing drone damage to a Russian military airfield.
The Story mentions Operation Vivaldi. · reporting linkAnalystUkrainian commander Biletskyi outlines strategic aim of Operation Vivaldi → Operation Vivaldi
The entity is linked to the Story as a mention-only subject; no Event participation is established for it.
How a Situation is put together6 Stories · 5 Events · 6 membership connections · 68 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 44 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.