Pods

Concepts

Your pod is everything on this machine your agent can search — your own vaults, ones shared with you, and ones you follow. More precisely, it is the local view of the vaults you can use on this machine: owned vaults, shared vaults, and subscriptions, organized through meshes.

VaultMarkdown plus stable identity Meshhomes, edges, and subscriptions Podeverything you can reach

What a pod is

A pod brings the local copies of your vaults and vaults you can read into one operating view. It records meshes, subscriptions, and local derived indexes, so Lyt can orient, search, and address the knowledge available on that machine.

One pod under a glass dome: meshes group vault containers on a shared base — the pod is one local view across all reachable vaults.

What can be in it

Ownedvaults you control locally and can publish when a remote permits it

Sharedprivate vaults another owner has explicitly granted you access to

Subscribedlocal copies of public vaults that update when you sync them

One local search surface

lyt search searches your pod by default; pass --vault to narrow it to one vault. Results come from the local markdown-derived indexes available to this pod, including the relationships represented by its meshes.

lyt search "federated vaults"

A local view, with explicit boundaries

A pod is local-first, not isolated by promise: sync uses configured Git remotes, and an agent may use an external adapter only when its operator configures one. The local pod does not silently convert those network choices into a background service.