Official warnings for border districts, confirmed received, and flagged when the network is down.

Official warnings exist, and most of them are short-lived. SACHET's all-India feed lists its latest 100 alerts, about a day of warnings. Most of the alerts SANDESHA holds for border and coastal districts warn of thunderstorms or lightning and are valid for three hours or less, so they are useful only if they arrive within minutes. Lightning killed nine people in three Bihar districts in a single day (Telangana Today, 12 Aug 2026).

Getting a warning to a border post or a village is the hard part. Mobile internet, broadband and landline services were suspended across Doda district in Jammu and Kashmir from 17 to 21 July 2026, with no published order (Internet Society Pulse). No shared record shows which posts and villages an alert reached.

• One inbox of official CAP alerts for the districts on India's land borders and coast, from IMD, CWC and state disaster management authorities, with severity, status against the clock, and the issuer's own text in every language it was sent.
• Places each alert in districts by the official LGD code where the issuer gives one, by name, by sub-district, or by the official polygon, and shows the evidence for every match.
• Flags alerts that were valid during an IODA outage signal in the state: May not reach. Long-running and nationwide drops are shown separately in grey, because they are weaker evidence.
• Records receipt per post, village council and harbour, over SMS, voice, wireless set, satellite phone, marine VHF, public address or messenger, in an append-only, hash-chained log that the oversight officer can verify.
• Shows coverage over 30 days: which frontier districts got alerts, which got none, and which alerts overlapped an outage.
• Publishes a free public page of active official alerts for border and coastal districts, with 112 and the official sources.

1. ReadThe all-India and 29 state SACHET feeds, then each CAP 1.2 file, parsed field by field with conformance checks.
2. PlaceLGD geocodes first, then district and sub-district names, then reference points inside the official polygon.
3. FlagIODA outage events per state, overlapped with each alert's validity window.
4. RelayInbox, alert page and public page; text shown as issued, labels in four languages marked for review.
5. RecordReceipts hash-chained with SHA-256 in the SAKSHI format, kept 90 to 120 days.

The full method, with matching rules, thresholds, the outage heuristics and known failure modes, is in the public methods note and, with live retrieval times and match counts, on the console's methods page.

SACHET served polygon files to our build network at some times on 21 October 2026 and refused them at others. The district list and its codes were built from OpenStreetMap and Wikidata on 21 October 2026 and are rebuilt on demand. The relay roster is synthetic, with generic labels and no locations; a deployment loads the district's own roster on its own servers.

• District disaster management authorities: which official alerts cover the district now, and which posts and villages have confirmed them.
• Border posts and coastal stations: one inbox instead of many apps, readable when only a wireless set works.
• Panchayats and harbour offices: the official text in the issuer's languages, and the public page to share.
• State emergency operations centres: which frontier districts get alerts, which get none, and where the network dropped.

• SANDESHA never changes an alert's meaning. Official text is shown verbatim, with a link to the SACHET file; only field labels are translated, and those are marked as needing local review.
• Outage flags restate IODA's measurements as facts. They do not explain an outage or describe any community.
• Acknowledgements are personnel records: they name a roster unit and a channel, never a person, and are deleted 90 to 120 days after entry, leaving a receipt.
• Places, events and conditions only. No person profiles, no scores.
• Advisory relay. Every page names IMD, CWC, NDMA, INCOIS, NCS, the Coast Guard, state authorities and the district administration as the sources to follow.

• The static site updates when the pipeline runs, so it can be hours behind SACHET.
• Alerts that describe their area only as a count ("9 Mandals") stay unplaced until their polygon file is read.
• IODA measures states, not districts, and cannot see a local SMS failure. No flag does not mean delivery.
• The archive holds what the feeds still list when the pipeline runs; busy state feeds roll over within days.
• In this build the acknowledgement log lives in the operator's browser; a deployment keeps it on the district's server.

We are looking for two border districts to pilot SANDESHA with their own roster, on their own servers. contact@trinetra.in