Field Note: AI-Ready Second Brain 3/8: Mapping the Sources

Chris Bernier

13h • Ops & Debugging

In Part 2, I reorganized my Second Brain so the folder structure gave each kind of information a clearer home.

That solved one problem: where information lived.

It did not solve the next problem: How an AI agent, or even future me, should approach that information.

A folder name alone cannot answer questions like:

Where should I look first?
Am I looking at raw source material or knowledge I have already adopted?
Could this contain sensitive information?
Does using it require approval?
Might it be out of date?

That gap led me to create what I’m calling Source Manifest Lite.

It sounds more technical than it is.

Source Manifest Lite is a small routing map for the major source areas in my Second Brain. It is not an inventory of every note, file, or document. I don’t want another system that becomes too heavy to maintain.

Instead, each source area gets a short description covering what it contains, what it is meant to be used for, its general sensitivity, any approval boundaries, the canonical place to start, and where supporting material can be found.

The distinction between a canonical starting point and supporting material has been especially useful.

I may have several raw captures about a subject, but only one current operating note that reflects what I have actually decided to use.

The raw material still matters. It provides evidence, history, and context. But it should not automatically outrank the operating note.

The same principle applies elsewhere:

Public research is not handled the same way as a sensitive source.
A recommendation is not the same thing as an approved action.
A historical note is not automatically a statement of current practice.

Without a routing layer, those differences can be easy to miss, especially when an agent retrieves a passage that appears relevant but lacks the context needed to use it properly.

Source Manifest Lite gives the agent a better starting point. It can indicate where to begin, what kind of material it is entering, and where it should slow down or ask for approval.

But this map does not guarantee that a source is true or fresh. It does not create security by itself. It does not guarantee that the correct note will be retrieved.

It is routing guidance, not proof.

The key for me is keeping it lightweight.

If maintaining the manifest becomes a second knowledge-management job, I probably won’t keep it current. So I’m focusing on major source categories and meaningful boundaries rather than documenting every possible detail.

My working test is simple: Can this map quickly answer where to look first, whether the material is raw or operating knowledge, whether it is sensitive, whether approval is required, and whether it could be stale?

The folder structure from Part 2 gave my information a structural layout. Source Manifest Lite adds a basic navigation layer on top of it.

The next problem is knowing what entered the system, whether it was processed properly, and what still needs review.

That is Part 4: Ingestion receipts and the source review queue.

If you use a Second Brain with AI, what would help more right now: a clearer folder structure or a better map of where to look first?

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

0 comments

Field Note: AI-Ready Second Brain 3/8: Mapping the Sources