Why a Village, not just an app
Anyone can build an app now — the features are becoming free. What software can't spin up is the foundation underneath: who is accountable for your data, where it lives, what the AI is allowed to do with it, and whether your records still mean something in ten years. That is what a Village is built on.
Your Village runs inside standing guardians that bound what the system and its AI can do: hold a boundary, check a claim against the record, and require real deliberation before a decision lands. Safety is wired into how it works, not a policy page you click past.
The AI runs on our own sovereign inference stack — Qwen today, and our own Situated Language Model. Your members' words and documents are never sent to an overseas cloud model, and never used to train someone else's product.
Every decision, document and exchange becomes a sovereign record: tamper-evident, carrying its own provenance, exportable whenever you ask, and yours to erase for good — on infrastructure you control.
Villages connect to one another directly — to share, refer, collaborate — with no platform owner in the middle. You choose who to peer with and exactly what crosses the line. Reach, without surrender.
Anyone can claim a record can never be changed. We do something more useful, and more honest. Every decision is sealed so that if it is ever altered, the change is provable — and you can verify that yourself, with keys your Village holds, without taking our word for it. And because a real organisation must sometimes correct or supersede a record, legitimate amendments are recorded, attributed and added to the trail: the original always stands, and only silent, unauthorised change becomes impossible to hide. A record you can correct and still prove beats a promise you can't check.
Features get copied. A governed, sovereign, provable, federated foundation does not — because it isn't something you generate. It is something you are built on.