Six community modules, one ledger
AnKampung takes the small, scattered jobs a kampung already runs in a WhatsApp group — hazard reports, borrowing, rotas, time-swaps, gardens and the school van — and gives each one a real tool. Every module writes to the same append-only event spine, so the whole community stays one honest book rather than six little ones.
Small tools, the same spine
All six are honestly tagged in formation — designed and specced on the event contract, not yet shipped to the pilot. They are shown here as what the platform is built to make cheap, because they are all the same shape: more events on one ledger.
AnWarn — hazard reports
from the walk to the gate
A blocked drain, a live wire, a dark lamp post — photographed and posted from the walk to the gate. Reports walk the same legal state machine as work orders, so nothing quietly closes; verified hotspots become the community's own risk map, and only banded, consented counts ever leave it.
AnPinjam — the lending shelf
the drill, the ladder, the camping mat
Catalogued once, borrowed and returned on the same append-only log. Trust is a per-person history inside one community; it never joins across tenants, because your record in PJS 8 is nobody's business in Ipoh.
AnRot — the event rota
kenduri & gotong-royong rosters
Kenduri shifts, gotong-royong weekends, the raya open-house roster. Volunteers sign up, the rota holds, and a shift nobody covered stays honestly grey on the committee's view — the platform never marks a roster green it cannot prove.
AnMasa — time banking
an hour for an hour
An hour of maths tuition traded for an hour of plumbing, hour-for-hour on a ledger the committee itself caps. Deliberately not money: balances are bounded, non-transferable and transparent, so a neighbourhood system never trips into e-money territory by accident.
AnKebun — urban farming
shared plots on the facilities ledger
Shared plots and raised beds booked through the facilities ledger, harvests logged, surplus listed — and what a garden cannot eat flows straight onto the AnKedai surplus board instead of into a bin. The produce trail uses the same events as everything else.
AnBas — family pings
the school van, honestly tracked
The school van and the community bus, tracked by driver check-ins as the signal — no hardware sold to a family. Parents get an honest 'five minutes out' or a plain 'no signal yet', the same refusal AnOmbak applies to grey roads: never invent the vehicle's position.
One ledger, four guarantees
A module is not a new database or a new login. It is a namespace of events on the spine the resident app and the gatehouse already trust — which is the whole reason the sixth one is cheap to add.
One append-only log
Every module writes to the same event spine — a borrow, a rota sign-up, a hazard report, a garden harvest is one more fact appended to the ledger, never a row edited in a private little table.
One state machine
AnWarn reports and maintenance work orders walk the same legal transitions. The engine rejects an illegal one and quarantines it — a module cannot invent its own shortcut to 'closed'.
One trust boundary
A record is a per-person history inside one community. Nothing joins across tenants: the same row-level security that fences the resident app fences every module by the tenant id on every table.
One entitlement switch
Modules are namespaces inside the monolith, turned on per community by edition and licence — a config layer, not a fork. Switching AnKebun on for a neighbourhood changes no schema.
The modules read from the same Community Digital Twin the platform surfaces do, and the intelligence that could ever be layered on them stays strictly optional and never load-bearing.
Bring your community onto its own spine.
One gated enclave at a time — identity, money, gatehouse and governance that a committee can actually trust.