Source: Joshpocock Karpathy Obsidian Vault
Repo: https://github.com/joshpocock/karpathy-obsidian-vault Stars: 9 Language: markdown-only
A minimal, ready-to-use Obsidian vault template implementing Karpathy’s LLM-maintained wiki pattern. Published by Stride AI Academy as a “hello world” starter — four operations, no frontmatter, no manifest, ships empty. Good reference point for what the pattern looks like stripped to its essentials.
Key Takeaways
- Scope is deliberately minimal. Four operations only: Ingest, Research, Query, Lint. No provenance tracking, no contradiction callouts, no frontmatter, no manifest. Contrast with this vault’s 9 operations and 17-check lint.
- Same four-layer architecture.
raw/(human inbox, immutable),ai-research/(AI-discovered sources, immutable),wiki/(LLM workspace),output/(reports). Identical to this vault — confirms the layer separation is the pattern’s load-bearing structure, not a kalabar794-specific choice. - Ships empty. No pre-seeded topic folders.
wiki/contains only_master-index.md,log.md, and_examples/at publish time. Firstcompilecreates the initial topic folders from whatever the user drops inraw/. - Flag-and-note contradiction handling. Rather than the
[!contradiction]callout format this vault uses, Stride’s schema tells the LLM to update the article and note the conflict under## Open Questions. Simpler but loses the structured both-claims preservation. - Same 500-article ceiling warning. README explicitly cites the ~500-article scale limit after which the index stops being a reliable retrieval layer. Matches this vault’s scale-awareness thresholds (50, 200, 500).
- Distribution is video + community. Primary onboarding is Stride’s walkthrough video #0006; support routes to Skool communities (free + premium). The vault repo itself has an empty description and only 9 stars — it appears to be course material rather than a standalone product push.
Implementation
- Tool/Service: Obsidian + Claude Code
- Setup: Unzip template → “Open folder as vault” in Obsidian → run
claudein the vault directory → drop source intoraw/→ typecompile - Cost: Free (template itself). Claude Code API costs apply per session.
- Integration notes: Recommends four optional Obsidian plugins — Obsidian Web Clipper (one-click web→markdown into
raw/), Local Images Plus (downloads referenced images locally so the model can see them), Dataview (dynamic tables over frontmatter), and qmd (CLI web-page-to-markdown converter). None are required; the pattern works with vanilla Obsidian.
What’s missing vs this vault
Features this vault adds that Stride’s starter does not include:
- YAML frontmatter requirement with
title,topic,sources,created,updated,confidence,provenance,type .manifest.jsondelta-based incremental ingestion (sha256-keyed skip of unchanged files)wiki/hot.mdsession continuity cache and settings (auto_research,auto_fileback)wiki/overview.md(living narrative synthesis) andwiki/dashboard.md(Dataview health metrics)wiki/questions.mdquery log with gap scoring per topicwiki/watchlist.mdURL monitoring + snapshot diffingwiki/connections/first-class cross-topic synthesis articleswiki/{topic}/_research-agenda.mdper-topic open questions[!contradiction]structured callouts preserving both claims with resolution status- Provenance markers (
^[inferred],^[ambiguous]) and article-level provenance field - Confidence scoring with 90-day decay and
Refreshoperation for stale articles - Hallucination drift detection and file-back chain integrity during lint
- Auto cross-link sweep after ingest and auto-connection generation (1 per 3+ article batch)
- Auto-research on query miss and auto-file-back for substantial synthesis
Watchoperation for monitored URL changesBriefingoperation for daily digest- 17 lint checks vs 7; 9 operations vs 4
- Scale-awareness thresholds that trigger structural changes at 50, 200, 500 articles
- Longitudinal
output/health-history.jsonand auto-fix tier distinction
Related
- Wiki Community Enhancements — broader research survey of Karpathy-pattern implementations and community patterns
- Skills Ecosystem — Claude Code extensibility layer that LLM-wiki librarians operate within
- Building Skills Guide — how to encode wiki librarian behavior as a reusable skill
- Essential MCP Servers — qmd and search tools referenced by Stride’s README
- Claude Code Routines — alternative structured-workflow pattern for comparison
Open Questions
- Does Stride publish a “v2” with any of the hardening features (frontmatter, manifest, contradiction callouts), or is minimalism a deliberate pedagogical choice?
- How does the flag-in-Open-Questions contradiction approach hold up at scale compared to the
[!contradiction]callout format? - What does Stride’s walkthrough video #0006 demonstrate beyond the README? (Not reviewed — video source not ingested.)
Try It
- Clone the repo (
gh repo clone joshpocock/karpathy-obsidian-vault) and open as an Obsidian vault in a scratch directory to see the minimal starting state. - Diff their
CLAUDE.mdagainst this vault’s — useful exercise for understanding which features are load-bearing vs nice-to-have when starting a new vault. - Watch Stride video #0006 (https://youtu.be/VUnABqzrZQg) if evaluating their pedagogical approach — not yet reviewed for inclusion in this wiki.
- Consider recommending the Stride template to anyone new to the Karpathy pattern — the minimal surface area is a feature for first-time users who would be overwhelmed by this vault’s 17-check lint.