Bring in a markdown folder you already have
Use casesYears of notes, in a structure you chose on purpose. Bringing them in should not mean rearranging them.
The situation
Someone already keeps years of notes in an Obsidian vault or a plain folder of markdown, with a structure they chose on purpose. Adopting that folder is additive: Lyt adds its own .lyt/ directory, registers the vault, and indexes what is there. The existing files, folder names, and links stay exactly as they were.
How you do it
Point your agent at the folder, name the vault, and say plainly that the structure is not to be touched. Then have it prove the index works by running one search against the vault it just registered.
Needs: Lyt initialized.
Using Lyt, adopt the existing markdown folder at ~/notes/obsidian-research as a Lyt vault named research/notes, homed in my personal mesh. Leave every file and folder exactly where it is — I chose that structure. Then confirm the vault is registered, tell me how many notes were indexed, and search research/notes for "meeting" so I can see the index working.
Adopt is additive: it creates a .lyt/ directory and registers the vault, and it does not modify your existing markdown. Point it at your own folder and pick your own vault name. Assumes Lyt is installed and initialized on this machine.
lyt vault adopt ~/notes/obsidian-research --name research/notes --mesh personalWhat changes
The folder becomes searchable and reachable by an agent, without reorganising a single note. Nothing about how you edit those files changes — the same editor, the same paths, the same links. The step-by-step version of this lives in the adopt existing markdown guide, including how to leave again cleanly.