Governance & the money wedge
A community platform earns trust in the two places people are legally and emotionally serious about: money and power. AnKampung models billing against Malaysian strata law, gives a committee a console whose every action is an auditable event, draws a hard line where e-voting law hasn't caught up, and treats personal data as an architectural constraint written down for legal review.
Community money is a legal object
Billing is where a community platform either earns a committee's trust or loses it. AnKampung treats it as compliance first — the Strata Management Act expressed as an auditable ledger — and never as a place to quietly hold someone else's ringgit.
Answer to Act 757, not the app store
Billing is modelled on the Strata Management Act 2013 and its 2015 regulations: maintenance charges, the sinking fund at its statutory rate, numbered receipts and arrears tracking. It is compliance expressed in ringgit, with an audit trail a committee and an auditor can both follow.
The 10% sinking fund, first-class
The default statutory sinking-fund contribution — 10% of charges, a body free to fix more by resolution — is encoded as an explicit, auditable line rather than a footnote. It is the exact number whose mismanagement is a documented Malaysian condominium failure, so the platform refuses to make it invisible.
Numbered receipts, real rails
Payments ride regulated FPX / DuitNow gateways and settle into sequentially numbered receipts. Money moves through the same finance ledger a facility booking's deposit already touches, so there is one book — not a payment app bolted beside a cash note.
Never custodial funds
AnKampung does not hold the community's money. A committee's ringgit should trace to the law that governs it, not to a vendor's balance sheet — so the platform orchestrates payments on regulated rails and keeps no float, no pooled account, no quiet custody.
Every act of governing is an event
The console a committee runs the enclave from does not keep a separate, softer record. An acknowledgment, a circular, an approval and a poll are each facts on the same spine the money office and the gatehouse already trust.
Announcements with acknowledgment
A notice records that it was acknowledged, not merely that it was sent. Delivery-proof becomes a fact on the ledger, so 'I never saw it' has an honest answer either way.
Circulars & approvals
Committee circulars and approval workflows run on the same state discipline as everything else — an approval is an event, traceable to who raised and who signed, never a verbal maybe.
Community polls
Opinion polls belong to the community console and are useful and honest for exactly that — gauging a mood. They are, by design, kept well away from anything statutory.
Where the law hasn't caught up
The honest part of governance is knowing what the software is not allowed to pretend. These two constraints are designed in, not discovered later.
App polls ≠ strata votes
Malaysian strata e-voting is not yet legally valid. So statutory AGM and EGM voting is kept architecturally separate from app polls — by deliberate design, not by oversight. The platform will not hand a committee a number that looks like a legal vote but isn't one.
PDPA by design, pending review
Consent and purpose limitation follow the Personal Data Protection Act 2010. Retention durations and the permission matrix are written down as named profiles and scope mappings — and honestly flagged as design proposals awaiting Malaysian legal sign-off, not guessed at by a developer at 2 a.m.
PDPA, written down
A Malaysian community is trilingual and governed by the Personal Data Protection Act 2010. Rather than improvise compliance, AnKampung names its retention profiles, its permission matrix and its cross-disclosure guardrails as explicit design proposals — and flags the ones still awaiting counsel.
Retention profiles
Financial, governance, security, membership, communication and telemetry each carry a named retention profile with a proposed duration and the Malaysian statute behind it. The values live in the event registry, so counsel can move a number without touching the engine.
A permission matrix, in writing
Access is resolved by named permission scopes against a concrete role→scope matrix the engine reads by name. Sensitive rows are marked for legal confirmation, and the whole matrix can be re-tuned after review without rewriting a single spec.
The cross-disclosure guardrail
One owner must never see another owner's arrears detail, and a household member never another household's records. That is enforced with record-level predicates, not just a coarse scope class — PDPA purpose-limitation made real in the data layer.
Honest status. The structure — the profiles, the scope names, the guardrail predicates — is decided. The statutory numbers and the sensitive permission rows are design proposals explicitly marked pending Malaysian legal sign-off in the platform's own contract. The project says so in writing rather than implying a compliance it has not been given.
Every governance guarantee above rests on the same engine discipline — the ledger that makes an acknowledgment, a payment and a receipt auditable facts rather than claims.
Bring your community onto its own spine.
One gated enclave at a time — identity, money, gatehouse and governance that a committee can actually trust.