DEV Community: Second Brain Starter

AI Agent Memory Rots Silently — Audit Yours in One Command

Second Brain Starter — Mon, 24 Aug 2026 22:55:19 +0000

Last week I published Verified Memory Vault — a free Obsidian vault that gives Claude Code, Codex or Gemini CLI persistent memory through a plain CLAUDE.md boot file and an append-only MEMORY.md. It works. But after running it for a few weeks, something became obvious:

Memory systems don't fail loudly. They rot silently.

Nobody deletes your agent's brain in one dramatic afternoon. Instead:

A note gets renamed and three [[wikilinks]] die — nobody notices for weeks.
Someone (you, or the agent during a "cleanup") rewrites a memory line without its date. That line is now unauditable: you can no longer tell what the agent knew when it made that decision last Tuesday.
The inbox folder grows to 40 unsorted files because capturing is easy and sorting is work. The agent reads the junk into its context every session.
And then there is the dramatic version anyway: an over-eager cleanup command runs git rm over half of MEMORY.md, the commit goes through, and the knowledge is gone. This is not hypothetical — it is the documented way agent setups die.

A folder structure that can't detect any of this isn't a memory system. It's a landfill with good intentions.

Two scripts, zero dependencies

So the vault ships with two small Python tools. No pip install, no Node, no plugins — if you have Python 3, you're done.

1. `memory_check.py` — the honest report

python3 tools/memory_check.py

It scores the vault's health out of 100 across four dimensions:

Protocol violations — undated lines in MEMORY.md, missing daily notes for active days
Dead links — every [[wikilink]] gets resolved against actual filenames
Inbox pressure — how much uncaptured junk has piled up in 00_Inbox
Bloat — MEMORY.md growing without consolidation

The output is a score, a list of concrete problems with file names, and an exit code (0 healthy, 1 degraded). That exit code matters more than it sounds: you can wire the check into CI, a cron job, or the end of your agent's session loop, so the system audits itself instead of relying on you remembering to care.

Here's what a degraded run looks like:

memory_check: 80/100 (DEGRADED)
  [links]   DEAD: [[weekly-review]] -> no such note (referenced in 01_Daily/2026-08-21.md)
  [protocol] MEMORY.md line 14: entry without date prefix
exit code: 1

Eighty points sounds fine until you realize each deduction is a fact your agent will misremember or miss.

2. `memory_guard.py` — the seatbelt

If you keep the vault in git (you should), this becomes a pre-commit hook:

ln -s ../../tools/memory_guard.py .git/hooks/pre-commit

From then on, any commit that deletes a large share of MEMORY.md gets refused:

memory_guard: REFUSED
  MEMORY.md: 31 of 44 lines deleted (70%)
  Mass deletion of the memory file looks like an accident.
  If it really is intentional, split it into smaller commits
  with an explicit reason in the message.

The guard doesn't make deletion impossible — it makes it deliberate. Legitimate restructuring still works; you just can't lose six weeks of agent memory to one fat-fingered command anymore.

Why not just use a vector database?

You can, and for some workloads you should. But most agents' persistent memory needs are smaller than the industry pretends: dozens of durable facts, not millions. Plain Markdown wins at that scale because

it's auditable — the agent's memory is readable in ten minutes by a human,
it's diffable — every change to what your agent "believes" is in git history,
it's portable — no lock-in, no export problem, works with Claude Code, Codex, Gemini CLI or anything else that reads a boot file,

and now, with these two tools, it's checkable — which plain text normally isn't.

Get it

The vault is free, licensed CC BY 4.0 (use it commercially, attribution only), and sets up in about ten minutes: download, open as an Obsidian vault, point your agent at CLAUDE.md.

Download Verified Memory Vault v0.9 (ZIP)
Source and updates: github.com/secondbrainstarter/verified-memory-vault

If you want a starter system for your own notes rather than your agent's, the companion project Second Brain Starter uses the same philosophy — three folders, no plugin zoo, working in ten minutes.

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Your AI Coding Agent Forgets Everything — Fix It With a Free Obsidian Vault

Second Brain Starter — Mon, 24 Aug 2026 14:31:34 +0000

Every AI coding agent starts every session with amnesia. The repository is
there, the instructions are there — but the knowledge from yesterday's session
is gone: the workaround for that build error, your preference about naming,
the decision you made last week. So you explain it again. And again.

The fix is almost embarrassingly simple: give the agent a place to write
things down — and a way to check that the memory is actually healthy.
Claude Code already reads CLAUDE.md at the start of every session.
Verified Memory Vault is a deliberately small Obsidian vault that turns
that mechanism into persistent memory: three folders, one boot file, one
memory file — plus two dependency-free Python scripts that verify the
memory instead of assuming it. Set up in ten minutes, free, licensed CC BY 4.0.

What is inside:

00_Inbox — everything lands here first (capture, don't sort)
01_Daily — one note per session: what was done, decided, blocked
02_Templates — daily note templates, English and German
CLAUDE.md — the boot file every agent reads first: rules and memory protocol
MEMORY.md — the durable memory: append-only, dated, one line per fact
tools/memory_check.py — scores memory health on demand: protocol violations, dead links, bloat, inbox pressure. One command, honest report.
tools/memory_guard.py — an optional git pre-commit hook that refuses the commit that deletes your agent's brain (the documented way agent memories die)

The whole method is three rules:

Capture, don't sort. New notes land in the inbox; sorting happens in the daily note, not while capturing.
Every session leaves a daily note. So the next session resumes cold — without asking you where you left off.
Promote durable facts into MEMORY.md. If a fact will matter in a later session, it belongs there: dated, one line, never rewritten.

Why "self-checking" matters: folder structures rot silently. Memory gets bloated, links die, entries lose their dates — and nobody notices until the agent's context is full of junk. Run

python3 tools/memory_check.py

and you get a score, a list of concrete problems, and an exit code your CI or agent loop can act on. If you keep the vault in git (recommended), the guard hook blocks mass deletions of MEMORY.md before they happen.

Setup takes ten minutes. Install Obsidian (free), download the vault,
open the folder as a vault — daily notes and templates are already
preconfigured, no plugins to install. Claude Code reads CLAUDE.md
automatically; for other agents (Codex, Gemini CLI, …) point them at the file
or copy it to their boot file, e.g. AGENTS.md. At the end of a session:
fill the daily note, promote the durable facts, run the check once. That is
the whole habit.

And what it is not — honestly: not a plugin collection
(no community plugins, no vector database), not an autonomous system (it is a
structure with two small scripts, not a magic product), and not a
replacement for your code repository — it is memory about the work. That is
exactly why it keeps working: nothing to maintain, everything auditable in
ten minutes.

Why the license matters: many “AI vaults” in circulation are
non-commercial. This one is licensed CC BY 4.0 — free to use,
including in your own business; only attribution is required. If you already run
a note system for yourself, Second Brain Starter is the human-side companion: the same three-folder philosophy, built for people who want a working note system in ten minutes.

Download Verified Memory Vault v0.9 (ZIP)
Source and updates: github.com/secondbrainstarter/verified-memory-vault

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

What the Full Second Brain Starter Adds (and Why You Start With the Mini-Vault)

Second Brain Starter — Mon, 24 Aug 2026 07:28:39 +0000

The Mini-Vault
is deliberately small: three folders, six templates, three rules. That is not a
placeholder for something bigger — it is the first stage of a system, and the full
Second Brain Starter is the second stage. This post says exactly what the full
version adds, what stays the same, and why starting small is the point, not the
compromise.

What stays the same. The full version does not replace the rules — it
builds on them. Everything
lands in the inbox first, one
note, one idea, always
link. The files stay plain text
in folders you own. What changes is how much structure sits around those rules.

What the full version adds. Ten folders instead of three, fourteen
templates instead of six, and eight topic hubs — pages that bring projects, finances,
health and learning together in one place. The templates grow from three types to
meeting notes, goals, habits, books, decisions and more. Method guides (in English and
German) explain the approaches this blog covers in practice: PARA, Zettelkasten, the
daily routine — without jargon.

Why you start with the Mini-Vault. Structure only helps if the habits
are already there. A daily note you actually open beats ten folders you admire.
The first week builds the habit;
the full version is for the moment when the inbox, the daily note and a few links feel
natural. The most common reason note
systems die is starting with too much — so the full version is designed to be the
second step, not the first.

Honest status. The full version is being built and is not finished
yet — there is no release date to promise here. The Mini-Vault stays free either way.
When the full version ships, you get one message, nothing else. That is the whole
newsletter: one-time updates, no spam.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Your First Week With a Second Brain: A Day-by-Day Plan

Second Brain Starter — Mon, 24 Aug 2026 07:26:26 +0000

The Mini-Vault
takes ten minutes to set up — but a system is not built in ten minutes, it is built in
the first seven days. Most people quit in that week, not because the system is too
complicated, but because they want everything at once. This plan is the opposite: one
small thing per day, taken from the actual steps of the instructions, with no
reorganization marathon.

Day 1: Set up and read the three rules. Install Obsidian, open the
vault, done — that takes less than ten minutes. What takes longer (and matters more):
actually read the three rules instead of skimming them. “Capture, don’t sort.”
Everything lands in the inbox first — idea, task or thought. “One note, one idea.”
Write in your own words what you mean. “Always link.” Every note links at least one
other note. Then create your first two notes: the
daily note
with today’s date and a project note for whatever is pressing on you most right now.
Nothing more is needed on day one.

Days 2 and 3: Start the 17-minute routine. From now on, the
routine
from the instructions applies: seven minutes in the morning (create the daily note, write
down three goals, look at yesterday’s inbox), ten minutes in the evening (process the
inbox, close the daily note). The important thing on these days: when something crosses
your mind, it goes into the inbox — not into the right folder, not into a new note. The
inbox
rule is the one place where you never have to decide.

Days 4 and 5: Learn to process the inbox. The actual trick happens
while processing in the evening: one note per idea, in your own words,
linked to
at least one other note. Anything holding more than one idea gets split —
one note, one
idea is the rule that keeps your system findable. For one idea that really matters to
you, create your first permanent note; the
templates
tell you which note is for what. If something is just a thought for later, one line in
the daily note is enough — not everything needs its own note.

Day 6: Review the first week. Look at what is left in the inbox and
which notes you can actually find again. That is the simplest form of a
weekly review:
no more than five minutes, honestly answering what works and what feels hard. If the
inbox is full, it is almost always because you are keeping too much — that is not a
system failure, it is a filter problem.

Day 7: Stay small on purpose. The most common reason
note systems
fail is the urge to optimize everything in week one: more folders, more templates,
more plugins. The Mini-Vault has three folders and six templates — and that is exactly
the point. Everything your system needed this week was an inbox, a daily note and a few
notes. If you can say that after seven days, you did not set up a note system, you built
a habit.

After that. The first week is the hardest part because it is new —
from the second week on it gets boring, and boring is the goal. The vault stays
plain text in files you
own, and the full version (10 folders, 14 templates, 8 topic hubs) is the next step
once the basics are in place. But the basics are these seven days, not the tool.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

One Note, One Idea: Why Atomic Notes Keep a Second Brain Alive

Second Brain Starter — Mon, 24 Aug 2026 07:24:45 +0000

Rule two of the Mini-Vault is the one people skip. “One note, one idea. Write in
your own words what you mean — not what somebody else wrote.” It sounds like
common sense, so it gets filed under “nice to have” and forgotten. But it is the rule
that decides whether a note system grows into a second brain or quietly rots into a
bigger, messier version of the internet.

A note is a unit of thought, not a container. The moment a note
holds three ideas, it stops being findable. You cannot link to “the idea” — it is
buried inside “Notes on chapters 3–5” next to two unrelated thoughts. Retrieval is
the first casualty: your system should remind
you of your ideas, but a bloated note reminds you of nothing because it looks like
everything. Linking is the second casualty: links
only work when they point at one thing. This is one of the
reasons note
systems fail: the notes get diluted until the network they were supposed to form
never forms.

Copy-paste is the trap. Most people break the rule because storing
somebody else's words is easier than writing your own. A highlight is not a thought —
it is a souvenir. Writing in your own words forces you to find out what you actually
understood, which is exactly why closing
the file and reconstructing the idea beats re-reading it. Distillation
turns notes into
thinking; the atomic note is the unit that process produces. One idea, one note,
your words — that is the whole job.

The test is one sentence. If you cannot say what a note is about
in a single sentence, it is not one note — split it. The
inbox
rule delivers the raw material; the evening part of the
17-minute
routine is where the splitting happens: one note per idea, link, file away. The
daily note with a date in its filename keeps the stream chronological; the atomic
notes keep each idea reachable.

The vault makes the rule concrete. The
six templates each
hold one kind of thing: the daily note holds the day, the project note holds one
project with a goal, a success criterion and a next step, the permanent note holds
one idea. You never have to decide “which of my five thoughts does this note
contain” — the structure already decided. That is why the
note
types stay small and why the whole system stays
plain text: small units
of your own words, in files you own.

Try it for one week. Download the free Mini-Vault, and every
evening while you process the inbox, split anything that holds more than one idea.
The effect is immediate: smaller notes, easier linking, and a system that actually
comes back to you when you need it — because each note now points at exactly one
thing you once thought.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Why Your Second Brain Should Be Plain Text

Second Brain Starter — Mon, 24 Aug 2026 07:15:44 +0000

Your notes are the one thing you want to keep for decades. The ideas you capture
today should still open in ten years, on whatever device you own then, without an
export ritual and without a subscription. That is the strongest argument for keeping
a second brain in plain text: plain Markdown files do not depend on any tool's
goodwill. They are just files. A file you can open with a text editor is a file you
will never be locked out of.

The Second Brain Starter Mini-Vault is built exactly this way. Everything inside
it — the daily notes, the project notes, the permanent notes, the templates — is a
normal .md file in a normal folder. There is no proprietary database, no
hidden format, no cloud account that owns your words. If Obsidian disappeared
tomorrow, your notes would still be there, readable by any editor on any system.
That is not a feature; it is the baseline a note system should start from.

Lock-in is a slow failure. The interesting failure mode is not
that a tool stops working — it is that switching becomes so expensive that you stay
with a tool that no longer fits. Exporting a thousand notes from a proprietary
format, fixing the broken links, losing the structure on the way — that cost is
exactly how a system dies. Plain text removes the cost. Moving to another app means
pointing it at the same folder. That is one of the
reasons note
systems fail: they get attached to a tool instead of to the content.

Files you can copy are files you can back up. A second brain
holds months of thinking. Losing it because a laptop died is not a technical problem,
it is a planning problem — and plain text makes the planning trivial. Your whole
vault is a folder; backing it up is copying the folder. The Mini-Vault ships as a
small ZIP for exactly that reason: the entire system is small enough to carry in one
file, and the same ZIP is what you download. Copy it to a USB stick, a second drive,
or a cloud folder, and your notes exist in two places. The
weekly
review is the natural moment to check that the copy is current.

No plugins is a feature, not a limitation. The vault runs on
core Obsidian with no community plugins and no setup ritual — the three folders, the
templates, and the routine are the whole system. Fewer moving parts means fewer
things that can break, and it means your notes never depend on a plugin that stops
being maintained. Plain text is the same idea one level down: the format itself is
the boring, stable foundation. The
inbox rule
keeps the structure simple; plain text keeps the files safe.

What this means in practice. You do not need a backup app, a
sync service, or a special workflow. You need three habits: keep the vault in one
folder, copy that folder somewhere else on a regular basis, and never let a tool
tell you your notes live somewhere you cannot reach. The daily note with a date in
its filename, the three templates, the
17-minute
routine — all of it works the same in twenty years, because all of it is plain
text.

If you want to see how small a plain-text second brain can be, the free
Mini-Vault is
exactly that: three folders, six templates, plain Markdown, no plugins. Unzip it,
open the folder in Obsidian, and the whole system is yours — as files you own.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

The 6 Templates That Keep a Second Brain Simple

Second Brain Starter — Sun, 09 Aug 2026 06:25:38 +0000

Every template is a decision you made in advance. The daily note does not ask you
what to write — it asks three questions. The project note does not ask you to invent
a structure — it asks for a goal and a success criterion. That is the whole job of a
template: to move the thinking from “how do I structure this?” to the actual content.
But templates can also become the problem, when you collect forty of them and spend
your evenings choosing. The fix is a small, boring set that covers the three moments
your system actually has.

The Second Brain Starter vault ships exactly six templates — three in English, three
in German — because the method needs three note types, not twelve. Here is what each
one is for, and why the set is complete with just these.

The Daily Note — one per day. Three goals, a focus line, a short
journal, and an inbox section for the thoughts that arrive during the day. The daily
note is where the
17-minute routine
happens: seven minutes in the morning to set the three goals, ten minutes in the
evening to close the day. The date lives in the filename, because
a date in the filename
keeps the daily stream chronological without any extra setup. You never decide
“what belongs in a day” — you just open today's note.

The Project Note — for everything with an end. A project is
anything that has a goal and a finish line: a website relaunch, a course, a move. The
template asks for the outcome in one sentence, an objective success criterion, and the
smallest meaningful next step. That is the difference between a project and a
permanent note:
the project note is about the work and its deadline, the permanent note is about the
idea that stays. Projects end, so their notes carry status and completion — the rest
of your system does not need those fields.

The Permanent Note — one idea, your own words. This is the
Zettelkasten engine. One note holds exactly one idea, written so you still understand
it in six months, with at least one link to something you already know. The template
enforces the checklist: one idea, own words, a link, a title that says what it is
about. It is deliberately the strictest template, because
links are what turn a collection into a brain.
If a note cannot pass the checklist, it is either two notes or a quote without a
thought.

Why six and not twenty? The three types map to the three moments
of the method: capture (daily note), work (project note), understanding (permanent
note). Everything else — meetings, books, goals, habits — is either a project, a
thought, or an item on today's note. Adding a template for every special case is how
a system gains weight, and
added weight is the most common way a second brain dies.
A template you do not use is not a feature; it is a decision you made that you now
have to ignore.

Two languages, same structure. The vault ships the same three
templates in German (Tagesnote, Projektnote, Permanentnote) with the same fields,
so switching languages never changes the method. That is a small detail that matters
more than it looks: the structure of your notes should not depend on the language you
happen to think in on a given day.

How to use them without plugins. Open a template, copy the content,
create a new note, paste, replace the placeholders. With Obsidian's built-in Templates
core plugin it is one step less: set the folder once, then insert the template and the
date replaces itself. No community plugins, no setup ritual — the whole vault runs on
core Obsidian, which is the point. The
inbox rule
and the templates work together: capture into the inbox during the day, then let the
evening routine decide which template each captured thought turns into.

If you want to see the six templates in a working vault, the free
Mini-Vault is set up
exactly like this — three folders, six templates, a daily note with the date in its
filename, and an inbox small enough to empty in one sitting. It is running in about
ten minutes.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Why Second Brains Fail: 5 Mistakes That Kill a Note System

Second Brain Starter — Sun, 09 Aug 2026 06:25:09 +0000

Every second brain starts the same way: a clean vault, three folders, big plans. And
most of them end the same way too — a graveyard of orphan notes that nobody opens.
The system did not fail. Five specific mistakes killed it, and each one is easy to
recognize before it does the damage.

Mistake 1: Collecting without processing. You capture everything —
articles, quotes, ideas — and the inbox grows into an archive. Capture without
processing is not a system, it is a pile with good intentions. The
inbox rule
only works when the inbox gets emptied, and emptying happens on a schedule, not on
inspiration. A note that sits in the inbox for three weeks was never captured; it was
postponed.

Mistake 2: Organizing instead of linking. Folders, subfolders,
tag taxonomies, color-coded everything. Organizing feels like progress, but a folder
tree does not connect ideas — it separates them. The second brain becomes a network
through links, not through placement, which is why
always linking
is the rule that turns a collection into something that thinks with you. If your vault
is tidy but nothing links to anything, you built a museum, not a brain.

Mistake 3: Storing other people's words. Highlights, clippings,
copy-paste paragraphs. The note exists, the thought does not. A
permanent note
is written in your own words, because writing is where understanding happens. Stored
quotes are a library; rewritten notes are a mind. If you cannot summarize what you
saved, you did not save a thought — you saved a file.

Mistake 4: Never closing the loop. Notes go in, nothing comes out.
No review, no retrieval, no reuse — the vault becomes a one-way street. The loop closes
in the weekly review,
and it is tested the moment you
close the file
and try to reconstruct the idea. A second brain that is never asked anything degrades
into a backup drive.

Mistake 5: Perfecting the system instead of using it. Plugin
shopping, template tinkering, another method migration every month. The system becomes
the hobby and the notes become the paperwork. If your vault needs a ritual to be
understood, it is a cabinet with a ceremony — distillation
is the layer on top of a
small system, not a substitute for one. Boring and used beats clever and abandoned,
every time.

The fix is boring on purpose. Three folders, three rules, and
seventeen minutes a day. Capture into the inbox, process in the evening, link every
note, review once a week, rewrite what matters. That is the whole method — no plugin
hierarchy, no tag architecture, no perfectionism. The mistakes above all come from
adding weight; the fix is removing it.

Want to see the boring version in practice? The free
Mini-Vault is built
exactly for this — 3 folders, 3 rules, 6 templates (English and German), a daily
note with the date in its filename, and an inbox that is small enough to empty in
one sitting. It is up and running in about ten minutes.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Distill, Don't File: How Notes Become Thinking

Second Brain Starter — Sun, 09 Aug 2026 06:24:39 +0000

You capture, you organize, you link — and the vault keeps growing. Growth is not the
goal. A vault that only grows is a warehouse; a second brain has to produce thinking,
and thinking does not happen in the filing step. The step that turns notes into
thinking is distillation: rewriting the core of a note in your own words, smaller
every time.

Filing is not understanding. You can file a quote you do not
understand, and you can link two notes without having understood either one.
Organization makes notes findable; it does not make them yours. A note stays a file
until you have rewritten it — that is the difference between storing an idea and
owning it.

Distillation is compressing toward understanding. Not summarizing
for its own sake. You read the note, close it, and write the core in one or two
sentences of your own — not the author's words, not your first draft, but the
compressed version that fits your thinking. If you cannot write it, the note is not
too long; it is too vague, and the fix is the note, not your patience.

Distillation is the step after retrieval. Closing the file tells
you what you can actually recall; distillation is what you do with what you recalled.
Recall without rewrite evaporates again, and rewrite without recall is copying. The
two habits belong together: pull the idea out of your head first — the
test of closing the file —
then compress it.

Habit 1: one sentence, at the top. Every note that matters gets a
visible one-sentence takeaway in its first line — plain text, no plugin. If you cannot
write the takeaway, you have not understood the note; rework the note until you can.
Thirty seconds of writing beats thirty minutes of reorganizing.

Habit 2: the review distills. In the
weekly review,
do not just check that the notes exist. Pick the three strongest of the week and
rewrite each in two or three of your own sentences. Not more. Three per week is more
than a hundred and fifty distillations per year — that is the difference between a
vault that grows and a mind that grows with it.

Habit 3: the link text is distillation. When you link two notes,
write the phrase that says why they belong together — the anchor text is a compressed
thought. That is what
always linking
is really for: every link carries a small decision, and every decision is thinking.

What this is not. No color hierarchy, no progressive-summarization
plugin, no markdown gymnastics. Highlighting is not distilling — highlighting is
selection, and selection is the easy half. Plain text and one honest sentence beat any
system of nested tags. If your vault needs a ritual to be understood, it is not a
second brain; it is a cabinet with a ceremony.

Structure first, distillation second. Compression only works on a
clean vault. A bloated collection with hundreds of orphan notes does not get better by
being summarized harder — it gets better by being emptied, and the
inbox rule
is where emptying starts. Distillation is the layer on top of a small system, not a
substitute for one.

Want to try it right away? The free
Mini-Vault is built
exactly for this — 3 folders, 3 rules, 6 templates (English and German), a daily
note with the date in its filename, and an inbox that is small enough to empty in
one sitting. It is up and running in about ten minutes.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Close the File: Why Reconstructing Your Notes Beats Re-Reading Them

Second Brain Starter — Sun, 09 Aug 2026 06:24:03 +0000

You close the note and it is gone — not from the vault, from your head. A minute ago you
were reading it, nodding, thinking yes, this is exactly it. Now you could not
reconstruct a single sentence. That gap is not a memory problem. It is a design problem:
re-reading was never the point of a note system.

Recognition feels like understanding, but it is not. When the note is
open in front of you, your brain takes the cheap path: it recognizes the words instead of
recalling them. Recognition is fluent, pleasant and completely free of effort — which is
exactly why it does not stick. You walk away feeling like you know the material, and the
next day the note might as well be blank. (Why that feeling fools us is covered in the
article on the weekly review:
review is retrieval under real conditions, not a re-read.)

The honest test is closing the file. Not skimming, not highlighting, not
nodding. Close the file and reconstruct the idea without looking. If you cannot, the note is
not in your head — it is only in your vault. A note you never pull back up is as good as
unwritten, and the same test applies to code, to systems, to everything a second brain is
supposed to carry for you.

Reconstruction is the skill your system should train. The difference
between reading and reconstructing is the difference between recognition and recall. Recall
is harder, slower and feels worse — and it is the only thing that actually changes what you
can do. Every time you reconstruct an idea from memory, you rebuild the connections around
it. The vault stores the raw material; the reconstruction is what turns it into thinking.

Habit 1: Write, then close. When you finish a note, close the file and
write two or three sentences from memory: the core claim, the one example, the one thing you
want to remember. If you cannot, the note is too long or too vague — compress it until you
can. Thirty seconds of this turns every note into a small retrieval practice.

Habit 2: Make the review a retrieval event. In the
weekly review,
do not open a note and skim it. Read the title, then reconstruct the point before you open
the file. What you remember tells you what the note is actually doing for you; what you
miss tells you what needs a link or a rewrite.

Habit 3: Let links be triggers, not decorations. A link only works when
you follow it. When you follow a link into an old note, pause before reading: what did I put
here, and why did I link it to this? That pause is a free retrieval practice, and it is the
difference between a collection and a network — more on that in the article about
always linking.

What this is not. This is not a call to turn your vault into a quiz.
No flashcards, no spaced-repetition plugin, no daily drilling. Retrieval practice works
precisely because it is a side effect of real work: closing the file, following a link,
explaining a note. If it becomes a chore, it stops being retrieval and starts being
recognition again — you will be reading your own quiz questions.

Structure first, retrieval second. Reconstruction only works if the
note is worth reconstructing. A bloated vault with three hundred orphan notes does not get
better by being re-read harder — it gets better by being emptied, linked and compressed
(the inbox rule
is the starting point). Retrieval practice is the layer on top of a clean system, not a
substitute for one.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

The Weekly Review: Why Your Second Brain Needs Maintenance, Not Just Input

Second Brain Starter — Wed, 05 Aug 2026 08:40:17 +0000

Note systems rarely die while you are collecting. They die a few weeks later, when
the inbox has grown fat, the daily notes have piled up, and you quietly stop
trusting the whole thing. The problem is not that you did not capture enough. The
problem is that capture has no maintenance rhythm. This article is about the
one appointment that fixes that: the weekly review.

Red means maintenance, not storage. When your inbox is full, the
obvious diagnosis sounds like this: “I need a better system.” In almost every case
that is wrong. The storage is not the bottleneck — the emptying rhythm is. A full
inbox is a queue that nobody is serving, not a container that overflowed. Adding
folders, tags or a second app does not serve the queue; it just gives the queue
more places to hide. (Why three folders are enough in the first place is covered in
the article on the inbox rule.)

The weekly review is a filter, not a cleanup. You do not review
to make your vault beautiful. You review to make a decision about everything that
arrived this week. Thirty minutes, once a week, three steps — that is the whole
method.

Step 1: Empty the inbox. Go through every item and decide: does
it become a note, a task, or does it go away? Nothing stays in the inbox overnight —
that is the daily rule from the 17-minute routine.
The weekly review is the safety net for everything the daily routine missed:
the half-finished thought from Tuesday, the link you saved “for later”, the idea
you scribbled in a meeting. Empty means empty — not sorted, not organized, empty.

Step 2: Look back. Open the daily notes of the last seven days
(a date in the filename makes this a one-second operation — see the article on the
daily note).
Skim them, not read them. Ask two questions: What stayed open? What became more
important than I thought? Take the two or three things that matter and give them a
permanent note with one link each. That is how a week of small entries turns into a
handful of notes that actually carry your work.

Step 3: Look ahead. Pick one to three notes that should carry
next week: a project focus, a recurring appointment you keep forgetting, an idea you
want to let ripen. Put them somewhere the daily note will see them. Next week, when
you open your daily note in the morning, the review has already decided what you
should be paying attention to — you do not have to re-decide it every day.

Why a fixed appointment beats motivation. The review works
because it is boring and scheduled, not because it is exciting. Pick a time that
does not compete with anything: Friday afternoon, 30 minutes, timer on. If a week is
chaotic, do a ten-minute version instead of skipping it — a short review keeps the
rhythm alive, and the rhythm is the system. The moment you start skipping “just this
once”, the inbox grows again, trust drops again, and the vault quietly dies again.

Maintenance is not perfectionism. You do not have to reorganize,
retag or archive anything in the review. If a note is not findable, the fix is a
link, not a folder move. If you are not sure, the answer is a decision, not another
reading. Thirty minutes of decisions keep a second brain alive for years; thirty
minutes of tidying keep it pretty for a week.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Want the full template set (EN, with the 17-minute routine, inbox & project templates)? Join the waitlist: secondbrainstarter.github.io — free, no spam, updates only.

Zettelkasten vs. PARA vs. Minimal: Which Obsidian System Is Right for You?

Second Brain Starter — Tue, 04 Aug 2026 08:40:51 +0000

Search for “Obsidian system” and you quickly drown in advice: Zettelkasten
purists, PARA devotees, template packs with forty folders. Most of that advice
is not wrong — it is just written for someone else. The honest question is not
“which method is best?” but “which method fits how you actually think
and work?” Here is a plain-language comparison of the three systems
you will meet most often, and where the Minimal approach of this site fits in.

Zettelkasten — for thinkers who build on their own ideas.
Invented by sociologist Niklas Luhmann, the Zettelkasten is a slip-box of
atomic notes that are linked into a web of thought. Its strength: ideas
accumulate and connect over years, and surprising links emerge that you never
planned. Its cost: it demands a writing habit and real intellectual patience —
a Zettelkasten is useless after a week, and only pays off after months of
consistent work. If you research, write, or think for a living, it is
unmatched. If you just want to stop losing tasks and notes, it is overkill.

PARA — for doers who organise by action. Tiago Forte's
system sorts everything into four buckets: Projects (active, with a
goal and deadline), Areas (ongoing responsibilities), Resources
(topics of interest), Archives (everything inactive). Its strength:
files live where the action is, and the four-way decision is quick to learn.
Its cost: you must keep moving things between buckets, and “areas” can become
a dumping ground if you are not disciplined. PARA suits people who think in
projects and need their notes close to their to-do list.

Minimal (what this site builds) — for everyone who has failed at a
system before. The Mini-Vault starts from a different observation:
most systems do not fail because they are wrong, they fail because they are
too heavy for daily life. So the Minimal approach keeps three rules only —
one
inbox, three folders, every
note links at least one other note, and
a
17-minute daily rhythm. It borrows the linking idea from Zettelkasten and
the “less structure, more action” idea from PARA, then cuts everything that
needs maintenance. You can start it in ten minutes — and the system is
designed to survive a busy week, not a perfect one.

How to choose honestly. If you write or research
professionally and can invest months, learn Zettelkasten properly — start
with one atomic note per day and let the network grow. If you live in
projects and deadlines, PARA will feel natural — just decide on the first
day which folder gets the note, and keep the rule. If you have tried both
and quietly given up (or you simply want a system that costs seventeen
minutes a day), start Minimal: it leaves the door open to both methods
later, because the two habits it builds — linking and daily review — are the
foundation that Zettelkasten and PARA both rely on.

Want to try the Minimal approach right away? The free
Mini-Vault comes
with the three rules built in as ready-made templates — inbox, daily note,
project note, permanent note — bilingual, and running in about ten minutes.
No forty folders, no setup weekend.

Question, feedback or an idea? Write to
geld.hamster@gmx.net — every
mail is read.

Download the free Mini-Vault (ZIP)

See it in action: Live preview

Question, feedback or an idea? Write to geld.hamster@gmx.net — every mail is read.

Want the full template set (EN, with the 17-minute routine, inbox & project templates)? Join the waitlist: secondbrainstarter.github.io — free, no spam, updates only.

DEV Community: Second Brain Starter

AI Agent Memory Rots Silently — Audit Yours in One Command

Two scripts, zero dependencies

1. memory_check.py — the honest report

2. memory_guard.py — the seatbelt

Why not just use a vector database?

Get it

Your AI Coding Agent Forgets Everything — Fix It With a Free Obsidian Vault

What the Full Second Brain Starter Adds (and Why You Start With the Mini-Vault)

Your First Week With a Second Brain: A Day-by-Day Plan

One Note, One Idea: Why Atomic Notes Keep a Second Brain Alive

Why Your Second Brain Should Be Plain Text

The 6 Templates That Keep a Second Brain Simple

Why Second Brains Fail: 5 Mistakes That Kill a Note System

Distill, Don't File: How Notes Become Thinking

Close the File: Why Reconstructing Your Notes Beats Re-Reading Them

The Weekly Review: Why Your Second Brain Needs Maintenance, Not Just Input

Zettelkasten vs. PARA vs. Minimal: Which Obsidian System Is Right for You?

1. `memory_check.py` — the honest report

2. `memory_guard.py` — the seatbelt