The Vault

The Vault

A shared desk of plain markdown

The Vault is a folder of markdown notes you and Navi share — her desk, open to you. It lives at config/vault/ inside the install folder: ordinary .md files in ordinary folders, no database, no proprietary format.

Obsidian compatible, by construction:

• Open config/vault/ in Obsidian as a vault and everything just works — the same files, both ways.
• YAML frontmatter is preserved exactly as written; the editor shows it raw and the preview never mangles it.
• [[wikilinks]] and #tags are first-class text: clicking a wikilink in Preview jumps to that note, or offers to create it.

Working in it, and how Navi uses it

In the Vault view:

1. The editor sits on the left and the Files tree — the navigation panel — on the right, Obsidian-style, each in its own column across the full width of the view. The panel's create row carries New note and New folder with their full labels, wrapping instead of crushing, and every note and folder carries a single ⋯ menu holding its actions — Move, Rename, and Delete (with a confirm) for notes; New note and Delete for folders — so the names take the row's full width. Drag a note onto a folder header — targets light up while you drag, and a drop anywhere else changes nothing — or use the note's ⋯ menu and pick the folder, which is how it works by touch. On a phone the panel becomes a toggleable full-width Files panel. Drop markdown files from your computer onto the vault to import them — other file types are refused in plain words.
2. The editor autosaves as you type and says when it saved; Edit, Split, and Preview modes sit on one toggle, rendered by the same markdown renderer as chat and these Docs.
3. The side panel shows each note's Backlinks, Outgoing links, and Tags; the top bar searches the whole vault, opens (or creates) today's Daily note, and exports the vault as a .zip of the folder itself. Files in a Templates/ folder are offered as starting templates for new notes.

Her side of the desk is Navi's Desk/: when a conversation produces something worth keeping — a decision, a finding, something you asked her to remember — she files a dated note there and tells you she did; when a vault note informs one of her answers, she names it as a source, the way she names a RAG pack. Your side is Operator/, and she never edits it silently: she writes there only when you ask her to in chat, and she says what she filed.

Keeping it. The vault folder is on the installer's persistence keep-list beside her chips, packs, Soul, and Memory: updates, reinstalls, and --fresh installs preserve it. In Settings → GitHub & Backup it is listed with chips and packs as an optional include; Soul, Memory, and Settings stay the always-ticked core.