Vault Structure

Organize your vault around your work, with as little setup as possible. Start by saving into capture/, then add folders, links, and metadata only when they make something easier to find or use.

MindWiki supplies a capture inbox. You choose the rest of your organization. A founder's project library, a researcher's source collection, and a writer's idea archive can use different structures while sharing the same readable Markdown foundation.

Start with the inbox

Every account has a user-facing capture/ folder for incoming notes. Email captures, web Quick Capture, and the agent capture tool use it as the default destination.

You do not have to organize an idea before saving it. A useful note in the inbox is better than a forgotten note waiting for the perfect category.

Grow folders from real content

When a few pages clearly belong together, give them a folder. These are optional patterns:

Folder	Useful contents
`projects/`	Briefs, plans, research, and progress for active work.
`sources/`	Notes about articles, books, papers, interviews, and other references.
`decisions/`	Decisions, alternatives, reasoning, and outcomes.
`people/`	Relationship context and notes about people.
`ideas/`	Questions, early concepts, and possibilities.
`research/`	Active investigations and developing explanations.
`reference/`	Stable material you expect to reuse.
`archive/`	Work you want to keep outside your active view.

These names are examples, not required folders. Use a smaller set if it serves your work better.

Build a small project home

Create a project folder and a hub page linking the useful material:

markdown

# Website Launch

## Brief
[[Website Launch Brief]]

## Research
[[Audience Interviews]]
[[Homepage Examples]]

## Decisions
[[Homepage Messaging Decision]]

The folder groups the files. The hub explains how they fit together. An agent can read the hub before retrieving the detailed sources it needs.

Use tags across folders

A page can have one file location and several themes. Add tags to connect content without copying it into multiple folders:

yaml

---
title: Audience Interviews
type: research
tags: [website, onboarding, customer-research]
---

This note can stay in a research folder while remaining discoverable alongside related project and decision pages.

Choose clear names and titles

Use descriptive filenames, such as homepage-messaging-decision.md, and a readable title property when useful. MindWiki uses the title for display when present, otherwise the filename.

Avoid generic names repeated throughout the vault. “Website Launch Brief” is easier to distinguish than several pages titled “Notes.” Use autocomplete when linking so you select the intended page.

After moving or renaming a page, check important incoming links. Changing a file's name does not guarantee every handwritten reference will remain valid. Supported structural proposal operations can provide their own link-update behavior; see Proposals.

Know which folders serve the app

Folder	Purpose
`capture/`	Your incoming notes and captures.
`_assets/`	Attachments added through supported app workflows.
`_meta/`	App-managed metadata and supported agent-guide material.

Attachments and app-managed folders can appear as their related features are used. Keep asset references intact, and use the relevant settings or guide-management workflow for app-managed content.

Let agents follow your existing structure

Tell a connected agent where the relevant project lives and ask it to read before writing:

text

Read my Website Launch hub and its linked brief. Save a draft using the naming and folder conventions already present. Tell me the path you used.

A folder convention helps agents organize. It does not by itself restrict access; access is determined by the permissions MindWiki actually enforces.

Next: Capture Methods, Properties, and Wikilinks & Backlinks.