Software that serves people,
not the other way around.

PublicWerx is a constitution for digital services that refuse to exploit their users. It is not a company or a product; it is a permanent set of rules any project can adopt, and a public record of those who have.

The default is exploitation.

Most software exists to extract value from people. Ads, tracking, dark patterns, and engagement loops have become the industry standard. Services that start honest are often acquired, gutted, and rebuilt around ad revenue.

These patterns feel inevitable. They are not. They are choices.

PublicWerx is the framework for making them.

Why now.

The ideas behind PublicWerx are not new. What is new is that the infrastructure finally exists to make them real.

Users are tired of watching their favorite apps get acquired, gutted, and rebuilt around ad revenue. The word "enshittification" exists because the pattern is so common it needed a name. People are ready for something different. And for the first time, the infrastructure exists to deliver it. With L2 networks and stablecoins, you can run a global service without a bank, a payment processor, or anyone who can cut off your access. The GPL kept code free but did not protect users. Signal and Wikipedia proved the model works but used non-profit structures that are hard to replicate. PublicWerx combines ethics, UX, and financial architecture into a single commitment that any project can adopt.

The Constitution

Eight tenets defining user-respecting software. Numbered by priority. Public, versioned, and permanent.

01

Forever Service

This service will never be sold or acquired. Your data will never be handed to a new owner. We remain the stewards. This includes protection against governance capture. If we can no longer run it, everything transfers to the community under terms that preserve these tenets.

02

Users Are Not Products

We do not optimize for engagement metrics or "time spent." We optimize for utility. When you are done, go live your life. No ads, no dark patterns, no manipulation. We are funded by users, not advertisers.

03

Protect the Commons

The service must defend itself against abuse, exploitation, and bad actors. A trust-based system is not a naive one. This tenet is never a justification for restricting access based on an inability or unwillingness to pay.

04

Core Access Is Free

Essential functionality is a right, not a tier. The free version must be complete and genuinely useful on its own. Premium features are additive -- they never remove artificial limits. If a user who never pays would not recommend this to a friend, we have failed.

05

Data Minimization

Collect only what is vital. Default to "no collection." If in doubt, do not store it. Analytics, if any, must be opt-in only.

06

User-First UX

We do not ship features that benefit us at the cost of the user. If there is a conflict between our convenience and the user's experience, the user wins.

07

Radical Transparency

All changes that affect users -- data practices, pricing, features, policies -- are documented publicly and loudly. No quiet updates.

08

Stay Lean

Minimalist architecture, simple code, and no bloated abstractions. Build exactly what is needed to fulfill our commitment to the user -- nothing more.

The Zurich Principle

In Zurich, the trams have no turnstiles. You simply walk on and ride. The system operates on the belief that access comes first.

PublicWerx takes that spirit and builds software around it.

Trust over enforcement.

Instead of wasting resources on paywalls and DRM "enforcement theater," we invest those resources into the service itself.

The free user is not a bug.

By keeping the core service free, the tool remains a public good. Those who can afford to pay do so to sustain the infrastructure for everyone.

The commons model.

Financial status should never dictate access to essential digital tools. The service belongs to everyone who uses it, not just everyone who pays for it.

Unstoppable Access

No middleman -- bank, processor, or gatekeeper -- should have the power to de-platform a project or its users. We value censorship resistance over specific payment rails.

Tokens

Any token the project and its users agree on. Stablecoins like USDC and USDT are common starting points.

Networks

Any chain that serves the project's users. Ethereum, Base, Polygon, Arbitrum, and other EVM-compatible networks are well-supported options.

Wallets

Any wallet the user already trusts. MetaMask, Rabby, hardware wallets, or any WalletConnect-compatible interface.

Ethics

No payment data stored. No hidden fees. Verifiable on-chain.

Projects Under the Charter

The following projects have pledged to uphold the PublicWerx tenets.

MemeWhatYaSay

Live

A meme-based party game. Create, share, and vote. The core game is free, forever.

memewhatyasay.com

Hardware Wallet Pay

In Development

A minimal open-source Android app for P2P crypto payments via hardware wallet. No accounts. No tracking.

Adopt the Constitution

  1. Commit. Ensure your project goals align with the eight tenets.
  2. Document. Add a CONSTITUTION.md to your repository referencing these rules. Include a succession plan for your users and their data.
  3. Register. Open a pull request on the PublicWerx repo to be added to the official list.
  4. Uphold. This is not a badge; it is a commitment to your users.

Amendments

The constitution is versioned and can evolve. Any amendment must follow these rules:

  • Proposed via public pull request with a written rationale.
  • Open for community review for a minimum of 30 days.
  • No tenet may be removed or weakened. Tenets may only be clarified, strengthened, or added to.
  • All active adopters must be notified before any change is finalized.