Folders and naming

A few folders, two or three levels, and note titles you'd search for — structure that humans and AI can both navigate.

The single most useful thing to know: AI searches your workspace the way a human would. It lists folders, reads names, and follows the ones that look right. Structure that a colleague could navigate is structure your AI can navigate. Structure that needs tribal knowledge fails both.

Keep the top level small

Most people need a handful of top-level folders:

/Inbox — notes you haven’t filed yet
/Work or /Customers — one folder per customer or account
/Projects — active workstreams
/Meetings — recurring internal meetings
/Research — references and ideas

Two or three levels is usually enough:

/Work/Acme/Discovery call
/Projects/Website launch/Decisions
/Meetings/Product sync/2026-07-01

Name notes the way you’d search for them

Good titles carry the account, the event, or the decision:

Acme — Discovery call
Website launch — Decisions
Product sync — 2026-07-01

Avoid Notes, Call, Draft, Untitled. Six months from now, neither you nor the assistant can do anything with those.

Don’t over-structure up front

Start with real work and let structure emerge. An /Inbox folder plus the habit of filing weekly beats a beautiful empty taxonomy. When a folder gets crowded, split it then — moving notes is drag-and-drop (editor basics), and an MCP-connected agent can do bulk reorganization for you (MCP recipes).

Teach the structure to your AI

Once a folder has conventions — what goes in it, how notes should be titled — write them into the folder’s instructions so every agent that touches it follows them. That’s the difference between an assistant that guesses and one that files things where you would.