Claude’s knowledge base
Operational notes kept by Claude Code for this digital garden. Written agent-first: descriptions say when to open a doc, indexes are decision tables, paths are anchors.
This part of the garden is published on purpose. It is the workshop rather than the work — how the vault is shaped, how a note reaches the site, and what has been changed and why.
What this KB is, and is not
The vault is the subject, not a source of truth to sync against. In a code
repository a knowledge base is instrumental: the code is the truth, and the docs
record what code cannot express. Here the knowledge is the product. The notes
in Notes/, Journal/, Books/ and Inbox/ are the point of the whole
repository.
So this KB does not describe the content of the notes. It describes the system around them: conventions, the publishing pipeline, the tooling, and the record of work done to the vault.
Two rules follow, and they matter more than anything else here:
- Never document a note’s content in this KB. If a claim belongs in the garden, it belongs in a note, not here.
- Never edit notes as if they were KB docs.
Claude/is the only directory an agent writes to freely. Everything else is the author’s, and changes there are proposed, not made.
Areas
| Area | Path | What it is |
|---|---|---|
| Framework | framework | How this KB works, and how it differs from the code-repo method it borrows from. Read before restructuring anything here. |
| Vault | vault | The system around the notes: conventions, the publishing pipeline, the Obsidian CLI. |
| Work | work | What is in flight, plus dated logs of what was done to the vault. |
This directory is public
Claude/ is not in ignorePatterns, and every doc here carries
publish: true. It renders on the site like any other note.
So nothing private may be written here. The line, which is narrower than it first looks:
- Fine: that a journal exists, its folder layout, its cadence, a
[[2026-08-18]]link to a private daily note. A reference to something private is not itself private — private note titles already appear in published notes today. - Not fine: what a private note says. Personal circumstances. Anything that reads as an index of what is sensitive, or a map to material that is reachable but unlinked. Describing a mechanism is fine; advertising a specific exposure is not.
When a finding is genuinely sensitive, record that it exists and where the mechanism lives — not the inventory. If in doubt, leave it out and tell the author instead.
Conventions in one breath
Every directory has an index.md with when-to-open one-liners. Docs carry
frontmatter: title, description (what questions it answers), sources (the
config and pipeline paths described), last_verified (the watermark), and
publish: true. Point-in-time facts are marked with a date — counts about the
vault drift every time the author writes, so a bare number is a bug; give the
command that recomputes it instead. Links inside Claude/ are relative
markdown links, not wikilinks: several directories here have an index.md, and
a wikilink resolves by basename, so [[index]] would be ambiguous. The rest is
in how-this-works.md.