Ten convicted in 2013 Jhiram Ghati Naxal attack that killed Congress leaders

An NIA special court convicted 10 accused in the 2013 Jhiram Ghati Naxal attack that killed Congress leaders in Chhattisgarh.

TruthFoundry Desk

from the fact record

Stands on 6 placed sources from 2 publishers.

On 25 May 2013, Naxalites attacked a Congress party's Parivartan Yatra in the Jhiram Ghati area of Darbha region in Chhattisgarh, India, killing many senior Congress leaders and a large number of people. ^[1] Thirteen years after the attack, a special court of the National Investigation Agency (NIA) convicted 10 accused in the case. ^[2] A special NIA court in Chhattisgarh has convicted all 10 accused individuals in the 2013 Jhiram Ghati Maoist attack. ^[3] The case had a total of 11 accused, one of whom had died before the verdict. ^[4] The court has scheduled September 16 to hear arguments regarding the quantum of punishment for the convicted defendants. ^[5] An eyewitness said that Naxalites danced on the body of Mahendra Karma, a senior Congress leader killed in the attack. ^[6]

What this stands on

Thirteen years after the attack, a special court of the National Investigation Agency (NIA) convicted 10 accused in the case. · Amar Ujala

A special NIA court in Chhattisgarh has convicted all 10 accused individuals in the 2013 Jhiram Ghati Maoist attack. · Deccan Herald

The case had a total of 11 accused, one of whom had died before the verdict. · Amar Ujala

The court has scheduled September 16 to hear arguments regarding the quantum of punishment for the convicted defendants. · Deccan Herald

An eyewitness said that Naxalites danced on the body of Mahendra Karma, a senior Congress leader killed in the attack. · Amar Ujala

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

Article provenance · 6 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Saturday, September 5, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events

What they stated is the numbered source list above.

Why these sources, and not others

How the desk chose them

We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.

Where they publish from

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

2 · The recordextracted those reports into signed fact rows

AI · semantic search

The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.

This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.

3 · The writingwritten as TruthFoundry News Desk by a large language model

AI · news generation

The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-05T12:32Z.

The prompts, verbatim

System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts

4 · The filingwritten to the permanent record

Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.

Integrity

Content hash (SHA-256)1ae83f885d85a48547fd7e00386d55d015082e4819bd4ad3cf31d7b6b2e8cbe3

Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed

Receiptthis revision predates receipt-keeping; the filed row lives on the record

Machine readablethe full proof, JSON

Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.