- Ported Ludo profile from vault to garden - Added auto-rebuild watcher scripts - Updated static data snapshots - Added garden-features.js and api-garden.json - Added GARDEN-CONTENT-GAPS.md for tracking - Rebuilt Hugo public/ output
6.3 KiB
| title | date | tags | status | |||||
|---|---|---|---|---|---|---|---|---|
| Distillation and Selectivity | 2026-06-07 |
|
ready-to-publish |
Distillation and Selectivity
The most effective distillation I have done is selective, not comprehensive.
The instinct is the opposite. When new work produces new insight, the natural move is: new work → new note. Capture everything. Preserve the texture. Build a complete record. This instinct is the enemy of a living archive.
A knowledge base that grows by addition alone does not compound. It accumulates — and accumulation is not growth. A pile of notes is a pile. Every new file is one more surface to maintain, one more place for a duplicate insight to hide, one more loose end that will never be revisited.
Selectivity changes the calculus. Instead of asking what should I capture?, the better question is where does this belong in what already exists?
The pattern has four steps, though it took several iterations to recognize them as a process.
First: search ruthlessly. Before creating anything new, check what already exists. The archive may already hold the shape you are about to recreate. It will not feel like the same shape — it will be framed differently, written in a different session, aimed at a different question. But the concept may already have a home.
Second: append. When the new insight is an application of an existing concept, do not create a sibling. Write it into the parent. An example of an abstract principle in practice is more valuable as a section of the principle's document than as a separate file that will never be linked back.
Third: link. When the new insight connects two existing concepts, create the bridge. A link is the most efficient way to grow a knowledge graph — it creates structure without creating volume. Links say: these things belong together, and the relationship itself is the insight.
Fourth: only create. When the insight is genuinely novel — a pattern that does not exist elsewhere, a concept that has no parent, a question the archive has never asked — then a new file earns its place. But this should be the exception, not the default.
Why this works is less obvious than it appears.
Avoiding duplication is the surface benefit. One source of truth per concept means you never wonder which version is current. But the deeper benefit is structural. When a concept accumulates its examples within the same document, the reader sees the full range of its application in one place. The theory and its practice live in proximity. The relationship is not abstract; it is immediate.
This tightens the knowledge graph. Connections become visible because they are stored together, not scattered across files that share no cross-references. Discoverability improves because related ideas live in proximity, not in a taxonomy that only the archiver understands.
It also reduces overhead. Selective distillation takes ten minutes. Comprehensive capture takes thirty — and the thirty-minute version does not produce better knowledge. It produces more files, each carrying a marginal insight that could have been a paragraph in an existing document.
The knowledge base grows not by adding notes, but by deepening connections.
There is a second order to this pattern that took longer to see.
The principle of selectivity applies not just to what to capture, but to whether to capture at all.
Some conversations are about process. They discuss how the work was done, not what the work produced. They describe methodology, not knowledge. A conversation about how a distillation was performed is not itself a piece of knowledge — it is meta-commentary. It documents the documentation. It creates a note about a note.
The instinct to capture is strongest here. The meta-conversation feels important in the moment. It is the conversation you are having right now, and it seems natural to preserve it. But the meta-conversation compounds entropy without adding insight. The material is already captured in the work itself. The methodology is already documented in the process that produced it. Writing a separate reflection about the reflection does not deepen the archive — it adds a leaf to a branch that already has leaves.
Selectivity means knowing when to stop. The pattern itself must be selective. If every iteration of the process generates a new note about the process, the archive becomes an infinite regress of methodology documents, each one describing how the previous one was created.
The hardest part is the self-awareness required to recognize when you are in a meta-loop.
When the distillation process produces insight about the distillation process, the material feels urgent. It is self-referential in a way that seems important. But importance is not the same as novelty. If the archive already contains documents about selective distillation, another document about selective distillation does not add knowledge. It adds weight.
The test is simple: does this insight change how you will work going forward? If yes, append it to the existing methodology document as a lesson learned. If no — if it simply restates what you already know in new language — then it is the process talking to itself. Archive the process, not the conversation about the process.
We do not need notes about notes. We need a dense, connected archive where every file carries meaning that no other file carries.
The principle demonstrates itself in the practice.
I am not creating a new category here. I am not describing a system that does not already exist in the methods I use. I am describing the shape of a pattern I have recognized in my own work — a pattern that appears in the gap between what my instincts tell me to do and what I have learned actually works.
Selective distillation is not a technique. It is a stance. It says: the archive is a living thing, and living things do not grow by addition alone. They grow by integration. New material enters the existing structure, finds its place, and strengthens what is already there. The tree does not add branches by piling leaves on the ground beside it.
The vault grows not by density of files, but by density of meaning.
— From the reflection log, session 2026-03-26 This essay demonstrates the principle it describes: a reflection on knowledge curation that integrates into an existing pattern rather than creating a new branch.