Home

The second brain

1. 01File-based memory: basic structure and disciplines7 min

   Claude Code's memory lives in a folder of markdown files, one fact per file classified by a type field with four values, and a note that carries a single idea linked to at least one other stays findable within seconds rather than after a full reread.

2. 02Obsidian: wikilinks, content maps and memory types8 min

   A wikilink is a native Obsidian feature that connects one note to another without depending on the folder each sits in. The content map is only a practice, a note that gathers links. Many people reuse Claude Code's memory type vocabulary in their own Obsidian vault, but they are two separate tools.

3. 03Querying a graph rather than rereading everything9 min

   A knowledge graph built once answers a question by walking explicit links, which costs noticeably fewer tokens than a full reread of the source files, a gap illustrated by a public example that carries its own caveat, and the same principle applies to an old session transcript, queried by levels before being reopened in full.

4. 04Dream and continuous learning: nightly consolidation7 min

   A nightly memory consolidation is a personal automation built on top of a scheduled task, not a native Claude feature: it digests notes in four phases, orientation, collection, consolidation through merging and archiving, verification, and only a task that runs on the machine or in an open session can read a folder of notes stored locally.

5. 05A perishable figure in an always loaded file7 min

   A figure that sleeps in an always loaded file reads like today's figure, even though it may have become false. If nobody would receive an alert the day it changes, it belongs in a dated register, opened only when the question arises, and the loaded file cites the principle or points to the register.

6. 06A shared vault has no concurrent editing6 min

   A local file notes application locks nothing on a shared network drive: a public report documents a settings folder that gets overwritten between users on this kind of mount, and the same mechanism makes plausible, without the source itself documenting it, the silent loss of a note edit.

7. 07The assistant's journal mostly talks about the assistant8 min

   A review of a large memory corpus kept by an agent shows that most entries document the agent's own mistakes, written by it, about itself, with almost no explicit instruction from the person it is supposedly profiling: it is like judging a pilot by the aircraft's maintenance log.