Architecture

Report in, street state out — one wall between

AnBanjir collapses to four layers with one rule: a report's personal context flows in and stops at the vault, and only corroborated street state flows out to the console and its surfaces. Here is the whole stack, an interactive model of the hardest promise — the alert that survives a dark tower — and the principles that keep a flood warning precise rather than a siren.

the stack

Four layers, one wall

01 · in

Sense

Three streams enter here: the council's own gauge and drain telemetry, a MetMalaysia radar cell taken as a lawful input, and ten-second crowd waterlines from residents. All arrive carrying context — a device, a reporter, a raw photo — and that context is about to be deliberately shed.

02 · the wall

The vault

Everything private stops at this layer. A waterline photo is corroborated here against gauges and neighbours, the reporter's confidence history is kept here, and the council's threshold lines are applied here. Nothing that identifies a resident or their device is allowed to leave — not encrypted, not access-controlled: absent from the outbound state.

03 · out

The street state

What the vault emits: the map. A street, a risk band, a rising hydrograph, which gates are closed, which routes are forbidden, which shelter is full. This is the only object the rest of the system is allowed to see, and it has no field that points back to a person who reported. The state is arithmetic over corroborated sensors, not a database of residents.

04 · act

Act & reconcile

One instance, many actors. The console dispatches a street-scoped alert, routes responders around the flood, updates shelters — and the state engine keeps mutating correctly on the council's LAN when the tower is dark, then reconciles legally on reconnect. Every action is downstream of the threshold; none can reach past the vault to a reporter.

design reference · the alert doesn’t need the tower

When the tower goes dark, the street still hears it

The failure that kills every ordinary flood app is simple: the warning only arrives while the network holds. Cut the mast. Watch the tower-dependent channels fall — and the offline engine keep firing. Pick a state and a street, and read exactly how the alert still gets there.

what happened to the network
choose a street
delivery channels · 5 of 5 reach the phone
App push over data

needs a working mast and a slot in the queue

Cell broadcast (CB)

mast-level, skips the data queue — dies with the mast

Peer mesh relayoffline-proof

phone-to-phone over Bluetooth — no tower, no SIM, no data

Council siren · TEINKoffline-proof

the loudspeaker mast on the roof, on its own power

Cached street planoffline-proof

the evacuation route already downloaded to the device

Lorong Sepuh 4
risk banddanger
lead time to act
~11 min
3 offline-proof channels always live
Every channel live

With the mast healthy, all five paths can fire and this street is inside its lead time. The engine still scopes the alert to the road that is rising — not the whole basin — so nobody's phone wakes for a flood two streets away.

This is an illustrative console over an illustrative matrix — not a live alerting system. The rule it demonstrates is the promise: no street’s warning depends on a single mast staying up. The offline delivery engine is a proven method inherited from AnKampung and AnVerified; the per-street nowcast that aims it is designed, not yet running. AnBanjir is designed, not yet running.

The principles

A report flows in and stops

A crowd waterline is more current than any gauge, so the vault keeps it — and keeps the reporter anonymous outside. The sighting strengthens the map; the person who sent it appears to every reader only as a street that is now correctly coloured.

The threshold is a wall, not a suggestion

Below the watch line the console sends nothing, even when a resident wants a number and even when a model is confident. The honest output for a quiet street is silence, and the architecture makes that the default, not a config option a stressed operator flips off.

Offline is the centre, not a fallback

The state engine is designed to run with no cloud at all, because the mast is the first thing a flood takes. Delivery degrades to mesh, siren and cached route in that order — a product that assumes four bars fails precisely when it is needed.

One council, one air-gap

The whole stack deploys to a single PBT. There is no foreign key from an AnBanjir street state to any neighbouring council or federal system — the separation is structural, which is what lets a state overlay be a licensed read-only product instead of a join.

The honest summary: AnBanjir moves street state, not people. A waterline sharpens a road’s band and stays in the vault; a reporter’s history protects the map’s honesty and is never published; a gate closing is a fact about infrastructure, not about who is behind it. What leaves is a street and its level — and there is no handle in it back to anyone who reported.

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.