A generic valley is a screensaver. Your valley is evidence.
Every flood platform demo opens with terrain. Almost all of it is invented, and everyone in the room knows it, so the visual carries no weight at all. It is treated as wallpaper and skipped.
The moment the terrain is the actual basin, the hero stops being decoration and starts doing the same job as the replay: it is a claim that can be checked. An officer can look at where we put Cuttack and tell us if we are wrong.
Five cities, every thirty minutes, wet or dry.
A rule engine an engineer wrote and a district can argue with. Rainfall against each location’s own thirty-year threshold, yesterday’s rain that stops decaying during an active flood, and a river term that only counts when the gauge is genuinely live.
The position, August 2026 - stated the way we would want it stated back to us
cities alerting: Bhubaneswar, Cuttack, Puri, Sambalpur, Rourkela
scoring cycle, every day of the year, wet or dry
lead on all six onsets in the August 2026 north Odisha replay
location-days scored LOW while people were still displaced
The ML model runs beside the engine in shadow and cannot alter a user-facing score. Heat has no live mode in the code at all. There is no signed MoU and no paying customer.
The trust gate is not passed, and the hero does not pretend otherwise.
The flood engine alerts on five cities. The ML model runs beside it in shadow and cannot alter a user-facing score. Heat has no live mode in the code at all. There is no signed MoU and no paying customer.
In production, driving user-facing alerts.
Measured on history. Never quoted as live accuracy.
Computed and published, structurally unable to alert.
The engine was wrong, and here is the write-up.
Every claim on this site carries one of those labels. Read the evidence before you believe the thesis, including the numbers that went against us.
The only metric that matters: one family, one more day
Name a flood. We will fly it and replay it.
Pick an event your district remembers. We run the unmodified engine on the forecast as it was issued that week, over the ground it actually happened on, and you see exactly when it would have fired, or that it would not have.
District pilot
One district, one monsoon, and a standing invitation to tell us every time we were wrong.
Replay request
Name an event your district remembers. We run the unmodified engine on the forecast exactly as it was issued that week.
Investors
We are raising a pre-seed. The engine already runs in production. What it lacks is reach, so the raise buys an ML engineer and a partnerships lead.