The engine that turns rain into a route
Beneath every surface sits the same short pipeline: ingest the gauges, nowcast the radar, corroborate the crowd, hold to the council's threshold, scope the alert to one street — and keep all of it mutating when the tower goes dark. Here is each module, and how far along it genuinely is.
Gauge telemetry ingestion
The council's own water-level staff gauges and drain sensors stream in as the ground truth the map is pinned to. Reading a gauge is ordinary telemetry, already done by JPS and the PBTs — AnBanjir binds those readings to a street, not just a river.
Radar-cell nowcasting
A MetMalaysia radar cell, taken as an input the council already has rights to use, drives a per-catchment model that projects the next hour street by street. It answers "which roads, this hour, which way" — not "danger, somewhere." The mechanics are fixed; no live instance runs yet.
Crowd waterline corroboration
A ten-second photo of a rising kerb moves the map only after it is matched against gauge telemetry, hazard layers and neighbouring sightings. An uncorroborated report shows as unconfirmed — visible, honest, zero-weight. The sighting and the map state are deliberately different objects.
Council threshold engine
The watch and danger lines are set by the council's own engineer, per catchment, and are the product's spine. Not a vendor default someone can flip: the alert fires on the line the authority that answers for the underpass drew, so the bell stays defensible to the people it wakes.
Street-scoped alert delivery
The alert is addressed to the road that is actually rising — push and SMS to phones inside that band, nobody else woken for a flood two streets away. Scoping is what a state-wide siren never was: precise enough that people still act on it after the third quiet week.
Offline state engine
Gates closed, routes forbidden, shelter counts current — the state mutates on the council's LAN with no cloud and reconciles legally on reconnect. This is AnKampung's gatehouse discipline lifted whole: a flood product that needs four bars is a flood product that fails during the flood.
Evacuee route solving
Around the flooded underpass, to the shelter that still has capacity, recomputed as the water moves. Being specified now, gated on a responder champion and the street-level state the nowcast feeds it. The routing layer that turns a warning into a movement, not a stampede.
Panic & fabrication triage
Noticing a burst of implausible waterlines from one account or one corner during a live event. Genuinely useful, genuinely hard to do without turning a reputation into surveillance — so it is planned to run on pseudonymous contributor rails, inside one council's partition, never across people.
The hardest module is the offline engine, not the model
Nowcasting and corroboration are solved engineering. What makes AnBanjir survivable in the hour that matters — tower down, hall dark, buses moving — is the state engine that keeps mutating correctly with no network at all, and the mesh that still carries the alert to a phone. The offline path is the product; everything else feeds it.
Follow the thread deeper
Warn the street. Route the rescue. Keep the map alive when the tower dies.
AnBanjir is designed, and it is built to be adopted one council at a time — a single PBT owns its catchment, its thresholds, and its console; nothing joins across councils. The opening offer is a reference deployment: one flood-prone catchment, one control room, one offline-capable state engine. Council enquiries are welcome today.