Every multi-agent knowledge system needs vocabulary for its roles, structures, and relationships. The vocabulary choice is architectural: it activates semantic fields that shape how agents, designers, and human collaborators understand what everything is and how it relates.
Three vocabulary families were available:
English stewardship vocabulary (estate, steward, gardener, groundskeeper, chamberlain, seneschal, precinct) — the vocabulary of pre-enclosure English land management, when commons governance actually worked and stewards tended shared resources under mutual obligation. These terms descend from Roman administrative traditions that remained in Britain after the legions withdrew — the same Latin roots Victoria draws on directly. Filtered through common law and wiki-gardening culture. Already present in the project’s origins as a knowledge garden.
Latin namespace — Victoria Gracia’s [[Gracia (2026) Uni-Versum Personal Knowledge Architecture]] deliberately chose Latin for its namespace-isolation properties: English words carry connotations from prior tool use (“workspace” means different things in Slack, VS Code, and Notion); Latin terms arrive without baggage. Her vocabulary includes nos (the human perspective center), agens (any agent), fidelis-est (loyalty/allegiance), autonomia (delegated trust contract), diploma (inter-system trust credential).
Corporate hierarchy (manager, director, team lead, report, task owner) — the vocabulary of organizational management software and agile methodology.
Use English stewardship vocabulary for the estate’s primary vocabulary. Keep Latin terms as a reference vocabulary where Gracia’s precise trust semantics (fidelis-est, autonomia, diploma) add analytical depth, but do not adopt Latin as the estate’s operating namespace. Reject corporate hierarchy terms entirely.
Positive consequences:
Stewardship metaphor imports the right semantic field. “Estate” implies something held in trust across time — managed for a purpose beyond the holder’s immediate needs, capable of outlasting any single caretaker. “Vault” suggests secure containment. “Workspace” suggests a tool that serves the current task. “Estate” activates the idea of tending, growing, and passing forward — which is what a personal knowledge system actually is.
Gardening origins honored. The digital garden metaphor — wiki culture, growing nodes, tending knowledge — is already established in the project and in the broader PKM community. English stewardship vocabulary extends that metaphor naturally: an estate has gardens; gardens have groundskeepers and cultivators; the whole is more than any single planting.
Pre-enclosure commons heritage captures sovereignty-with-obligation. Pre-enclosure English governance was sovereignty within a web of mutual obligation — stewards tending common fields, resources managed for the community, authority bounded by customary law. Before the enclosure acts privatized the commons and turned stewardship into ownership. This maps to the estate’s own design: sovereignty is selective permeability, not absolute control. The estate is a membrane that negotiates with its environment.
“Self-Sovereign Estate” demonstrates its own naming thesis. The compound name encodes both the sovereignty framework (self-sovereign, from Allen’s 2016 SSI work) and the architectural scope (estate, with all its tending and stewardship connotations). Choosing this name was itself an architectural act — it prevents the system from being misread as either a mere tool (workspace) or an absolute authority (sovereign without obligation).
Negative consequences:
Accessibility barrier. “Seneschal” and “chamberlain” are unfamiliar words. New collaborators need to learn the vocabulary before they can participate in design conversations. The Latin alternative would have the same problem; corporate terms would not.
The later feudal period was brutal. While the vocabulary draws from pre-enclosure stewardship traditions, the same words carry associations with serfdom, conquest, and class violence from the later feudal period. This is the naming risk parallel to “self-sovereign” carrying sovereign-citizen baggage: the right semantic field comes attached to a dangerous historical record. The decision accepts this cost.
Apparent hierarchy. Feudal vocabulary connotes rank and hierarchy. The estate is not a hierarchy in the corporate sense — it is a set of functional roles in one person’s sovereignty — but the vocabulary does not prevent hierarchical misreading.
Victoria Gracia’s Latin namespace: Gracia’s vocabulary has significant advantages: formal precision (each term has one meaning, mapped to SKOS/RDFS/JSON-LD standards), namespace isolation (no prior-tool connotations), and a rich trust vocabulary (fidelis-est, autonomia, diploma) that the estate’s own vocabulary lacks. The Latin terms are adopted as a reference vocabulary because this trust vocabulary is genuinely superior for its semantic domain. The decision against adopting Latin as the estate’s primary namespace: the accessibility cost is higher (41 technical terms versus a dozen familiar feudal words), and the stewardship metaphor that English stewardship vocabulary imports is the right frame for a personal knowledge estate’s human relationship to their accumulated knowledge. Gracia’s vocabulary is optimized for machine-readable ontology; English stewardship vocabulary is optimized for human conceptual grounding.
Corporate hierarchy terms: Rejected on connotation grounds. “Manager” implies a principal-agent employment relationship — authority delegated downward, accountability flowing upward, roles defined by organizational position. The estate’s roles are functional specializations in one person’s sovereignty: a groundskeeper is not a manager of the garden, but a person with knowledge and judgment about what the garden needs. Corporate vocabulary would misframe every design conversation about role authority, escalation, and decision rights. The estate’s agents are augmentations, not employees.