Trust & security
Trust you can verify, not just take.
A community hands its platform the two things it can least afford to lose: its record and its money. Meridian's answer isn't "trust us" — it's a system where tampering is detectable, storage stays in the community's own hands, and no AI or administrator can quietly rewrite history.
The guarantees
How the record protects itself.
Security here isn't a checklist in an appendix. It's the architecture — and the parts that exist today are already doing this work for our pilot community.
A hash-chained record
Every entry in the decision record is cryptographically chained to the one before it. Deleting or editing history breaks the chain — and the break is detectable by anyone who checks.
Live todayYour records, your storage
Community records live in storage the community itself controls and authorizes — never a Meridian-held account. If you leave, your records were already yours.
Data sovereigntyAI bound to the evidence
Meridian's AI cites only from records it actually fetched. If the data isn't there, it says so and asks for it — it never invents a number to fill the silence.
No invented figuresEvery action attributed
Board actions, manager actions, AI suggestions — each one lands on the record with its owner attached. Append-only means accountability doesn't fade with time.
AttributionDual control for money
As money movement ships, it ships with dual-control approval and member-readable reconciliation — no single person moving community funds alone, ever.
PlannedOpen to the members it serves
Member access is scoped at the database layer — each member sees their own community's record because the system enforces it, not because an administrator allows it.
Member accessToday, the hash-chained record, community-controlled storage, and evidence-bounded AI are live and working for our pilot community. Dual-control money movement and the full member portal are on the roadmap — and will ship with these same guarantees, not exceptions to them.