Open Knowledge Format
A formal specification published by Google Cloud that defines a standard structure for organizing knowledge into bundles (folders) of plain text files, where each file represents one concept and files can link to each other, designed to work with language models
As defined in Google's OKF: Why a Folder Beats the Vector Database
Where it comes up · 1
Most important claims · 10 of 12Search all claims for “Open Knowledge Format” →
- On June 12th, Google Cloud published the Open Knowledge Format, a formal specification that standardizes Karpathy's loose community idea of using plain text files for knowledge organization.Google's OKF: Why a Folder Beats the Vector Database
- The Open Knowledge Format specification is intentionally minimal, defining a bundle as a folder, with each file representing one concept, file paths serving as names, links between files forming a graph, two special file names (one listing contents and one logging changes), and one hard rule: every file must declare its type in one field.Google's OKF: Why a Folder Beats the Vector Database
- The deepest catch is that the Open Knowledge Format standardizes the container, not the meaning—the one required field is a free-form label, so one team writes 'BigQuery table' while another writes 'table' and another writes 'relational asset,' and all are valid, but each speaks a different language and agreeing on what's inside is still the team's responsibility.Google's OKF: Why a Folder Beats the Vector Database
- The underlying idea that plain text folders are a better approach to machine memory than vector databases has already won, regardless of what happens to the Open Knowledge Format specifically, because the most overfunded field in tech spent two years and a fortune convincing itself that giving machines memory needed exotic infrastructure when a tidy folder of text files did the job better.Google's OKF: Why a Folder Beats the Vector Database
- The pitch of the Open Knowledge Format is that the AI does the bookkeeping that humans always abandon, which rests on an assumption about human behavior that the specification itself provides no mechanism to enforce.Google's OKF: Why a Folder Beats the Vector Database
- The Open Knowledge Format did not come from Google's AI lab but from Google's BigQuery team, every sample data set ships on BigQuery, the reference tool that writes the bundles runs on Gemini, and the easiest place to pour a finished bundle is Google's own knowledge product that they just renamed for exactly this moment.Google's OKF: Why a Folder Beats the Vector Database
- Google dropped Karpathy's instructions for how the AI maintains the wiki from the Open Knowledge Format specification, keeping the folder structure but removing the mechanism that keeps the knowledge current.Google's OKF: Why a Folder Beats the Vector Database
- The Open Knowledge Format specification orders any tool reading a bundle to forgive almost everything—unknown fields, broken links, and files that cannot be parsed—making it an enterprise standard from Google whose defining feature is how little it demands and how much it lets you break.Google's OKF: Why a Folder Beats the Vector Database
- The primary catch with the Open Knowledge Format is that the specification has no mechanism to keep knowledge current; while it includes a field for a timestamp, a field is not a process, and nothing in the format updates itself, so on a shared team folder it will go stale in a month because nobody volunteers to tend it, and agents start answering from expired knowledge.Google's OKF: Why a Folder Beats the Vector Database
- The Open Knowledge Format is not competing with MCP (Model Context Protocol); MCP is the pipe that moves data around live while the Open Knowledge Format is the cargo that moves through it.Google's OKF: Why a Folder Beats the Vector Database