cities alerting: Bhubaneswar, Cuttack, Puri, Sambalpur, Rourkela
scoring cycle, every day of the year, wet or dry
rule engine in production, with the active-flood hold
lead on all six onsets in the Aug 2026 replay
Four terms, and a gate.
Every term is a rule an engineer wrote and a district can argue with, which is the point, because an officer has to defend the call the next morning.
Rain 6 h
78 mm
p95 baseline
41 mm
Antecedent
3 wet d
Forecast 24 h
46 mm
One cycle, assembled term by term.
And the gate: river level only reaches the risk path when the station is marked status == live. Otherwise the briefing says the read is rainfall-only, out loud, and the score is capped accordingly.
Built for 3 a.m., not for a screenshot.
Cities ranked by severity, evidence open by default, and one suggested action per city. Small enough to read at three, complete enough to defend at nine.
Ranked by severity
- CuttackHIGH · 0.71
Mahanadi lower · rising
- BhubaneswarMEDIUM · 0.48
Mahanadi lower · no CWC station
- SambalpurLOW · 0.22
Mahanadi upper · Jamadarpali 181.68 m
- PuriLOW · 0.19
Coast · Nimapara unavailable
- RourkelaLOW · 0.14
Brahmani · Pamposh unavailable
Evidence mode · Cuttack
rule_score 0.71 · v2.3Rain 6 h
78 mm
p95 baseline
41 mm
Antecedent
3 wet d
Forecast 24 h
46 mm
- River
- Kishan Nagar 34.6% out of range · not counted · n/a
- Closest past event
- Nearest match in 653 labelled INDOFLOODS events, with what the following 48 hours did.
- Suggested action
- Pre-position at Naraj. Alert wards 4 to 9. Rainfall-only read, so treat river state as unknown.
The running surface is the War Room, which carries this same evidence view against live data. You can also rewind a real flood or read the Benchmark scoring without asking us for anything.
Location onsets caught, by lead time · Aug 2026 north Odisha
72 h
1 / 6
48 h
6 / 6
24 h
4 / 6
At seventy-two hours the engine caught one of six, so seventy-two hours does not appear anywhere on this site.
The recession failure: 14 of 18 location-days scored LOW while 13.44 lakh people were still displaced.
The rain had stopped; the water had not. The engine scores rainfall, not flood state, and the active-flood hold we built for exactly this keys off river level, which made it dead code for ungauged locations.
This is the single largest known gap in the system, and it is the reason real river telemetry is now in production.
Five is a decision, not a limit.
Expanding the alert map is the easiest way to look bigger and the fastest way to page a district officer about a location we have never validated. New geography goes to shadow first, every time.
Jajpur and Bhadrak are scored and logged with a shadow badge. They are not public alerts and they are not traction. The gate that opens them is the trust gate, and it is not passed.
D001 · recorded decision
What Flood Ops is not.
- It is not district-scale coverage.It is five cities.
- It is not a live ML system.The model is logged and cannot move a user-facing score.
- It is not validated against a passed trust gate.The gate is open.
- It does not replace IMD, CWC or OSDMA.It is advisory, and it says so on every screen.