foundrylisted

<objective> Build and maintain a compounding personal wiki. The vault is the durable asset; the agent is its full-time maintainer. Knowledge enters through a single `inbox/`, is promoted to immutable atomic source notes under `sources/`, and is woven into evergreen concept pages under `wiki/` that get denser as material accumulates. Cross-referenced via wikilinks. Linted by the agent. </objective> <essential_principles> <principle name="three-folders-discriminated-by-frontmatter"> The vault has exactly three folders: `inbox/` (staging), `sources/` (immutable atomic source notes — one per article/paper/transcript/tweet), and `wiki/` (concepts, queries, people, plus three always-present singletons: `index.md`, `log.md`, `health.md`). Note kind is discriminated by the `type` frontmatter field, not by folder nesting. </principle> <principle name="self-contained-by-default"> No external read contract. The skill operates entirely inside one vault. If the user later wants to cite into a second vault (e.g. an existing Obsidian vault), they can add that as a one-way read contract in the vault's `CLAUDE.md` — but the skill does not assume one exists. </principle> <principle name="sources-are-immutable-wiki-is-evergreen"> Once a source note is written and triaged, it is not rewritten. It is the atomic ledger of what entered the system. Concept pages under `wiki/` are the compounding asset — they get edited, densified, re-organised, and cross-linked indefinitely. Queries are written-