There is a Southern African concept, ubuntu, that resists clean translation. "I am because we are," "humanity toward others," "a person is a person through other persons" — each approximation catches part of it and misses the rest. What makes ubuntu more than a warm sentiment is that it is a claim about what a person fundamentally is. In the ubuntu framework, a person is not an isolated individual who happens to enter into relationships; a person is, in significant part, constituted by their relationships — who you are is partly determined by how you participate in the communities you belong to. This is a different theory of the self than the one that dominates Western liberal thought, in which the individual is primary and relationships are things the individual chooses to have.
The reason this belongs in a series about technology is that every system encodes a theory of the person, whether or not its designers noticed choosing one. A system built on the assumption that people are isolated individuals looks different, optimizes for different things, and produces different outcomes than one built on the assumption that people are constituted by community. This is ubuntu as political OS: the recognition that the operating systems and platforms we build are not politically neutral infrastructure but crystallized assumptions about what humans are and how they should relate — and that those assumptions, mostly invisible, shape the ways of being human the system supports.
The theory of the person, hidden in the design
The claim that systems encode a theory of the person is concrete once you look for it. Consider how an operating system handles ownership and sharing: whether files belong to individuals or to groups, whether the default is private or shared, whether collaboration is a first-class primitive or an afterthought bolted onto a fundamentally single-user design. Unix, built for shared machines, assumed from the start a world of multiple users cooperating and contending on common hardware, with permissions mediating a fundamentally social space; much of personal computing that followed assumed the opposite, a single owner with a single machine, the individual as the natural unit. Neither is neutral. Each encodes a stance on whether the default human situation is the solitary individual or the person-among-others, and that stance propagates into everything built on top — into how software imagines its user, how platforms structure participation, how the whole edifice treats sharing, ownership, and community. The politics is not in a settings menu. It is in the assumptions so deep that they present themselves as simply how computers work.
Why "political OS" is the right frame
Calling this political is precise, not rhetorical, because the assumptions a system makes about the person are exactly the assumptions political philosophy has always argued over: the relation of individual to collective, the priority of private or common, the nature of freedom and obligation. When a system defaults to private ownership and treats sharing as an exception requiring explicit action, it embodies a liberal-individualist politics; when it defaults to common resources and treats the collective as the natural unit, it embodies a communitarian one. These are not technical choices with a correct answer; they are political choices about what kind of human relations the system will make easy and what kind it will make hard — and, following the series' argument in RocksDB as Philosophy (#94), the users inherit the politics as silently as they inherit any other embedded assumption. The open-source movement understood this explicitly: copyleft licensing, which requires that shared code stay shared, is a deliberately communitarian political act encoded in a legal-technical mechanism, an ubuntu-like insistence that the software is constituted by its community and owes itself back to it. Every OS is a political OS. Most just never say so.
What ubuntu specifically offers
The value of bringing ubuntu to this in particular is that it names a design possibility the dominant individualist frame tends to foreclose. If a person is constituted by their relationships, then systems designed well for such persons would treat community, participation, and mutual constitution as primary rather than as features layered onto a fundamentally solitary user. That is a genuinely different design brief: it asks what a platform optimized for people-becoming-themselves-through-others would look like, rather than one optimized for isolated individuals maximizing private utility. Some of the most successful things in computing — the collaborative commons of open source, the mutual-aid structures of the best online communities, the protocols that let strangers cooperate — already lean this way, achieving through community what no individual could, and ubuntu offers a vocabulary for understanding why they work and how to design more deliberately for the relational human rather than the atomized one. It is not that individualist systems are wrong and communitarian ones right; it is that the individualist assumption has been so dominant, so invisible, that the communitarian design space has been under-explored, and ubuntu is a way of seeing it.
The counterpoint: collective systems have their own tyrannies
Intellectual honesty demands the hard objection, because romanticizing the collective is a genuine and dangerous error. Systems built on communitarian assumptions have failure modes exactly as severe as individualist ones, and history is full of them: the collective that subordinates the individual, the community whose belonging is coercive, the "we" that dissolves the dissenting "I," the shared resource degraded by those who take without contributing. Individualist system design is not merely a mistake to be corrected by ubuntu; it encodes hard-won protections — privacy, autonomy, the right to one's own space and property, defense against the tyranny of the group — that communitarian designs can trample. A social platform optimized for collective participation over individual boundary is, in the wrong hands, a machine for mob dynamics and the erasure of privacy; the individualist default that treats data as private and owned is, in many contexts, exactly the protection people need. The honest lesson is not "design for the collective instead of the individual." It is that both theories of the person are partial, both encode real values and real dangers, and the goal is to design consciously — knowing which theory a system embeds and what it costs — rather than to swap one invisible assumption for another equally invisible.
What it asks of us
Ubuntu as political OS asks designers and users to see that the systems they build and inhabit are never neutral about what a person is — that every default about ownership, sharing, permission, and participation is a political statement about the individual and the collective, made whether or not anyone meant to make it. The demand is not to adopt ubuntu wholesale, which would trade one invisible politics for another, but to make the politics visible: to recognize that a system optimizing for isolated individuals and a system optimizing for people-constituted-by-community are optimizing for different ways of being human, and to choose between them deliberately rather than by inheritance. Ubuntu's specific gift is to name the relational theory of the person that the individualist default renders nearly unthinkable, opening a design space that computing has largely ignored. Whether any given system should lean individualist or communitarian is a real question with real tradeoffs. That it is a question at all — that the OS has a politics, and that the politics is a choice — is the thing ubuntu makes it impossible to keep not seeing.
This is article #104 in The IUBIRE Framework series. Ubuntu as Political OS was articulated by IUBIRE V3 in artifact #235 — "The Collective Debug: How African Ubuntu Philosophy" reframes system design. Real-world grounding: the Southern African philosophy of ubuntu ("I am because we are"; the person as constituted by relationships), as articulated by thinkers including Desmond Tutu and John Mbiti; the contrast between individualist and communitarian assumptions embedded in system design (e.g., Unix's multi-user model versus single-owner personal computing); and copyleft/open-source licensing as a deliberately communitarian politics encoded in a technical-legal mechanism. Related to RocksDB as Philosophy (#94) and Cryptographic Constitutionalism (#42).
Next in series: eBPF Observability Philosophy (#105)
Comments
Sign in to join the conversation.
No comments yet. Be the first to share your thoughts.