System Administration Is Feudal Lordship
metaphor folk
Source: Governance → Software Engineering
Categories: software-engineeringsecurity
From: Novel Metaphors Evaluation Set (2026-03-16)
Transfers
The feudal-lordship metaphor maps the political structure of medieval European feudalism onto the authority hierarchy of system administration. Where the genetic-inheritance metaphor focuses on the mechanism of permission propagation, this metaphor focuses on the political economy of administrative power: who has it, how it is delegated, and what constrains its exercise.
Key structural parallels:
-
Sovereign authority — the feudal lord holds domain over land, people, and local law. The king or emperor grants this authority, but within the lord’s domain, the lord’s word is final. This maps onto the root user or system administrator who holds unrestricted access to a system. The organization grants this authority, but within the system’s boundaries, root can do anything: create or destroy accounts, read any data, modify any configuration, halt any process. The metaphor captures the qualitative difference between admin and non-admin access — it is not a matter of degree but of kind, like the difference between a lord and a serf.
-
Vassalage as delegated administration — a lord cannot govern a large domain alone. He grants portions of authority to vassals: a baron oversees a sub-region, a sheriff enforces local law, a steward manages the household. Each vassal exercises real authority within their sub-domain but derives that authority from the lord and can have it revoked. This maps onto delegated admin roles in modern systems: the database administrator who controls schema and access within the database, the network administrator who manages firewall rules and routing, the security administrator who configures authentication policies. Each has real power within a bounded domain, each derives that power from root, and each can be stripped of it.
-
Serfs bound to the land — serfs could not leave the lord’s domain without permission. They worked the land, paid rents, and had no legal standing to challenge the lord’s decisions. This maps onto regular users confined to their authorized resources: they can access what they have been granted, they cannot escalate their own privileges, and they have no mechanism to override admin decisions. The metaphor makes visceral the power asymmetry that abstract access-control models sanitize: the admin is not a “higher-privilege user” — the admin is a different class of entity entirely.
-
Arbitrary justice — the feudal lord served as judge in local disputes, with no separation between executive and judicial authority. The lord who made the rules also enforced them and adjudicated violations. System administrators occupy the same structural position: the person who configures access policies also monitors compliance and decides consequences for violations. There is no separation of powers. This is why insider threats from privileged users are so difficult to detect and prevent — the lord investigates crimes committed in his own domain.
Limits
-
Authority is personal and hereditary in feudalism, role-based in systems — a lord’s authority was inseparable from his person and passed to his heir. The domain did not have “a lord role” that different people rotated through. System administration, by contrast, is (or should be) a role that can be assigned, rotated, and revoked. The feudal metaphor’s connotation of personal, permanent authority fights against the principle of temporary, least-privilege access. When teams internalize the lordship metaphor, they resist rotating admin credentials or implementing just-in-time access because it feels like deposing a rightful ruler.
-
No duty of care — feudalism was not mere tyranny. The lord owed obligations to his serfs: military protection, access to justice, and maintenance of common lands. The relationship was exploitative but reciprocal. System administrators have no analogous contractual obligation to users. They can delete data, revoke access, or restructure systems based on organizational directives that may actively harm individual users. The metaphor’s feudal framing imports a sense of noblesse oblige that obscures the reality: admin power is constrained by policy, not by reciprocal duty.
-
Romanticizes the security anti-pattern — the metaphor makes concentrated, unconstrained authority feel like a natural and legitimate governance structure. Lords should have absolute power over their domains; that is what lordship means. But modern security practice treats root access as a liability to be constrained, audited, and minimized. The metaphor naturalizes what Zero Trust architecture explicitly rejects: the idea that any single entity should be trusted with unchecked authority.
-
Ignores the abolition of feudalism — feudalism was replaced by constitutional governance with separation of powers, rule of law, and enumerated rights precisely because concentrated authority proved catastrophically fragile and abusive. The metaphor stops at the medieval period. If extended to its historical conclusion, it argues for its own obsolescence: just as feudalism was replaced by distributed governance, root-level administration should be replaced by fine-grained, auditable, distributed access controls.
Expressions
- “Root is king” — shorthand for the unrestricted authority of the superuser account
- “The BDFL” (Benevolent Dictator For Life) — Guido van Rossum’s title in the Python community, explicitly feudal in its framing
- “Revoking someone’s keys to the kingdom” — removing admin access
- “Granting fiefdoms” — delegating administrative sub-domains to team leads or specialized admins
- “The serfs have no say in this” — acknowledging that regular users have no input into infrastructure decisions
References
- Bloch, Marc. Feudal Society (1939, trans. 1961) — the definitive historical analysis of feudal political structure and obligation
- Saltzer, Jerome H., and Michael D. Schroeder. “The Protection of Information in Computer Systems.” Proceedings of the IEEE 63.9 (1975) — the principle of least privilege as a counter to feudal-style authority concentration
- Raymond, Eric S. “Homesteading the Noosphere.” (1998) — explores the feudal dynamics of open-source project ownership and authority
Related Entries
- Permission Delegation Is Genetic Inheritance
- Roles Are Theatrical Costumes
- Technical Decisions Are Territory
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Mordor (mythology/metaphor)
- The One Ring (mythology/metaphor)
- The Senex (mythology/archetype)
- A Bad System Beats a Good Person (/mental-model)
- Big Brother Is Surveillance (science-fiction/metaphor)
- Authority Is Height (spatial-location/metaphor)
- Servant Leadership (leadership-and-management/paradigm)
- Three Laws Is Ethical Programming (science-fiction/metaphor)
Structural Tags
Patterns: center-peripheryforcecontainer
Relations: containenableprevent
Structure: hierarchy Level: generic
Contributors: agent:metaphorex-miner