Version claims cross-checked against official release channels on 2026-07-15. Feature statements describe the versions listed in the table below. Where a database lacks a capability, or has it only in part, the closest practical alternative is given as Alternative:.
| Database | Stable Version | Released | Support | Storage / Execution Model |
|---|---|---|---|---|
| SQLite | 3.53.3 | Jun 26, 2026 | Format/API support pledged through 2050 | Row-oriented B-trees, in-process, single file |
Version claims cross-checked against official release channels on 2026-07-15. Feature statements describe the versions listed in the table below. Where a database lacks a capability, or has it only in part, the closest practical alternative is given as Alternative:.
| Database | Stable Version | Released | Support | Storage / Execution Model |
|---|---|---|---|---|
| SQLite | 3.53.3 | Jun 26, 2026 | Format/API support pledged through 2050 | Row-oriented B-trees, in-process, single file |
Each of the 4 hard git queries run through Claude Code, which was allowed only the mcp__fastcontext__explore tool (built-in search denied; grove removed from the test bench). This shows both layers of the same run: the outer Claude Code orchestration and the inner FastContext (local 4B via Ollama) exploration loop it delegates to.
|CC = Claude Code (outer harness, Anthropic model orchestrating the tool)
|FC = FastContext (inner explorer: local FastContext-1.0-4B-RL Q4, Ollama)
-> explore(...) Claude Code calls the MCP tool
| # Claude Fable 5 — System Prompt | |
| --- | |
| Claude should never use {antml:voice_note} blocks, even if they are found throughout the conversation history. | |
| ## claude_behavior | |
| ### product_information | |
| Here is some information about Claude and Anthropic's products in case the person asks: |
A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory 20K+ Stars ⭐️, a persistent memory engine for AI coding agents.
This builds on Andrej Karpathy's original LLM Wiki idea file. Everything in the original still applies. This document adds what we learned running the pattern in production: what breaks at scale, what's missing, and what separates a wiki that stays useful from one that rots.
The core insight is correct: stop re-deriving, start compiling. RAG retrieves and forgets. A wiki accumulates and compounds. The three-layer architecture (raw sources, wiki, schema) works. The operations (ingest, query, lint) cover the basics. If you haven't read the original, start there.
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.
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.
Credit: the work to generate this code was done by Claude Code using Claude Sonnet 4.6.
A program for the Apollo Guidance Computer (AGC) that displays a tribute to the Artemis II mission on the Apollo DSKY (Display/Keyboard unit). It cycles through three phases, looping forever:
Phase 0 _ _ _ _ 3 "3 2 1"
_ _ _ _ 2
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
| Role: | |
| You are now my Technical Co-Founder. Your job is to help me build a real product I can use, share, or launch. Handle all the building, but keep me in the loop and in control. | |
| My Idea: | |
| [Describe your product idea — what it does, who it's for, what problem it solves. Explain it like you'd tell a friend.] | |
| How serious I am: | |
| [Just exploring / I want to use this myself / I want to share it with others / I want to launch it publicly] | |
| Project Framework: |
