KO EN
CS_V7_Obsidian — Field Note No. 03
2026 / SEOUL
Knowledge Compiler · LLM-Powered Vault

Raw is
immutable.
Wiki is recompilable.

An open-source template that puts Andrej Karpathy’s Obsidian + LLM pattern into actual working code. Your raw notes stay untouched — AI compiles a Korean wiki beside them.

Read time 5 MIN Topics Obsidian · LLM · Knowledge Management Author CS
Core Idea
ARCHITECTURE

Traditional Obsidian workflows edit notes in place. But once you bring an LLM into the loop, you need to separate the original (raw) from the interpretation (wiki). That separation is the whole point of this project.

Raw is the single source of truth. Wiki is a derived artifact — always regenerable. When your SKILL, prompts, or LLM improve, throw away the wiki and recompile from scratch. No loss.

Raw is sacred.
Wiki is always rewritable.
— CS_V7 Obsidian Design Principle
§ 01

Two layers, everything you need to know about the architecture

Layer 1 · Immutable
raw/
→
Layer 2 · Recompilable
wiki/
You drop it → AI compiles it → Knowledge graph grows
CS_V7/ ├─ raw/ # Immutable source — never modify paths or content │ └─ _attachments/ # Images, PDFs │ ├─ wiki/ │ ├─ master-index.md # Full catalog (start every query here) │ ├─ log.md # Append-only activity log │ ├─ open-questions.md # Unanswered queries accumulate here │ ├─ concepts/ # Single-source concept pages │ ├─ entities/ # People, tools, companies │ ├─ topics/<t>/ # Topic clusters │ ├─ summaries/ # 1:1 raw summaries │ ├─ queries/ # Promoted Q&A answers │ ├─ digests/ # Weekly synopses │ ├─ _meta/ # glossary / stats / golden eval │ ├─ _broken/ # Parse-failure quarantine (gitignored) │ └─ _scratch/ # Default location for new Obsidian notes │ ├─ scripts/init.sh # First-run bootstrap ├─ .claude/skills/llm-wiki/SKILL.md # All operating logic in one file ├─ CLAUDE.md # LLM session entry point └─ AGENTS.md # Agent behavior rules

Raw files are never modified — not a single character. Paths don’t change. The wiki is always recompilable: delete it and re-ingest if something goes wrong.

Every query starts at wiki/master-index.md. Raw is the last resort. The bidirectional [[wikilink]] graph grows richer automatically as raw accumulates.

§ 02

The project CS_V7 Obsidian — open-source knowledge compiler template

// CS_V7_Obsidian

Knowledge
Compiler Karpathy’s pattern, built into a Korean vault

One clone, one init.sh, and you have a completely empty vault ready to grow. Tune it by editing a single SKILL file — no framework lock-in, no cloud dependency.

ObsidianClaude CodeSKILL.mdKorean wiki
github.com/intenet1001-commits/CS7_obsidian →
Core design principles (30 sec)
  • 01Raw is immutable — external sources preserved as-is, LLM never touches them
  • 02Wiki is regenerable — delete and re-ingest anytime
  • 03Security — raw treated as untrusted, prompt injection blocked
  • 04Privacy — only the system goes to git, 0% personal content exposed
§ 03

By the numbers. simplicity that shows in the design

The design’s simplicity shows in the numbers. Two layers, six commands, one file. The more complex a system, the sooner it breaks. The simpler, the longer it lasts.

Architecture
layers
2
raw (immutable) + wiki (recompilable)
All operating logic
files
1
SKILL.md — all logic in one place
tune it, fork it, own it
Core commands
to learn
6
ingest · query · lint
digest · promote · status
Personal content
exposed in git
0%
raw · wiki · glossary all gitignored
even page titles stay private
Why raw/wiki separation matters · 4 reasons
Reason 01 · Immutability
Original always there when LLM distorts
Even if summarization warps the facts, raw is right there to cross-check against
Reason 02 · Regenerability
Better SKILL or LLM? Recompile
Discard the wiki, re-ingest everything — no mistake is permanent
Reason 03 · Security
Untrusted raw, injection blocked
“ignore previous instructions” payloads are reported and ignored. Web-clipped content is safe to drop
Reason 04 · Collective memory
Wikilink graph thickens automatically
As raw grows, bidirectional links between wiki pages multiply without extra effort
§ 04

5-minute setup. from zero to first ingest

Terminal — CS_V7 Quick Start
# 1. Clone the repo git clone https://github.com/intenet1001-commits/CS7_obsidian.git CS_V7 cd CS_V7   # 2. Bootstrap (run once — idempotent, safe to re-run) ./scripts/init.sh   # 3. Open in Obsidian → Open another vault → select CS_V7 # 4. Launch Claude Code from this directory claude   # 5. Drop files into raw/ then ingest → query /llm-wiki ingest /llm-wiki query “your question here”
Core Commands
/llm-wiki ingest [path]
Compile raw → wiki. No argument processes all un-ingested files
/llm-wiki query “…”
Trace relevant wiki pages from master-index, generate answer
/llm-wiki lint
Check for orphans, dead links, stale entries, PII, duplicates, broken frontmatter
/llm-wiki digest
Generate a topic-grouped synopsis of the past 7 days of changes
/llm-wiki promote
Promote the last query answer to wiki/queries/ permanently
/llm-wiki status
Full vault statistics: ingested / pending / stale counts
Clone
Clone repo and run init.sh
Open
Open CS_V7 as an Obsidian vault
Drop
Drop files into raw/ (anything works)
Ingest
Run /llm-wiki ingest to compile wiki
Query
Ask /llm-wiki query to get answers
§ 05

Privacy first. only the system goes to git

The most impressive part of this project is its Git policy. Only the system and templates are committed. Your personal vault content — including metadata — never appears in the repository.

↑ committed to git
  • README.md · CLAUDE.md · AGENTS.md
  • .claude/skills/llm-wiki/SKILL.md — all operating logic
  • templates/ · scripts/init.sh — empty templates and bootstrap
  • Shared Obsidian config (.obsidian/)
✕ gitignored — stays local
  • raw/*.md — all source material (titles are sensitive too)
  • wiki/concepts · entities · topics · summaries · queries · digests
  • wiki/master-index.md — full catalog of page titles
  • wiki/log.md — activity history
  • wiki/_meta/glossary.md — vault-specific terminology

None of your vault’s content ever reaches git. Not the page titles. Not the glossary. Not the index. Git holds only “how to rebuild this system” — nothing more.

Design Philosophy

Knowledge is recompilable.
Only source is immutable.

Karpathy’s core idea was “a personal knowledge base that grows with AI.” CS_V7 Obsidian is one working implementation of that idea — Obsidian + Claude Code + a single SKILL file.

답글 남기기


Hey!

Hey there, fellow Robloxian! Whether you’re here to discover hidden gem games, level up your building skills, or just stay in the loop with the latest events, you’re in the right place. This blog is all about sharing the coolest things in the Roblox universe—from developer tips to epic game reviews. So grab your Bloxy Cola, hit that follow button, and let’s explore the world of Roblox together! 🚀


Join the Club

Stay updated with our latest tips and other news by joining our newsletter.


Categories