Connected Situation / Through 2026-09-15

Russia–Ukraine Strikes and Polish Border-Security Measures

stories
21
events
12
entities
112
connections
21
Retained edition
Frozen through 2026-09-15 UTC · published 2026-09-16 00:33 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Checked against retained evidence
Situation at a glance

The retained Situation concerns reciprocal Russian and Ukrainian strikes, a reported Ukrainian territorial-recapture account in Donetsk, and Polish military and communications measures near the Ukraine frontier.

Footnotes[3][1][4][5][13][11][12][9]
Assessment

Structurally, the evidence connects battlefield activity with strikes on logistics, industrial and energy facilities, while separately recording Polish air, border and emergency-alert measures. The retained links describe some of these measures as responses, but same-day association alone does not establish causation.

Footnotes[19][18][17][20][21][15][16]

As-of explanation captured 2026-09-16 · Evidence through 2026-09-15 UTC

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

This retained edition
  • Scope

    A 2-day Situation represented by 12 coded Events carried across 21 member Stories.

  • Coded activity

    The coded activity is led by AIR/DRONE STRIKE (5) and SHELLING/ARTILLERY/MISSILE ATTACK (2).

  • Prominent subjects

    🇺🇦Ukraine, 🇷🇺Russia, and 🇵🇱Poland are prominent in the retained actor and relationship evidence.

  • Entity coverage

    112 canonical Entities are linked to this edition.

Metric coverage. 12 coded Events · 4 CAMEO+ · 8 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3.8
min 2max 8
4 measured
Systemic importance0.27
min 0.07max 0.43
4 measured
Propagation potential0.43
min 0.24max 0.64
4 measured
Market sensitivity0.06
min 0.05max 0.1
4 measured

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

12 coded events — 4 CAMEO+ (3 political) · 8 conflict

  • Significance · 120.35
    min 0.2max 0.61
  • Magnitude · 43.8
    min 2max 8
  • Systemic · 40.27
    min 0.07max 0.43
  • Propagation · 40.43
    min 0.24max 0.64
  • Market · 40.06
    min 0.05max 0.1
  • Goldstein · 11-7.4
    min -10max 3
  • Fatalities · 80
    min 0max 0
  • Confidence · 120.73
    min 0.35max 0.9

Quad class over those 11 events · Material Conflict 9 · Verbal Cooperation 2. 1 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 4 CAMEO+ events only; the 8 conflict events have no such column.

Significance

12 measured / 12 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 12 events

Magnitude

4 measured / 4 eligible · 0 missing · 8 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across the 4 of 12 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

4 measured / 4 eligible · 0 missing · 8 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 4 of 12 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

4 measured / 4 eligible · 0 missing · 8 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 4 of 12 events coded in the CAMEO+ family; the conflict family has no such column

Market

4 measured / 4 eligible · 0 missing · 8 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 4 of 12 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

11 measured / 11 eligible · 0 missing · 1 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 11 of 12 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics

Fatalities

8 measured / 8 eligible · 0 missing · 4 not applicable

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 8 of 12 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

Confidence

12 measured / 12 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 12 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

The lay of the land

Situation timeline

Threads
All 2 daysarticlesstoriesevents
09-1409-15
Loading Situation timeline…

What kind of event · 7 coded types

over 12 coded events on this edition

  • Conflict7
    • AIR/DRONE STRIKE5
    • SHELLING/ARTILLERY/MISSILE ATTACK2
  • Political3
    • 014 · Consider Policy Option1
    • 022 · Appeal for Diplomatic Cooperation1
    • 154 · Mobilize/increase Armed Forces1
  • Conflict1
    • GOVERNMENT REGAINS TERRITORY1
  • Infrastructure1
    • IN04 · Communications Infrastructure1
Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystRussian and Ukrainian strikes

    The retained evidence records Russian strikes on Ukrainian logistics and facilities and Ukrainian strikes on Russian industrial and oil facilities.

    The retained evidence records Russian strikes on Ukrainian logistics and facilities and Ukrainian strikes on Russian industrial and oil facilities.

    Footnotes[3][1][12][11][10]
  2. development
    AnalystDonetsk territorial-recapture account

    The retained evidence reports a Ukrainian offensive in Donetsk and codes Ukrainian forces as recapturing territory from Russian forces.

    The retained evidence reports a Ukrainian offensive in Donetsk and codes Ukrainian forces as recapturing territory from Russian forces.

    Footnotes[4][13]
  3. development
    AnalystPolish military and emergency-alert measures

    The retained evidence records Polish fighter deployment near the Ukrainian border and incomplete emergency-alert delivery to residents of Lubelskie and Podkarpackie.

    The retained evidence records Polish fighter deployment near the Ukrainian border and incomplete emergency-alert delivery to residents of Lubelskie and Podkarpackie.

    Footnotes[5][7][9]

Key actors

    Key Events

    1. contextAnalystUkrainian forces recapture territory from Russian forces in Donetsk

      The coded Event records Ukrainian forces recapturing territory from Russian forces in Donetsk.

      The coded Event records Ukrainian forces recapturing territory from Russian forces in Donetsk.

      Footnotes[13][4]
    2. contextAnalystRussian missile strike destroys EVA sorting center in Odesa

      The coded Event records a Russian missile strike destroying an EVA sorting center in Odesa.

      The coded Event records a Russian missile strike destroying an EVA sorting center in Odesa.

      Footnotes[12][3]
    3. contextAnalystUkrainian drones ignite fire at Syzran oil refinery

      The coded Event records Ukrainian drones igniting a fire at the Syzran oil refinery.

      The coded Event records Ukrainian drones igniting a fire at the Syzran oil refinery.

      Footnotes[11][1]
    4. contextAnalystPoland deploys fighter jets near Ukrainian border

      The retained connection describes Poland’s aircraft activity as a military response to Russian attacks on Ukraine.

      The retained connection describes Poland’s aircraft activity as a military response to Russian attacks on Ukraine.

      Footnotes[7][5][18]
    5. contextAnalystPoland's security centre reports incomplete emergency alert delivery

      The coded Event records incomplete emergency-alert delivery to residents of Lubelskie and Podkarpackie.

      The coded Event records incomplete emergency-alert delivery to residents of Lubelskie and Podkarpackie.

      Footnotes[9][5]

    Notable connections

    Evidenced relationships involving significant participants beyond the central cast.

    1. the retained connection describes Russian mass strikes as a response to the Ukrainian offensive · reporting linkAnalystUkrainian forces launch large-scale offensive in Donetsk region → Russia launches mass strikes on Ukrainian logistics hubs and ports

      The supplied connection explicitly characterizes the Russian strikes as a response to the Ukrainian offensive.

      The supplied connection explicitly characterizes the Russian strikes as a response to the Ukrainian offensive.

      Footnotes[19][4][3]
    2. the retained connection describes Polish aircraft activity as a response to Russian attacks on Ukraine · reporting linkAnalystRussia launches mass strikes on Ukrainian logistics hubs and ports → Poland Scrambles Military Aircraft Amid Russian Attacks on Ukraine

      The supplied connection explicitly identifies the Polish aircraft activity as a response to Russian attacks.

      The supplied connection explicitly identifies the Polish aircraft activity as a response to Russian attacks.

      Footnotes[18][3][5]
    3. supports the coded Ukrainian strike on the Syzran oil refinery · reporting linkAnalystUkraine strikes Russian industrial and oil facilities in Samara region → Ukrainian drones ignite fire at Syzran oil refinery

      The Event record links the Syzran refinery strike to the Story about Ukrainian strikes on Russian industrial and oil facilities.

      The Event record links the Syzran refinery strike to the Story about Ukrainian strikes on Russian industrial and oil facilities.

      Footnotes[1][11]
    4. supports the coded Ukrainian missile attack on Taganrog · reporting linkAnalystUkraine strikes Russian industrial and oil facilities in Samara region → Ukrainian forces launch missile attack on Taganrog

      The Event record links the Taganrog attack to the Story about Ukrainian strikes on Russian industrial and oil facilities.

      The Event record links the Taganrog attack to the Story about Ukrainian strikes on Russian industrial and oil facilities.

      Footnotes[1][10]
    5. the same-day records concern the passenger-train strike and Polish military activity near the Ukraine frontier · analytical connectionAnalystRussian drone strikes passenger train near Ukraine-Poland border → Poland Scrambles Military Aircraft Amid Russian Attacks on Ukraine

      The supplied same-day edge establishes adjacency between the two reports, not a common recorded actor or causation.

      The supplied same-day edge establishes adjacency between the two reports, not a common recorded actor or causation.

      Footnotes[20][2][5]
    How a Situation is put together21 Stories · 12 Events · 21 membership connections · 261 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 112 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.