Consent as Infrastructure: What Open Source Taught the World About Agreement

Words
663
Reading
3 min
Listen
Play
3M

Consent as Infrastructure: What Open Source Taught the World About Agreement

The problem with implicit agreement

Most of the agreements that structure our lives were never explicitly made.

You did not agree to be raised in a particular language, to absorb the value structures of a particular culture, to inherit a particular set of assumptions about what constitutes a normal life. These agreements were made for you by the circumstances of your birth, and they operate with extraordinary efficiency because you were inside them before you could question them.

This is not, primarily, a critique. Some things cannot be consented to before the fact. You cannot consent to being born, to childhood socialization, to the existence of gravity. The structure of any life requires a significant amount of inherited agreement, or it would spend itself in continuous renegotiation of first principles.

The problem is not inheritance per se. The problem is when inherited agreement becomes invisible — when the terms we accepted without knowing we were accepting them become impossible to examine because we cannot see them as terms.

What the GPL did

In 1989, Richard Stallman published the GNU General Public License. It was, superficially, a software license. More fundamentally, it was an attempt to make visible a term that had been invisible in software distribution: the term about who gets to modify and share the code.

Proprietary software implicitly agreed to: you may use this, but the terms of that use are ours to set, modify, and revoke. Most users never saw this as a choice — it was simply the condition of software. The GPL made it a choice by providing a clear alternative: you may use, modify, and distribute this, provided you extend the same terms to anyone you distribute to.

The GPL did not just license software. It created the conceptual infrastructure for a question: what kind of agreement do you actually want to be inside?

Consent as something you build

The lesson WOLNO takes from open source is not primarily about software. It is about consent as an active practice rather than a passive state.

Most ethical and legal frameworks treat consent as a binary: it is present or absent. You consented or you didn't. This is useful for specific transactions — medical procedures, contracts, sexual encounters. But it is too thin a concept for the diffuse agreements that structure everyday life.

Open source proposed something thicker: consent as the ongoing maintenance of legible terms. The license is always readable. The modification history is public. The fork is always possible. You know what you're inside, and you have technical and legal recourse to leave it or build something different.

Legibility is consent infrastructure. You cannot meaningfully consent to terms you cannot read, in language you cannot understand, that can be changed without notice. This is not a controversial claim when stated abstractly. It becomes controversial when applied to the actual agreements we live inside: platform terms of service, employment contracts, national laws written in technical language for specialists.

The WOLNO practice

The practice WOLNO proposes here is: make your agreements visible to yourself.

This means periodically examining the implicit agreements you are operating under. Not to renegotiate all of them — most of them are fine, and renegotiating everything is a kind of madness. But to see them as agreements rather than as facts.

The operating system of a life contains many default settings. Most are reasonable defaults set by a particular context at a particular time. Some are no longer appropriate. None of them are immutable.

The first step in changing a term is seeing it as a term.

Open source showed that making invisible terms visible is technically possible, economically viable, and culturally generative. It created an entire mode of production that runs on legible agreement rather than inherited assumption.

The infrastructure is there. The question is whether we will extend it from software to everything else that governs how we live.


WOLNO — an experiment in legible freedom — 776f6c6e6f.org

Consent as Infrastructure: What Open Source Taught the World About ... | Ecency