Skip to main content

Your first vault

A vault is one life domain of your memory — your onboarding profiles already created some. Here's how to create one yourself, feed it, and stay in charge of it. (The full picture of how vaults work lives in Concepts → Vaults.)

  1. Create the vault

    Click + New Vault, name it, and pick a type — Dev, Research, Social, Personal, Creative, Dream, or Custom.

    The New Vault dialog: name, type, and the provisional option

    Notice the provisional vault checkbox: a scratch space you can empty in one gesture, which stays out of default-scope answers, the Neural Map and the dream layer until you make it permanent. Perfect for experiments you're not sure you want to keep.

  2. Feed it a folder

    A vault stays empty until a folder feeds it. Right after creation, the OS offers to attach one: its files are read, cut into chronicles and vectorised right away — and again whenever they change.

    The “Feed it now?” dialog after creating a vault

    Later is a real option — you can attach the folder anytime from the vault's Sources.

  3. Its sources, at any time

    In the vault's Sources section you see the watched folders, add new ones (Add a folder to watch…), and force a Rescan if you want the vault to re-read everything now.

    The Sources section of a vault

    From here on, dropping a file into the watched folder is all it takes — the watcher ingests it. This is the same door web capture and every other entry route use.

  4. Tune how much it weighs

    Open the vault's settings and you'll find its dials:

    A vault's settings panel: attention, sources, spines

    • RAG attention — how much recall listens to this vault when you ask questions, from 100% down to Off. A hobby vault can whisper while your work vault speaks.
    • Spines — the nature of each memory (a note, a decision, a piece of source code…). The vault shows which spine types live in it, and can reclassify.
    • Sub-vaults — carve a vault into finer domains when it grows.
  5. Govern it

    The Governance section holds the two decisions that are always yours:

    The Governance section: protection level and deletion

    • Protection — Normal is ordinary memory, read in default-scope answers on any route. Maximum is for sensitive domains: kept out of ordinary answers (see Concepts → Vaults for exactly what it does and doesn't block).
    • Delete vault — permanent, and clearly labeled as such. The OS never deletes memory silently.

Vaults that apps create​

When a cartridge (an app) gets its own vault, it arrives walled off: excluded from Dream State consolidation, the Neural Map and federated recall — the app's data stays isolated until you validate it.

A walled-off app vault, waiting for your decision

Unlock permanence is your gesture, not the app's. You can also empty the vault in one click. No app writes itself into your permanent memory without you.