Before the age of networks, before the age of code, before the age of the machine — there was an older agreement.
That which a community builds together belongs to that community. That which is given for the common good cannot be taken back by any private hand. These are truths older than law, older than commerce, older than the state itself. Every civilisation that has endured has built, in one form or another, on this foundation.
We, the Society of Open Systems, reconstitute this ancient agreement in digital form. We are builders and maintainers, practitioners and thinkers, scattered across geographies but aligned in purpose. We build tools that serve people — not markets, not investors, not governments, not ourselves.
The world holds billions of people whose digital needs are treated as afterthoughts by an industry that optimises for those who can pay most. We hold that this is not an accident of the market, but a failure of imagination and will. We choose a different path. And we always have.
Article I
Knowledge Is the Commons
The libraries of Timbuktu held hundreds of thousands of manuscripts, freely available to any scholar who came to read. The madrasas of Fez taught regardless of a student's wealth. The guilds of medieval Europe passed their craft to apprentices who would, in time, teach others. The great academies of Athens argued in public, not behind walls of payment.
In each age, the builders of lasting civilisation understood a truth that markets are slow to learn: knowledge hoarded is knowledge that dies. Knowledge shared is knowledge that multiplies. This is not sentiment. It is the empirical record of every enduring institution in human history.
We hold this as our first law: no knowledge produced under this Society's banner may be locked from those who could use it. Our code is open. Our documentation is open. Our methods are open. We do not build private forks. We do not accept terms that compromise this openness. The moment a tool becomes someone's property, it ceases to be ours.
"What we create, the world inherits."
Article II
The Sovereign Node Doctrine
A tool that cannot work without the permission of a distant server is not a tool. It is a lease arrangement. And lease arrangements can be revoked.
We have observed that the communities most in need of digital infrastructure are precisely those with the least reliable connectivity. The rural clinic in the highlands. The cooperative farm at the end of an unpaved road. The school in a valley the cellular towers have not yet found. The community health worker who travels three hours to reach the patients she serves.
For these communities, the cloud is a rumour. The internet is intermittent. The power grid flickers. We do not respond to this reality with apology. We respond with doctrine.
Every application we build must have a defined, complete offline state. When the network returns, synchronisation follows. But the absence of a network must never produce the absence of function. We call this the Sovereign Node — a piece of software that runs in the browser, on the device, in the hands of the person it serves, requiring the cooperation of no distant infrastructure. The network, when it comes, is a gift. It is not a requirement.
"The grid will fail. Our software must not."
Article III
Privacy Is a Form of Dignity
Ancient societies understood that there are matters which belong to the household, matters which belong to the community, and matters which belong to the public square. The failure to observe these distinctions is not an efficiency gain. It is the failure of civilisation itself.
The surveillance economy has collapsed these boundaries. It has decided that all human activity is, in principle, available for observation, analysis, and sale. It has dressed this collapse in the language of convenience and connection, and it has made billions of people complicit in their own diminishment. The philosopher who cannot think without being watched cannot think freely. The patient whose records are traded cannot trust her healer. The community whose movements are logged is not free.
We refuse this arrangement. Our systems are built on the principle of data minimalism: collect only what is needed; store only what is used; expose only what was explicitly shared; forget by default; remember only by consent. This is not policy. It is a principle of respect. The person using our clinic tool trusts us with their health. The person using our ledger trusts us with their livelihood. This trust is a sacred thing. We do not trade in sacred things.
"A mind that fears observation cannot think freely. We build tools for free thinkers."
Article IV
Affordability Is Not Compromise
There is a common error among those who build for constrained environments: they believe it means accepting a lower standard of craft. That offline-first means primitive. That low-bandwidth means ugly. That affordable means inferior. This error has produced decades of second-rate tools delivered to the world's most deserving communities.
We reject this entirely.
The constraints of the LMIC condition — limited memory, slower processors, intermittent power, smaller screens, unreliable storage — are not obstacles to good design. They are the design brief. The greatest engineering achievements in human history were accomplished not in spite of constraints, but because of them. Constraint is the mother of elegance. Scarcity produces clarity.
We hold that a Society tool must be as well-crafted as any tool made for the wealthiest user in the best-connected city — and it must also run on a five-year-old device, on two bars of signal, with half a battery remaining. This is not a lower bar. This is a higher one. We do not apologise for the people we build for. We are proud of them.
"Constraint is not our enemy. It is our brief."
The Protocols
Operating Agreements
These are not suggestions. They are the binding norms by which we operate, by which all Society software is judged, and by which we invite the world to hold us accountable.
Protocol Zero
The Public Good Test
Before any feature is built, ask: who does this serve? If the answer is not the user — if it serves the platform, the data collector, or the developer's convenience alone — do not build it. Return to first principles.
Protocol One
Offline First
Every application must have a complete, non-degraded offline state. Offline is not an error condition. For the communities we serve, it is frequently the primary condition. An app that requires the network to function has not yet been finished.
Protocol Two
No Dark Patterns
Our interfaces do not manipulate. No infinite scroll. No deceptive confirmations. No notification coercion. No hidden costs or misdirected clicks. What the interface says it does is precisely and only what it does.
Protocol Three
Open Codebase
All code produced under the Society banner is open source. We do not build proprietary forks. We do not accept terms that restrict openness. The code is the document. The document belongs to all who can read it. We publish stable, maintained applications—not experimental dumps. We are the custodians of our tools, responsible for their reliability and adaptation to community need. The code is open; the duty to maintain is ours.
Protocol Four
Minimal Footprint
Collect only what is needed. Store only what is used. Expose only what was explicitly shared. Forget by default. Remember only by consent. Every byte of unnecessary data is an unnecessary liability.
Protocol Five
Accessibility as Mandate
A tool that cannot be used by someone with impaired vision, limited literacy, or low motor control has not yet met its brief. Accessibility is not a feature to be added. It is a condition of completion.
Expectations
Of Those Who Build With Us
To join this Society as a contributor is to accept the obligations below. They are not complex. They are simply the demands of seriousness, and of respect for the people our work affects.
01.
Write code you could explain to the community whose lives it will affect — in plain language, without technical mystification. If you cannot explain it simply, it is not yet understood.
02.
Do not introduce dependencies that compromise the offline guarantee. Every external dependency is a potential point of failure for the user. Treat it as such.
03.
Document your work as if the next maintainer has never met you — because they probably have not, and they are working in difficult conditions.
04.
Treat a bug report from a community health worker in a remote district with the same urgency you would give any critical system failure. Their work is no less important. It may be more so.
05.
Do not seek individual acclaim at the expense of collective clarity. The Society's name outlasts any contributor. Act accordingly.
06.
When you discover that a design choice serves the developer at the expense of the user, change the design. Not the user's expectation.
07.
When you find a way to do something simpler, do it simpler. Simplicity is not laziness. It is respect for those who will maintain what you leave behind.
The Covenant
Our Pledge
We who bind ourselves to this Society agree:
To build as if we were building for the people we love most in the world.
To protect the data of those who trust us as fiercely as we would protect our own.
To never mistake the sophistication of a tool for the worthiness of its purpose.
To remember that the ultimate test of our work is not whether it runs in a well-equipped lab — but whether it runs when the tower falls, the power cuts, and the road washes out, and the clinic still needs to record who came through its doors.
To measure our success not in funding rounds, not in user acquisition numbers, not in press coverage — but in the Tuesday when everything went wrong and our software held.
To hold open, sovereign, privacy-first infrastructure not as a product offering, but as a moral position — one we will defend even when it is commercially inconvenient to do so.
"That which is created for the common good belongs to no one, and therefore, belongs to everyone."
So it is written. So we build.
— The Society of Open Systems · Anno Domini MMXXVI