Significance
301 measured / 301 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 301 events
Connected Situation / Through 2026-10-25
India’s Election Commission Dispute and Protest Restrictions
- stories
- 323
- events
- 301
- entities
- 773
- connections
- 323
Evidence so far on 2026-10-25 UTC · updated 2026-10-25 10:25 UTC · analysis as of 2026-10-24 19:29 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 28 September, the Indian National Congress sought the Chief Election Commissioner’s removal and cancellation of the Varanasi result, as “Congress seeks CEC's removal and cancellation of Varanasi election result” reported. On 29 September, Mallikarjun Kharge demanded Gyanesh Kumar’s immediate removal; “TVK stays cautious as allies seek India's chief election commissioner's ouster” described differing positions among allies. On 2 October, Delhi Police imposed assembly restrictions across New Delhi district, while “Delhi closes 11 metro stations ahead of planned Jantar Mantar protest” reported metro closures ahead of a planned demonstration; Mamata Banerjee separately demanded Kumar’s removal at an INDIA bloc meeting. On 6 October, “India's PIB rejects claim ECI removed Form 6 press release after Supreme Court remark” reported the PIB’s response to a claim about the press release. On 9 October, the Supreme Court rejected a plea for unrestricted police action against protesters, while “India bloc MPs weigh fresh protest over alleged election vote theft” described protest deliberations. On 13 October, the Aam Aadmi Party called for Kumar’s resignation and announced a Delhi march, while “Delhi Police detain CJP leaders again during SIR protests at Jantar Mantar” reported Cockroach Janta Party detentions. On 15 October, the Delhi High Court declined to block a CJP protest, and the Supreme Court sought a response in a separate Jantar Mantar challenge.
Footnotes[16][15][18][17][14][21][13][12][23][20][9][23]Assessment
The named actions establish a sustained political dispute over voter-roll revision, allegations of electoral misconduct, demands concerning Gyanesh Kumar, protest activity and restrictions on protest access. They do not establish that voter-roll manipulation occurred: claims about Form 6 and the PIB’s response to a press-release claim are distinct, and the PIB response is not a judicial finding on the alleged changes. The Delhi High Court’s decision about a CJP protest and the Supreme Court’s response request in a separate Jantar Mantar challenge do not resolve protest access in one direction. Opposition initiatives, CJP actions and the separate cases concerning CJP leaders are related by subject and setting, but these reports do not establish a single coordinated campaign or one continuous legal case.
Footnotes[13][8][23][6][7][9][2][3]Explanation originally captured 2026-10-24 · Evidence through 2026-10-25 UTC · Source edition sed_5413403b43e247ae54acdf673d46b2e6
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 29-day Situation represented by 301 coded Events carried across 323 member Stories.
- Coded activity
The coded activity is led by PEACEFUL PROTEST (38) and PROTEST WITH INTERVENTION (32).
- Prominent subjects
Indian National Congress, Delhi Police, and Bharatiya Janata Party are prominent in the retained actor and relationship evidence.
- Entity coverage
773 canonical Entities are linked to this edition.
Metric coverage. 301 coded Events · 209 CAMEO+ · 92 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3.8
min 1max 7
Systemic importance0.12
min 0.03max 0.37
Propagation potential0.27
min 0max 0.44
Market sensitivity0.06
min 0.05max 0.38
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
301 coded events — 209 CAMEO+ (189 political) · 92 conflict
- Significance · 3010.28min 0.12max 0.54
- Magnitude · 2093.8min 1max 7
- Systemic · 2090.12min 0.03max 0.37
- Propagation · 2090.27min 0max 0.44
- Market · 2090.06min 0.05max 0.38
- Goldstein · 281-3.3min -9max 7
- Fatalities · 920min 0max 0
- Confidence · 3010.78min 0.25max 0.98
Quad class over those 281 events · Verbal Conflict 152 · Material Conflict 69 · Verbal Cooperation 56 · Material Cooperation 4. 20 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 209 CAMEO+ events only; the 92 conflict events have no such column.
Magnitude
209 measured / 209 eligible · 0 missing · 92 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 209 of 301 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
209 measured / 209 eligible · 0 missing · 92 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 209 of 301 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
209 measured / 209 eligible · 0 missing · 92 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 209 of 301 events coded in the CAMEO+ family; the conflict family has no such column
Market
209 measured / 209 eligible · 0 missing · 92 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 209 of 301 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
281 measured / 281 eligible · 0 missing · 20 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 281 of 301 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
92 measured / 92 eligible · 0 missing · 209 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 92 of 301 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
301 measured / 301 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 301 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day29 reporting days · click a day to open or close it
2026-10-25from the recordslatest
INDIA bloc to hold public impeachment of Chief Election Commissioner Gyanesh Kumar
3 Stories and 0 coded Events (-7 / -6 against the day before). Widest coverage: INDIA bloc to hold public impeachment of Chief Election Commissioner Gyanesh Kumar (7 articles).
- 3-7
- Stories · vs day before
- 0-6
- Events · vs day before
- 14
- articles
The lay of the land
Situation timeline
Threads
All 29 daysarticlesstoriesevents
09-2710-0310-0810-1410-1910-25
Loading Situation timeline…
What kind of event · 56 coded types
over 301 coded events on this edition
- Political189
- 111 · Criticize or Denounce28
- 01 · Make Public Statement20
- 1041 · Change Leadership20
- 112 · Accuse14
- 02 · Appeal12
- 115 · Bring Lawsuit Against10
- 17 · Coerce7
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystVoter-roll allegations and Form 6 scrutiny
Congress challenged the Varanasi result, while later coverage addressed the Form 6 dispute and the PIB’s response to a press-release claim.
- core
AnalystProtests and demands concerning the election chief
Political figures and parties demanded Kumar’s removal or resignation; separate coverage reported CJP detentions and protests by Cockroach Party protesters over voter-roll removals.
- development
AnalystPolice restrictions, protest access and legal proceedings
Delhi Police assembly restrictions and metro station closures sit alongside the Supreme Court’s separate consideration of the Jantar Mantar protest-ban challenge.
Key actors
- IN
RuleIndian National Congress
Recorded as actor and target in 17 coded Events, including Indian National Congress demands disclosure of electoral-roll changes.
Recorded as actor and target in 17 coded Events, including Indian National Congress demands disclosure of electoral-roll changes.
Footnotes[?][?][?][?][?] - DP
RuleDelhi Police
Recorded as target and actor in 67 coded Events, including Delhi Police imposes assembly restrictions across New Delhi district.
Recorded as target and actor in 67 coded Events, including Delhi Police imposes assembly restrictions across New Delhi district.
Footnotes[?][17][?][?][?] - BJ
RuleBharatiya Janata Party
Recorded as actor and target in 6 coded Events, including BJP spokesperson Gaurav Bhatia criticizes Rahul Gandhi over CJI request.
Recorded as actor and target in 6 coded Events, including BJP spokesperson Gaurav Bhatia criticizes Rahul Gandhi over CJI request.
Footnotes[?][?][?][?][?] - CJ
RuleCockroach Janta Party
Recorded as actor and target in 9 coded Events, including Union home ministry approves major CAPF deployment in Delhi.
Recorded as actor and target in 9 coded Events, including Union home ministry approves major CAPF deployment in Delhi.
Footnotes[?][?][?][?][?] - GK
Key Events
contextAnalystMallikarjun Kharge demands Gyanesh Kumar’s immediate removal
On 29 September, Mallikarjun Kharge demanded Gyanesh Kumar’s immediate removal.
On 29 September, Mallikarjun Kharge demanded Gyanesh Kumar’s immediate removal.
Footnotes[18]
contextAnalystDelhi Police imposes assembly restrictions across New Delhi district
On 2 October, Delhi Police imposed assembly restrictions across New Delhi district.
On 2 October, Delhi Police imposed assembly restrictions across New Delhi district.
Footnotes[17]
contextAnalystMamata Banerjee demands Gyanesh Kumar’s removal at INDIA bloc meeting
On 2 October, Mamata Banerjee demanded Gyanesh Kumar’s removal at an INDIA bloc meeting.
On 2 October, Mamata Banerjee demanded Gyanesh Kumar’s removal at an INDIA bloc meeting.
Footnotes[21]
contextAnalystSupreme Court of India rejects calls to shut Delhi Metro
On 9 October, the Supreme Court of India rejected calls to shut Delhi Metro.
On 9 October, the Supreme Court of India rejected calls to shut Delhi Metro.
Footnotes[23]
contextAnalystAAP calls for Gyanesh Kumar to resign and announces Delhi march
On 13 October, the Aam Aadmi Party called for Kumar’s resignation and announced a Delhi march.
On 13 October, the Aam Aadmi Party called for Kumar’s resignation and announced a Delhi march.
Footnotes[20]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Story reports Kharge’s demand alongside differing allied positions. · reporting linkAnalystMallikarjun Kharge demands Gyanesh Kumar’s immediate removal → TVK stays cautious as allies seek India's chief election commissioner's ouster
The linked Story describes Kharge’s demand and varying allied positions.
The Story reports metro station closures ahead of a planned demonstration in the setting of the assembly restrictions. · reporting linkAnalystDelhi Police imposes assembly restrictions across New Delhi district → Delhi closes 11 metro stations ahead of planned Jantar Mantar protest
The Story reports closures ahead of a planned demonstration; it does not establish that the demonstration proceeded as planned.
The Event is linked to the Story reporting CJP detentions during SIR protests. · reporting linkAnalystAAP calls for Gyanesh Kumar to resign and announces Delhi march → Delhi Police detain CJP leaders again during SIR protests at Jantar Mantar
The linked Event and Story describe separate AAP and CJP actions.
The Event is linked to the Story describing INDIA bloc MPs weighing a fresh protest. · reporting linkAnalystSupreme Court of India rejects calls to shut Delhi Metro → India bloc MPs weigh fresh protest over alleged election vote theft
The Story also reports protest deliberations, but does not make them the cause of the Court’s decision.
The later Story concerns a separate Jantar Mantar protest-ban challenge, not the metro decision. · analytical connectionAnalystSupreme Court of India rejects calls to shut Delhi Metro → India Supreme Court considers technology in challenge to Jantar Mantar protest ban
The Court matters in both accounts, but the metro decision and the Jantar Mantar challenge concern distinct proceedings.
How a Situation is put together323 Stories · 301 Events · 323 membership connections · 6,215 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 773 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.