Field Note: AI-Ready Second Brain 4/8: Capturing and Reviewing Sources

Chris Bernier

8h • Ops & Debugging

In Part 3, I mapped the kinds of sources that can feed a Second Brain.

That raised the next practical problem:

How do I know what entered the system, what happened to it, and what still needs my attention?

I’m working with two lightweight tools for this: a Second Brain Ingestion Log Lite and a Source Review Queue Lite.

They sound similar, but they serve different purposes.

The ingestion log is the receipt.

It records meaningful captures and maintenance events, not every typo, wording change, or small edit. The goal is to preserve enough state to understand what happened and resume safely if the work stops halfway through.

A useful log entry might answer:

What kind of source entered?
What action was taken?
Where did the resulting material go?
Is the work complete, partial, or blocked?
Where should I resume?

This matters because a successful capture can still leave unfinished work.

A source may have been saved but not synthesized. A note may have been updated while related material still needs checking. A maintenance pass may have started without reaching a safe conclusion.

The log helps me avoid relying on memory to reconstruct that state later.

The Source Review Queue Lite is different.

It is not primarily about recording activity. It is a decision lane for captured material that may still require judgment.

An item might need to be:

synthesized with related material;
merged into a canonical note;
adopted into the working knowledge base;
retained for reference only;
held for approval;
or intentionally ignored.

That last option matters.

An AI-ready Second Brain should not create an obligation to process everything. Some material will not be useful enough to justify more attention. The queue makes that an intentional decision rather than an accidental omission.

The relationship between the two tools is simple:

The log answers:

What entered? What happened? Where do I resume?

The queue answers:

What deserves judgment? What should happen next?

I’m also preserving some important distinctions:

Captured does not mean reviewed.

Reviewed does not mean adopted.

Logged does not mean approved.

Neither tool decides whether a source is valuable, accurate, trustworthy, ready for adoption, or approved for use.

They make the state visible and help organize the evidence for review. The judgment about value, truth, trust, adoption, and approval stays with me.

For me, that is the practical value.

The system does not need to remember everything perfectly or decide everything automatically. It needs to leave enough evidence that I can see what happened, identify what remains unresolved, and continue without guessing.

The next field note will look at Canonical Confidence Labels: a simple way to communicate what status a note currently carries.

Do you currently have a simple way to tell the difference between something that was captured and something you have actually reviewed?

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

0 comments

Field Note: AI-Ready Second Brain 4/8: Capturing and Reviewing Sources