Meshes
ConceptsA mesh is how you group related vaults, so work and personal notes stay in their own lanes. Formally, it is a named topology for related vaults: it organizes membership and edges; it is not a central server or a sharing permission.
What a mesh is
A mesh names a group of vaults and the parent-child edges between them. Its declarations describe the relationship graph; local indexes project that graph for operations such as rollups and scoped search.
Membership and names
A vault has a home mesh, which contributes to its computed canonical display name {mesh}/{vault}. Moving a vault updates that display name without changing its stable rid. See identity and addressing for the resolution rules.
lyt vault init team/handbookEdges and rollups
Edges give Lyt a declared route across related vaults. Their derived rollups can widen what a mesh-scoped search sees, while the underlying markdown and YON records remain the source material. Use lyt mesh add-edge to declare an edge and lyt mesh rebuild-rollup to rebuild the local projection.
Topology is not permission
A mesh does not grant anyone access to a vault. Sharing and subscriptions are explicit Git and access-control choices, described in sharing.