Adding a Jev review gate to a self-running Obsidian note loop
Splits a Claude plus Obsidian looping note workflow into capture, context, draft, review and commit, with a small Jev decision model gating each commit at the review step.
CLAUDE + OBSIDIAN + LOOP ENGINEERING = KARPATHY'S SECOND BRAIN THAT RUNS ITSELF the core idea: your Zettelkasten vault is the loop's state, not the chat window everything Claude knows lives in a .md note, linked to the ones around it the loop: > capture - a thought lands in 00-inbox > context - Claude Opus 5.5 pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts and supersedes are Zettelkasten links the loop can read - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump runs 10-50x > if the review step keeps approving its own slop, bolt on Jev engineering: a small decision model gates every ship one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order worth stealing even without a graph: the review step. most vaults skip it, Claude writes straight to live notes errors compound without a sound for months set that gate first
This post quotes another post: x.com/mr_buzzoni/status/2066904909849440434