Questions, answered honestly
Straight answers about what AnBanjir is, how it differs from JPS, MetMalaysia and NADMA, why a photo isn't enough to move the map, how the offline engine still warns a street when the tower goes dark, whether crowd reports can be trusted, why it signs with one council only, and exactly where the product is today — with the same refusal to overstate that keeps a status grey until it's earned.
The basics
Council flood intelligence that reads the street, not just the river. It fuses the council's own gauges, a MetMalaysia radar cell and consented crowd waterlines into a per-street nowcast, runs an offline-hardened response console, and routes evacuees — sold one local authority (PBT) at a time, to the body that actually answers for the flooded underpass.
How it works
Because that is the resolution flood warning has never reached — not a state-wide siren, but this street rising, this hour, moving in this direction, with enough lead time to close a gate or divert a bus. The whole product is built around answering the only question that matters at 4pm on a monsoon afternoon.
Privacy & the street
No — by construction, not by policy. Outputs are street states: a road, a band, a level. A raw waterline is corroborated inside the vault and never published; a reporter is accountable to the model through AnVerified pseudonymous rails and invisible to every reader. There is no field in the output that points back to who sent it.
For the council
No, and that limit is deliberate. The product raises a bell, stages a route and shows a level; the YDP and the council engineer, who already hold the mandate and answer for the underpass, make the call. A warning system that pretended to command would be both unsafe and politically impossible to sell.
Offline & trust
The engine is built to answer this from AnKampung's gatehouses: state mutates locally — gates closed, routes flagged, shelter counts current — on the council's LAN, and reconciles legally on reconnect. The alert still reaches a phone over a peer-to-peer mesh, the council's own siren mast, and the route already cached on the device. This offline path is a proven method, not a promise.
The roadmap
The offline state engine and the credentials rails already ship in AnKampung and AnVerified; gauge telemetry and radar as inputs are existing public capability; the threshold-against-level decision is plain arithmetic. Those are the pieces it starts on solid ground — the alert survives a dark tower because the mechanism is already real.
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.