Vault access

• Owned — a vault you control, which may remain local or be connected to a remote.
• Shared — a private vault whose owner has explicitly granted you read or write access.
• Public — a vault whose remote is already readable by anyone, which others can then subscribe to as a local copy. Lyt does not make a vault public for you: the repositories it creates are private, and changing that visibility is a step you take on GitHub yourself.

Two senses of publish meet here. Everywhere else in these docs — and in lyt sync — publishing means pushing your vault to its own remote, which stays private unless that repository is already public. Making a repository readable by the world is a different act, and not one Lyt performs.

Share a private vault

Grant a collaborator explicit read or write access to the vault's Git remote. Lyt reflects that permission when it checks or syncs the local copy; write access is never inferred from mesh membership.

Subscriptions are local copies

lyt mesh subscribe clones a vault whose remote is already public and adds it to your local pod as a subscription. It can be refreshed through sync; the local copy stays read-only, and the upstream remote remains the publisher's boundary.