The Founding Document

The Manifesto

Version 1.1 · Adopted 22 April 2026 · Clarified 2 August 2026

“That which is created for the common good belongs to no one, and therefore, belongs to everyone.”
Preamble

The Common Agreement

Technology built for the common good must remain answerable to the people who depend on it.

We, the Godsway Sackey Free Apps, put people and communities before institutional, political, or commercial incentives. We build tools people can inspect, adapt, keep, and use on their own terms.

Article I

Useful Software First

Each application should communicate its purpose, limits, readiness, and operating requirements clearly. Documentation should explain how the system works, how it can be supported, and where its limits lie.

Useful software must not expose personal data, credentials, safeguarding information, or unresolved security vulnerabilities.

Knowledge hoarded is knowledge that dies. Knowledge shared is knowledge that multiplies.
Article II

The Sovereign Node Doctrine

A tool that cannot perform its essential work without the permission of a distant server leaves its user dependent on that server.

Every released application publishes an offline contract: which core tasks work without a network, what is stored on the device, what requires connectivity, and what happens when connectivity returns. Core records remain readable and exportable offline.

The grid will fail. Our software must not.
Article III

Privacy Is a Form of Dignity

Our systems are built on data minimalism: collect for a stated purpose; store only what is needed; expose only what was deliberately shared; retain for a defined period; and make deletion and export understandable.

A mind that fears observation cannot think freely. We build tools for free thinkers.
Article IV

Affordability Is Not Compromise

Offline-first must not mean primitive. Low bandwidth must not mean careless. Affordable must not mean inferior.

Each application declares and tests its support budget: target devices, browsers, download size, network needs, storage behavior, and core performance. Constraints are design inputs, not excuses for a diminished experience.

Constraint is not our enemy. It is our brief.