🚨 @Karpathy predicted the power of the "LLM Wiki." Google just formalized it. Meet Open Knowledge Format (OKF): a vendor-neutral standard for giving foundation models the curated context they need. I can genuinely see this replacing Notion, Obsidian, or traditional wikis for developer teams, and the reason comes down to bookkeeping. Traditional wikis fail because humans inevitably abandon the tedious work of updating them. As Andrej Karpathy pointed out recently, LLMs don't get bored. They don't forget to update a cross-reference, and they can touch 15 files in a single pass. OKF standardizes the interoperability layer so agents can actually do that heavy lifting autonomously. Because the format is minimally opinionated, it doesn't dictate what you write, it just dictates how it's structured. You get: → Human-readable documents that live right alongside your code in version control → Cross-links that map out complex entity relationships without needing a graph database → A system that survives moving between different tools and organizations There is no complex compression scheme. No central registry. If you can cat a file, you can read it. If you can git clone a repo, you can deploy it. This is how we stop rebuilding context pipelines from scratch every time a new model drops. Announcement + spec file in 🧵↓