Identity & addressing
ConceptsEvery vault keeps one permanent ID that survives rename and move, so anything that points at the ID still finds the same vault. A vault's rid is its stable identity. Names, aliases, and origin coordinates are ways to resolve that identity without making a display name permanent.
The rid is the identity
Each vault has an rid, a UUIDv7 minted locally. It remains stable when the vault is renamed or moved between meshes, so references can continue to identify the same vault across those changes.
The canonical display name
Lyt computes the human-readable name from the home mesh and leaf name:{mesh}/{vault}. For example, company/handbook identifies the handbook's current home, but the rid—not that display string—is the underlying identity.
lyt vault info company/handbook --jsonWays to address a vault
- Canonical name — use
{mesh}/{vault}for an unambiguous, readable local reference. - Bare leaf — convenient only when it resolves uniquely; collisions are reported rather than guessed.
- Pod-local alias — an
@aliaspoints to a rid and survives a rename or move. - Origin coordinate —
lyt:vault:<host>/<owner>/<repo>identifies a remote origin across pods.
Why the distinction matters
The separation lets Lyt improve organization without breaking durable references. lyt alias gives people a short local handle; stored or cross-pod references should prefer the canonical name or origin coordinate when appropriate.