Six faces, one signatory
AnBanjir reaches different hands through six surfaces — but every one is the same council instance, sold to the authority that actually answers for the flooded underpass. The resident, the control room, the responder, the state, and the offline relay underneath them all. Here is each face, honestly labelled by how far along it is.
The street warning
A push and SMS alert scoped to your actual road and your actual risk band — clear, watch, danger — not a state-wide siren that trained everyone to ignore it. It fires when your street's level crosses a threshold the council engineer set, and it says which way the water is moving.
The council console
One instance per local authority: thresholds, alert dispatch, gate and route state, shelter capacity, and the post-event record the audit and the next budget submission are written from. This is the operating layer no federal agency sells a council — the last kilometre of authority, not the science.
The nowcast map
The catchment drawn as street hydrographs, not a basin polygon — radar fused with the council's own gauges to answer which roads, this hour, in which direction. Confidence is published on every cell; a thin street reads "not enough to say", never a confident guess.
Responder & shelter routing
AnVerified-credentialed responders receive routed assignments that avoid the flooded underpass; shelters see incoming evacuees before the buses do. Being specified now, gated on a council champion and one monsoon of drill — the logistics layer that turns a warning into a movement.
The state overlay
Where a state or NADMA wants the picture across councils, they get a read-only overlay licensed separately — the aggregation is a product, never a join. Councils stay air-gapped from each other; the view up is a contract, not a foreign key.
The offline relay
When the tower is dark, the state engine still mutates locally — gates closed, routes forbidden, shelter counts current — and reaches phones over a peer-to-peer mesh and the council's own siren mast. This offline discipline already ships in AnKampung's gatehouses and AnVerified's rails; here it is reused, not reinvented.
Three lawful inputs. One street, eleven minutes out.
Federal radar, the council’s own gauges and a corroborated crowd waterline fuse in a per-catchment nowcast that runs on thresholds the council engineer set. It doesn’t answer “danger, somewhere” — it answers which road, this hour, and fires the bell scoped to that road when its level crosses the danger line.
This is an illustrative model, not a running nowcast. The figures are a shape, not a measurement — no live council instance exists yet. The rule it draws is the promise: resolution down to the street, the hour and the direction, with the alert scoped to the road that is actually rising. AnBanjir is designed, not yet running.
The catchment, on the console
The resident’s street warning and the council’s control room — rendered as honest design mockups, because there is no running council instance to photograph yet.
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.