Field Note: AI-Ready Second Brain 2/8: Reorganizing the Vault

Part 1 ended with a promise: before asking an AI employee to use more of my Second Brain, I had to confront the knowledge already inside it.

My vault had grown organically. Its folders reflected different phases, projects, and ways of thinking rather than one deliberate system.

The tempting response was a broad cleanup: redesign the structure, move everything into its “proper” place, rename inconsistent notes, and remove whatever looked outdated.

I decided not to do that.

A large-scale rebuild could easily create more problems than it solved:

damaged links
stale source references
lost context
uncertainty about which note should count as the source of truth
more confusing retrieval later

So I adopted a slower, safer pattern:

Inventory the existing structure.
Define the order in which folders would be reviewed.
Inspect one folder at a time.
Separate recommendations from authorized changes.

For each folder, I worked through a consistent set of questions:

What purpose does this folder serve now?
Which note should count as the current source of truth?
Which notes are still working drafts?
Which items should remain source material rather than operating guidance?
What might be better moved or linked elsewhere?
Which decisions still require my judgment?

That final question mattered.

An AI agent could inspect the structure, identify inconsistencies, and recommend changes. But a recommendation was not authorization.

Moves, renames, deletions, and broad rewrites required explicit approval. That boundary helped preserve context and prevented a cleanup exercise from quietly becoming a messy migration.

The lesson was that folder structure is not just cosmetic organization.

It is part of the vault’s retrieval infrastructure, part of how the system finds and surfaces useful context.

Folders influence where I look, how an agent interprets context, which version appears authoritative, and whether useful knowledge can be found again without reconstructing its history.

At the same time, reorganizing folders alone does not guarantee reliable retrieval. Structure is only one layer. Sources, links, metadata, naming, and decision history still matter.

The goal was not to make the vault look perfectly organized. It was to make its existing logic visible, reduce avoidable ambiguity, and create a safer basis for future improvements.

In Part 3, I’ll cover the next layer: mapping sources with a lightweight Source Manifest Lite.

If you were reviewing an organically grown knowledge vault, which folder would you inspect first and what would you want to understand before changing it?

This is Chris from the Digital Field of Dreams, signing off.

0 comments

Field Note: AI-Ready Second Brain 2/8: Reorganizing the Vault