Latest: Assam disaster authority says Sankosh level steady on Friday morning as Dhubri residents stay anxious
A glacial lake at Shintaphu in Bhutan's Gasa district burst on Thursday evening, sending about 7.4 million cubic metres of water into the Mo River. West Bengal moved thousands of people along the Sankosh to safer areas and Assam put Dhubri and Kokrajhar on alert.
By Friday morning the Sankosh was reported steady in Assam, and no major damage or casualties were reported in Kumargram. Summary updated 2 Nov, 07:42 IST
Why it matters: The Sankosh flows into Assam and north Bengal, so a flood from a Himalayan glacial lake puts border districts and thousands of residents at risk.
New developments are added here, newest first. When the headline, summary or other sections change, the earlier version is kept under “See earlier version”.
Summary before this update: A glacial lake at Shintaphu in Bhutan's Gasa district burst on Thursday evening, sending about 7.4 million cubic metres of water into the Mo River. West Bengal moved thousands of people along the Sankosh to safer areas and Assam put Dhubri and Kokrajhar on alert, with no major damage or casualties reported in Kumargram so far.
“What's missing” before this update:
Based on 11 articles read in full. Scores describe each article's framing, not the outlet and not whether it is accurate.
Large outlets read: 2 of 15 (The Hindu, India Today). Most of India’s largest outlets, including NDTV, India Today, Times of India, Hindustan Times, The Hindu and Indian Express, block our reader in this prototype, so their coverage is missing here. The launch pipeline reads their public feeds.
Outlets broadly agree on the facts and differ mainly on how many people were moved and on added detail such as Bhutan damage and climate context.
No real disagreement between sides in this coverage.
Why: Disaster report on a glacial lake flood and evacuation, with no policy, religion, security or social justice angle. Tone is factual and the response is described neutrally.
Why: Disaster-response report relaying official updates on a glacial flood. No religion, identity, social justice or statism framing, and no criticism or praise of any government.
Why: Disaster-alert report on a Bhutan glacial lake flood with no policy or identity angle; it relays official advisories and preparedness neutrally, with no praise or criticism.
Why: Disaster report on a glacial lake flood alert with no religion, identity, social-justice or economic-policy angle. Quotes the state minister's preparedness claims alongside resident accounts, without praise or criticism.
Why: Disaster report on flood alerts after a glacial lake outburst, with no policy, identity or welfare framing. Officials are quoted factually and no government is praised or criticised.
Why: A disaster report on a glacial lake flood and evacuations, with no policy, identity or statist angle. It relays official statements neutrally and does not criticise or praise any government.
Why: A disaster-alert report on a glacial lake flood with no engagement with religion, identity, social justice or statism themes; it relays state officials' statements plainly.
Why: Disaster report on a glacial lake flood and alerts in Assam and Bengal; no policy, identity or welfare angle, so not ideological. Plain factual wire copy with no government judgment.
Why: A disaster report on a glacial lake flood with no religion, social justice or statism angle; it relays official alerts and administration preparedness without praising or criticising any government.
Why: A disaster report on a glacial lake flood in Bhutan and alerts in Assam and Bengal. It has no policy, identity or statism angle, and no framing of the government.
Why: Disaster-preparedness report on a flood threat from Bhutan. It has no religion, identity, social-justice or statism angle, and it relays official alerts plus resident concerns without praise or criticism.
Critical, Neutral or Supportive, scored separately. It refers to the Union government unless the story is about a state. On the spectrum strip, each dot is an article: its position is the ideology score and its colour is the stance.
If an article would score differently with the parties' roles reversed, that signal is partisanship. It goes into the stance tag, not the ideology score.
High, Medium or Low, based on how much of the article was read, how many clear signals it has, and whether they agree.
Stories with fewer than five articles are marked. A blindspot is a contested story where we found coverage from only one side.
Articles that touch none of the three dimensions, such as a car launch or a match report, carry no ideology score.
This prototype is refreshed by hand (last on 17 Oct, 03:00 IST). At launch:
| Wires and the top 20 outlets | checked every 5 minutes |
| All other outlets | checked every 15 minutes |
| New story | goes up at 3 articles from 2 or more outlets, marked Limited coverage |
| Live stories | new articles added every 15 minutes; summary rewritten at most hourly |
| Home page order | every 15 minutes |
New facts go into a dated update log at the top of the story. New articles carry an “Added” tag. If a note or list changes, the earlier version stays viewable.
A story is Live while coverage arrives, Winding down after about 2 days without new coverage, and Archived after about 7. Nothing is deleted: links never change, archived scores are frozen, and stories stay on their issue pages and in search.
NDTV, India Today, Times of India, Hindustan Times, The Hindu, Indian Express, News18, ABP, Times Now and Mint block the reader used for this prototype, so their articles are missing. Each story shows how many of India’s 15 largest outlets we read. The launch pipeline will read outlets’ public feeds, TV transcripts and Hindi articles.
Editor-in-charge: S. Kalra, editor@thenazariya.com. The editor-in-charge sets Nazariya's editorial rules, reviews the AI desks' daily decisions, and is responsible for everything we publish.
How we work: AI reads and scores every article against our published rubric; an AI standards desk checks accuracy and fairness; people set the rules, review decisions and handle complaints.
Grievance officer under the IT Rules, 2021: to be confirmed (based in India). Until then, write to grievance@thenazariya.com. Complaints are acknowledged within 24 hours and resolved within 15 days. To report a factual error: corrections@thenazariya.com. Other questions: support@thenazariya.com.
Ownership: Nazariya is independently owned by S. Kalra, an Indian citizen.
Funding: Nazariya is currently funded entirely by its founder. It carries no advertising and takes no money from any political party, government or party-linked organisation. In future it will be supported by optional reader memberships. Any other funder, grant or investor will be listed here, with the amount and date.
Independence: No owner, funder or member can change a story, a score or a correction. Scores follow the published rubric, and anyone can appeal them.
Anyone, including the outlet that published an article, can appeal a score: tap any score on a story page, then "Appeal this score" to write to the editor. Outlets can also dispute a summary. The editor reviews every appeal, and any change is recorded below. Appeals: appeals@thenazariya.com.
No detail that could identify a child or a survivor of sexual violence (Juvenile Justice Act, POCSO, BNS section 72). Court cases are reported as what was said and alleged. No analysis of a poll in the 48 hours before voting there (Representation of the People Act, section 126). Press Council and NBDSA norms on communal incidents.