Significance
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events
Connected Situation / Through 2026-11-02
Moscow Threat Warning and Reported Detention
- stories
- 3
- events
- 1
- entities
- 15
- connections
- 3
Evidence so far on 2026-11-02 UTC · updated 2026-11-02 09:36 UTC · analysis as of 2026-11-02 09:22 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
The United States and Canada warned of a possible mass-casualty threat at Moscow venues, as reported under “US and Canada warn of mass-casualty threat at Moscow venues” on November 1. On that date, the German Federal Foreign Office made a public statement warning German citizens in Russia of a terror threat in Moscow; the coded event places the statement at Tsaritsyno. On November 2, “Russia detains teenager after US warning of possible terrorist attack” reported a detention, while “Russian security services arrest planner of attack in Moscow” described an arrest connected to the same reported incident. The Federal Security Service and the Embassy of the United States in Moscow are mentioned in both the warning and detention coverage, but the entity records do not show them as participants in the coded event.
Footnotes[3][4][1][2][9][5][6]Assessment
The November 2 headlines describe one reported arrest, not separate arrests, while differing over whether the suspect was a teenager or an attack planner. The November 1 coded event is specifically the German Federal Foreign Office’s public statement to German citizens in Russia; it is not the US and Canadian warning described in the headline of the linked Story. These facts establish warnings and a reported detention, but do not establish that an attack occurred or that the differing descriptions of the suspect are resolved.
Footnotes[9][1][2][4][3]As-of explanation captured 2026-11-02 · Evidence through 2026-11-02 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
- Scope
A 2-day Situation represented by 1 coded Event carried across 3 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (1).
- Prominent subjects
🇷🇺Russia is prominent in the retained actor and relationship evidence.
- Entity coverage
15 canonical Entities are linked to this edition.
Metric coverage. 1 coded Events · 1 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3
min 3max 3
Systemic importance0.06
min 0.06max 0.06
Propagation potential0.25
min 0.25max 0.25
Market sensitivity0.05
min 0.05max 0.05
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 7 scores, distributions & definitions
How the coder scored the full retained Event set
1 coded event — 1 CAMEO+ (1 political)
- Significance · 10.21min 0.21max 0.21
- Magnitude · 13min 3max 3
- Systemic · 10.06min 0.06max 0.06
- Propagation · 10.25min 0.25max 0.25
- Market · 10.05min 0.05max 0.05
- Goldstein · 10min 0max 0
- Confidence · 10.72min 0.72max 0.72
Quad class over that 1 event · Verbal Cooperation 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero.
Magnitude
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Systemic
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Propagation
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Market
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events — every one of them CAMEO+
Goldstein
1 measured / 1 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 1 of 1 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Confidence
1 measured / 1 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 1 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day2 reporting days · click a day to open or close it
2026-11-02analystlatest
Detention reports
The two Stories report a detention tied to the possible Moscow attack and are connected as accounts of the same reported arrest, though they describe the suspect’s role differently.
- 2+1
- Stories · vs day before
- 0-1
- Events · vs day before
- 8
- articles
The lay of the land
Situation timeline
Threads
All 2 daysarticlesstoriesevents
11-0111-02
Loading Situation timeline…
What kind of event · 1 coded type
over 1 coded event on this edition
- 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
AnalystMoscow threat warning and reported detention
The thread links the November 1 warning at Moscow venues with November 2 reporting of a detention tied to the possible attack; the two detention headlines are connected as descriptions of the same reported arrest.
Key actors
Key Events
contextAnalystGerman Federal Foreign Office warns citizens of terror threat in Moscow
On November 1, the German Federal Foreign Office made a public statement warning German citizens in Russia of a terror threat in Moscow; the event is located at Tsaritsyno and is linked to the US and Canada warning Story.
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The November 2 detention is described as a follow-up to the warning about a possible attack. · analytical connectionAnalystUS and Canada warn of mass-casualty threat at Moscow venues → Russia detains teenager after US warning of possible terrorist attack
The connection identifies the reported detention as a follow-up to the US warning.
Both Stories describe the same reported arrest, with different descriptions of the suspect’s role. · analytical connectionAnalystRussia detains teenager after US warning of possible terrorist attack → Russian security services arrest planner of attack in Moscow
The connection identifies the reports as the same incident and notes the difference between the teenager and planner descriptions.
The event is linked to the US and Canada warning Story, while its coded source actor is the German Federal ForeignOffice · reporting linkAnalystGerman Federal Foreign Office warns citizens of terror threat in Moscow → US and Canada warn of mass-casualty threat at Moscow venues
The event names the German Federal Foreign Office as its source actor and lists this Story as linked; the Story headline describes a US and Canadian warning.
How a Situation is put together3 Stories · 1 Events · 3 membership connections · 25 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 15 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.