A protocol that holds nothing it could leak
AnBanjir's privacy is not a promise someone could break under pressure — it is the shape of what the system is allowed to output. One council, street states only, an engine that informs but never commands. Here is the doctrine, and the open questions a real council tender would still have to answer.
What crosses the wall — and what never does
Four rules, written into the schema
States, never individuals
The output is a street and its level — an object about infrastructure, not people. A cell whose only support is a single uncorroborated report publishes a state of "unconfirmed", and that is the answer a resident and a hostile audit both accept.
The engine informs, the council decides
AnBanjir has no authority to order an evacuation and never claims any. It raises a bell and stages a route; the YDP and the council engineer, who already answer for the underpass, make the call. The separation keeps a warning system from becoming an unelected commander.
PDPA 2024 by design
Mandatory breach notification and RM1M-class penalties make hoarding residents' flood photos everyone's worst quarter. AnBanjir holds no personal data to breach — the cheapest compliance posture is the one with nothing in hand when the hall loses power.
Weight earned, not assumed
A crowd report moves the map only after corroboration; a reporter carries a pseudonymous confidence history, not a name. Panic and fabrication both cost weight, not anonymity — the map stays honest or the alert bell loses its meaning.
The honest open questions
A product this honest about authority has to be equally honest about what it has not worked out. These are being designed with the first council champion, not claimed as solved.
Who moves a threshold mid-event?
An unprecedented deluge makes the council's own watch line wrong in real time. The engineer can raise or lower it, but the governance answer — who signs off, how the change is logged for the audit — is being specified with the first council champion, not pretending to be settled.
How is a serial false reporter handled without naming them?
AnVerified makes a repeat fabricator recognisable to the model while invisible as a person. Where the line sits between protecting the bell's credibility and tracking an individual is a live design question we state as open.
What protects the people inside a shelter?
The console needs shelter capacity to route buses; capacity is a count of displaced families. The discipline is to publish only the number and never a location-linked list — but the tension between logistics and privacy is real and we leave it visible rather than papered over.
When does a report port out of AnKampung?
A resident's flood report can become a consented contribution to their council's instance — but the default is no transfer, and the state overlay opens only once council data quality earns the licence. The public trust in the bell comes before any aggregation up.
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.