Better tools. Better news.
Sunday, November 22, 2026 · UTC
World

Ashwini Vaishnaw reviews Indian Railways Cyclone Akvan preparedness

Union Minister Ashwini Vaishnaw reviewed Indian Railways Cyclone Akvan safety preparations.

TruthFoundry News Desk
References:
Share on X
Stands on 6 placed sources from 2 publishers.
Union Minister Ashwini Vaishnaw reviewed Indian Railways preparedness for Cyclone Akvan. [1] Andhra Pradesh was struck by severe cyclone Murasu near Ongole on 3 November 2026 [2] Cyclone Akvan is forecast to intensify and make landfall between Narsapur and Puri on 20 November 2026 [3] Cyclone Akvan preparations prioritise passenger safety, railway infrastructure protection, train service regulation, and swift post-cyclone restoration. [4] S.S.V.S. Ramakrishna stated El Niño increases post-monsoon cyclone formation in the Bay of Bengal [5] This report was last updated on 18 November 2026 at 17:50 IST. [6]
Proof6 sources · 2 publishers · signed
What this stands on
  1. Union Minister Ashwini Vaishnaw reviewed Indian Railways preparedness for Cyclone Akvan. · Deccan HeraldIndia
  2. Andhra Pradesh was struck by severe cyclone Murasu near Ongole on 3 November 2026 · The HinduIndia
  3. Cyclone Akvan is forecast to intensify and make landfall between Narsapur and Puri on 20 November 2026 · The HinduIndia
  4. Cyclone Akvan preparations prioritise passenger safety, railway infrastructure protection, train service regulation, and swift post-cyclone restoration. · Deccan HeraldIndia
  5. S.S.V.S. Ramakrishna stated El Niño increases post-monsoon cyclone formation in the Bay of Bengal · The HinduIndia
  6. This report was last updated on 18 November 2026 at 17:50 IST. · Deccan HeraldIndia
All of them publish from India. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · signed receipt ✓ · 6 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, November 18, 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 across 2 source articles
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
All of them publish from India. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
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
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
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)3b4c1089705a7213e7c7bfb6e68ad0c39d09be9d343a4d157f866bde24708b5f
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)djnmd4pyxdGk9t5Rno3nLV9O1jffJLCZm9SjexA5_mhjWOuhhEZaARWKZ2sp1g2B5cwpbCVqZQUUhWzFs2C1Bg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hash7c056dfd1cc44db8b588e6bdf89681ab7e3ceaf739bfa8a169aea5e869d834d2
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.