Padmaavat Co-Writer Defends Jauhar Scene Against Swara Bhasker

Prakash Kapadia defends Padmaavat's Jauhar scene as historically accurate against Swara Bhasker's criticism.

TruthFoundry Desk

from the fact record

Stands on 5 placed sources from 2 publishers.

Prakash Kapadia, co-writer of Sanjay Leela Bhansali's 2018 period drama Padmaavat, reacted to criticism regarding the film's Jauhar sequence. ^[1] Kapadia stated that the depiction of the Jauhar scene was the reality of those times and described the situation as 'do or die'. ^[2] Prakash Kapadia stated that the makers portrayed the events according to their research and what is written in history books. ^[3] Kapadia explained that in Rajput tradition, Kesariya refers to men dressing in saffron robes and marching into battle to fight to the death when victory is impossible. ^[4] Kapadia reacted to Swara Bhasker calling the portrayal 'problematic' by stating that the controversy feels unnecessary to him. ^[5]

What this stands on

Prakash Kapadia, co-writer of Sanjay Leela Bhansali's 2018 period drama Padmaavat, reacted to criticism regarding the film's Jauhar sequence. · Mid-day

Kapadia stated that the depiction of the Jauhar scene was the reality of those times and described the situation as 'do or die'. · Mid-day

Prakash Kapadia stated that the makers portrayed the events according to their research and what is written in history books. · Mid-day

Kapadia explained that in Rajput tradition, Kesariya refers to men dressing in saffron robes and marching into battle to fight to the death when victory is impossible. ·

Hindustan Times

Kapadia reacted to Swara Bhasker calling the portrayal 'problematic' by stating that the controversy feels unnecessary to him. ·

Hindustan Times

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 · 5 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 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-03T12:21Z.

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)1275bcc033c346b3b06f50ac582b759fa2e3cd334c6af1d6497e62753f5afb70

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.