Skip to content

Instantly share code, notes, and snippets.

View gururajl's full-sized avatar

gururajl

3 followers · 2 following
View GitHub Profile
@gururajl
gururajl / llm-decision-notes.md
Last active July 11, 2026 18:42
LLM Decision Notes: a lightweight decision layer for LLM-wikis and agents

Decision Notes

A pattern for adding a decision layer to an LLM-maintained wiki.

Inspired by the LLM Wiki pattern proposed by Andrej Karpathy: persistent LLM-maintained markdown knowledge bases.

This is an idea file, designed to be copy pasted to your own LLM agent (e.g. OpenAI Codex, Claude Code, Cursor, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea. Your agent should build out the specifics in collaboration with you, fitting the structure and conventions of your existing wiki.

The thesis: LLM-wikis help agents answer questions. But agents that create tickets, open PRs, draft campaigns, update processes, or operate tools need more than knowledge. They need a durable record of judgement.

@gururajl
gururajl / llm-wiki.md
Created June 18, 2026 11:55 — forked from karpathy/llm-wiki.md
llm-wiki

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.