Adopt an existing vault
Vault setupAlready keep notes in Obsidian, or any folder of markdown? Lyt adopts it as it stands — nothing moves, nothing is rewritten.
Before you adopt
Adopting means Lyt starts working with notes you already have — nothing moves, nothing is rewritten.
Confirm the directory contains the Markdown you intend to register. Adoption is local and additive; remote publication is a separate sync decision.
Register the folder
Point your agent at the folder and Lyt takes it from there.
Bring my existing markdown folder at /path/to/your-vault into Lyt.
Adoption is additive only: it adds a .lyt/ folder and never modifies your .md files.
lyt vault adopt /path/to/your-vaultAdoption creates Lyt's .lyt/ area, registers the vault, rebuilds its local index, and links installed patterns. Existing markdown files are left alone, and no remote is contacted.
Choose a home and inspect the result
Using Lyt, adopt that folder into my research mesh instead of the personal one.
lyt vault adopt /path/to/your-vault --mesh researchA bare adoption is placed in your personal mesh. Use --mesh when the vault belongs in a named mesh instead.
Leave cleanly
If Lyt is not for you, leaving is as safe as arriving: your notes stay exactly where they are.
Using Lyt, take my research notes vault back out of Lyt and leave my markdown exactly where it is.
Nothing is removed until you confirm it: the command refuses to act unless --yes is added, and that flag is the confirmation. It is not an exact inverse of adopting — it removes Lyt's own folder, deregisters the vault and drops its aliases, but leaves your markdown, any README or .gitignore changes, and the GitHub repository exactly where they are. A mesh's main vault cannot be abandoned this way.
lyt vault abandon research/notesAbandon removes only the local .lyt/ adoption state. Your Markdown and GitHub repository remain untouched.
Next: use the pod on another machine or share a vault.