In software development, there is a version number that functions as a philosophical confession: 1.0. Everything before 1.0 is beta, alpha, preview, experimental — language that signals not-quite-yet. Version 1.0 is the declaration that a thing is finished, ready, complete. It is the moment when the makers step back from the object and say: this is what it is.
And then, almost immediately, 1.0.1. A patch. A fix. A small adjustment that 1.0 required in order to actually be what it claimed to be. Then 1.1, which adds something that was always missing. Then 2.0, which reconsiders something fundamental. The version number keeps climbing because the thing is never, actually, done. The declaration of completeness was always a useful fiction — a way of releasing the work into the world, not a description of the work's ontological state.
The software development community has, over decades of painful experience with this dynamic, developed a counter-tradition: the practice of shipping early and shipping often, of embracing the perpetual beta, of treating every version as a draft rather than a declaration. This is not cynicism about quality. It is an honest reckoning with the nature of complex systems: they are not completed; they are cultivated. You do not finish a garden; you tend it, and the tending is the whole story.
The WOLNO philosophy arrives at the same insight by a different path, through the snail rather than the server farm. But the snail, it turns out, knows something about unfinishedness that the software engineer is still learning.
The Myth of the Done
Every culture that has produced both art and technology has produced, alongside them, the figure of the completed masterpiece: the painting that is finished, the building that is done, the theory that is settled. This figure serves important social functions. It allows exchange — you can sell a finished thing, cannot easily sell a process. It allows criticism — you can evaluate a completed work against a stable object. It allows legacy — a finished thing can be attributed, transmitted, preserved.
But the masterpiece is also a kind of violence against the work itself. The painting that is declared finished is no longer allowed to change. The moment the frame goes on, the possibility of the painting becomes the actuality of the painting, fixed. Everything the work could have become that it did not become is now foreclosed. The completion of a thing is also the death of its possibilities.
There is a famous story, probably apocryphal but useful, about Michelangelo's Sistine Chapel. The Pope, impatient, would call up to the scaffold: when will you be finished? Michelangelo would call back: when I am done. The tension in this exchange is not merely between patron and artist; it is between two different relationships to the work. The Pope needed a completion date. Michelangelo needed the work to be allowed to become what it was becoming.
The WOLNO tradition, in its fifth dogma — which resists easy translation but might be rendered as powolność applied not to speed but to finality — suggests that incompleteness is not a failure state. It is, in many cases, the appropriate state of living things.
Systems That Are Done, Stop
There is a biological observation embedded in this claim that is worth making explicit. Living organisms are not completed. They are, at every moment, in process: metabolizing, adapting, responding, changing. The state of life is incompletion. A fully completed organism — in the sense of one that has reached its final, stable form and is no longer changing — is, by definition, dead.
This is not a metaphor. It is a literal description of how biological systems work. The human body is replacing most of its cells on a continuous basis. The brain is forming and pruning synaptic connections throughout life. The immune system is constantly encountering, learning, and forgetting pathogens. You are not the same physical object you were ten years ago — not approximately, but literally: most of the atoms are different, most of the cellular structures are different, many of the neural connections are different. You are a process that maintains a pattern, not an object that maintains an identity.
The snail understands this. It does not complete its shell and then stop adding to it; it adds to the shell as it grows, the shell's spiral a record of the snail's expansion, each new whorl a draft of the organism's relationship to its own size. The shell is a growth diary written in calcium carbonate. It is, at every moment, unfinished — and that unfinishedness is what makes it alive.
Systems that achieve completion — in the sense of closure, of having resolved all their tensions and addressed all their needs — are systems that have stopped growing. And systems that have stopped growing have, in the relevant sense, stopped living. This is as true of organizations as it is of organisms, as true of philosophies as it is of gardens.
The Ethics of Beta
To call something a beta version is, conventionally, to apologize for it. It is not yet what it will be. Use it with caution. Report bugs. This is the beta as prelude, the beta as lesser-than.
But there is another way to understand the beta: as the honest label for everything that is alive. Every living system is in beta. Every idea that has not calcified into dogma is in beta. Every relationship that is still growing is in beta. The beta is not the version before the real version; the beta is the state of being genuinely in process, genuinely responsive to what it encounters, genuinely capable of revision.
The finished thing — the 1.0, the masterpiece, the dogma — is what happens when a system closes itself off from revision. Sometimes this is necessary; sometimes the moment of completion is a gift to the world, the offering of something stable that others can build on. But when completion becomes the only acceptable state — when the beta is always an embarrassment, when the draft is always hidden, when the unfinished work is always private — something is lost.
What is lost is the permission to be visible while still becoming. The permission to share a thought that is not yet fully formed. The permission to build something that you know has flaws, because the alternative is to build nothing until you can build it perfectly, which means to never build anything at all.
This permission is harder to grant than it sounds. We live in a culture of the highlight reel, where what is shared is curated to show the completed, the polished, the arrived-at. The process is private. The drafts are deleted. The false starts are not merely undisclosed but actively hidden, because to be seen in process is to be seen as not-yet-good-enough.
The WOLNO tradition's insistence on openness — its fourth dogma, which could be rendered as otwartość, a porousness to the outside, a willingness to be seen in one's actual state rather than one's ideal state — pushes against this. Openness means being legible while incomplete. It means allowing the trail to be read before it is finished.
Version Numbers as Philosophy
There is something worth attending to in the particular form that software versioning has taken. The major.minor.patch structure (2.1.4, say) encodes a hierarchy of change: patches are small corrections; minor versions add features without breaking existing behavior; major versions change something fundamental, possibly breaking what worked before.
This structure acknowledges that change comes in different registers. Not all change is the same. A patch is not a revolution; a major version is not a bug fix. And the numbering never reaches infinity — there is no version 9999.0.0 that represents completion. The numbering just continues, the acknowledgment that there will always be a next version, that the work is never done, that done is not the point.
Philosophical systems would benefit from this structure. Every major philosophical work presents itself as, in some sense, final — as the answer, or at least as a significant step toward the answer. But philosophy that is honest about its own history knows that it is always, in the software sense, a version: building on what came before, departing from it in some ways, preserving it in others, and inevitably to be built upon in turn.
The WOLNO five dogmas are themselves a version. They have a history; they will have successors. The particular formulation they have received is contingent — it reflects the moment of its writing, the language in which it was written, the particular anxieties and insights of those who articulated it. To treat them as complete would be to misunderstand them. They are a beta release, offered in the spirit that a beta should be offered: as the best current thinking, subject to revision, grateful for engagement.
The Discomfort of Incompleteness
None of this is easy. The permission to be incomplete is a permission that must be actively chosen, repeatedly, against a persistent inner voice that insists on readiness, on finished-ness, on having-worked-it-out before speaking.
This voice is not entirely wrong. Some incompleteness is premature sharing — is the author's responsibility to the reader abdicated in favor of the author's convenience. The draft that is offered as finished because the author is tired of it: this is a different kind of incompleteness from the version that is shared openly, honestly marked as in-process, asking for engagement. One is incompleteness masquerading as completion. The other is incompleteness as a form of trust.
The trust that incompleteness requires is mutual. The sharer must trust that the receiver will understand what beta means — that the cracks in the surface are not deceptions but honest disclosures. The receiver must trust that the sharer is not being lazy or evasive but genuinely offering what they have, not what they have been able to finish.
In a culture organized around the finished product, this trust is eroded. We have learned to present ourselves as done, to package our thoughts as conclusions, to share our art only when it is (we imagine) unassailable. The cost is that we show each other only our surfaces, and then wonder why we feel unseen.
The Snail's Shell Is Never Finished
Return, finally, to the snail. Its shell is built incrementally, each new layer deposited at the growing edge, the spiral widening as the animal inside it grows. There is no moment when the shell is complete. While the snail is alive, the shell is still being written.
This does not make the shell fragile or provisional. It makes the shell alive. The incompleteness is not a flaw to be apologized for; it is evidence of the continuing life of the system that produces it. A finished shell — one that is no longer growing — is the shell of a dead snail, or of a snail that has been separated from its shell, which amounts to the same thing.
The art of inhabiting incompleteness is, in the end, the art of remaining alive to the possibility of change. Not change for its own sake — not the restless revision of things that are working, not the perpetual dissatisfaction with anything that exists — but the simple refusal to close off the future. The refusal to declare that what you are now is the final version of what you will be.
The snail knows this refusal. It carries its always-unfinished home on its back and moves through the world at the speed at which the world can be genuinely encountered. It does not rush toward completion. It does not apologize for being in the middle. It is, at every moment, exactly what it is: a living system in the process of becoming what it has not yet become.
That is not a deficit. That is the whole practice.