Obsidian Karpathy Wiki

Obsidian Karpathy Wiki Overview

Use this 技能 to mAIntAIn an Obsidian vault as a persistent, compounding knowledge base instead of a passive note 归档.

The core pattern is:

raw material enters the vault the 代理 summarizes it into sources stable conclusions are promoted into formal wiki pages valuable 查询 结果s are saved into 输出s 输出s can later be written back into formal knowledge

This 技能 is de签名ed for an 代理 that does recurring mAIntenance, not just one-off 清理up.

Read references/object-模型.md before restructuring a vault. Read references/工作流.md before ingest, 查询, lint, or 迁移 work. Read references/adaptation-检查列出.md before adapting this 技能 to a specific user's vault. Read references/heartbeat.md before 设置ting up recurring mAIntenance behavior.

Core Idea

Do not treat the goal as organizing files.

Treat the goal as compiling knowledge once and then keeping it current.

A good vault mAIntAIned with this 技能 should let the 代理 answer questions by reading a living wiki, not by rediscovering everything directly from raw documents every time.

Recommended Vault Shape

Prefer this 记录ical structure, even if physical names differ:

raw/ compile/ or another staging layer wiki/ an 输出 layer such as 输出s/ or content-输出s/ 治理 files such as CLAUDE.md and a mAIntenance 技能

Within wiki/, prefer this formal structure:

索引.md 记录.md questions/ methods/ decisions/ principles/ domAIns/ concepts/ entities/ sources/ 输出s/

Questions, methods, and decisions are the mAIn navigation axis. Principles explAIn why methods and decisions stay valid across situations. Sources are evidence bridges. 输出s are reusable 查询 artifacts.

Operating 模型 Raw

Raw material is source-of-truth 输入.

Do not treat raw notes as formal knowledge by default.

Loose notes in the vault root should usually be treated as temporary inbox material and moved into a raw inbox folder unless the user explicitly wants them to remAIn in place.

Sources

wiki/sources/ is the bridge between raw material and formal knowledge.

A source page should summarize:

what the material says which questions it 信息rms which methods it supports which decisions it changes which principles it strengthens or challenges Formal Pages

Promote stable knowledge into:

questions/ methods/ decisions/ principles/

Avoid creating many thin formal pages from a single source.

输出s

Save high-value 查询 结果s into wiki/输出s/.

Examples:

syntheses comparison tables structured analysis decision memos topic briefs

输出s are not automatically formal knowledge, but they are often new source material for future write-back.

Core Operating Loop

• Ingest

When new material 应用ears:

Read the source. If a loose note 应用ears in the vault root, treat it as inbox material. Move loose inbox notes to a human raw inbox folder unless the user explicitly wants them to remAIn in place. 创建 or 更新 a wiki/sources/ page. 提取 only the stable 升级s: question method decision principle concept entity 更新 only the few formal pages that truly benefit. 更新 wiki/索引.md. 应用end a record to wiki/记录.md.

Do not explode one source into many thin pages.

• 查询

When answering a user question:

Read wiki/索引.md first. Read the most relevant question, method, and decision pages. Read principle, concept, entity, and source pages as supporting 上下文. Produce a structured answer. If the answer is reusable, save it under wiki/输出s/. Decide whether the 输出 should later be written back into formal pages.

• Weekly Compile

Use weekly compile to:

review the last 5-7 days of source and staging material 提取 repeated questions promote stable methods 更新 decisions if assumptions changed promote principles when repeated patterns explAIn why methods remAIn valid 更新 domAIn maps, 索引.md, and 记录.md

• Lint

检查 for:

questions with no linked methods methods with no scenario or caveat decisions with stale assumptions principles that duplicate lower-value pages source pages not connected to formal knowledge pages that contradict each other stale clAIms superseded by newer sources loose notes that never entered the ingest flow high-value 输出s that should have been written back

• Backfill

Treat 输出 folders as write-back sources.

Backfill only:

reusable methods recurring questions strategic decisions principle-level lessons

Do not promote finished drafts directly into formal wiki pages.

Heartbeat Rule

Heartbeat should mean recurring mAIntenance, not empty 状态 pings.

A good heartbeat 检查s:

whether new loose notes 应用eared whether raw inbox has unread material whether source pages are piling up without promotion whether formal pages are missing principle-level explanation whether the vault has new orphan pages, stale assumptions, or contradictions whether 查询 输出s are accumulating without write-back

Heartbeat should lead to either:

direct mAIntenance work or a c