Open Knowledge Format (OKF) bundle The Open Knowledge Format (OKF) bundle is a new convention for packaging knowledge bases as a tree of Markdown files with typed front matter, enabling AI agents to ingest an entire corpus in a single fetch instead of scraping page by page. The format emphasizes loose conformance, progressive disclosure via index.md files, and a change log, while leaving serving and discovery out of scope. The specification is already implemented on the author's site, with the bundle generated from the same content collection and advertised via an AI Catalog entry and llms.txt. Open Knowledge Format OKF bundle Publish your whole knowledge base as an Open Knowledge Format bundle — a tree of Markdown concept files with typed front matter — so an agent can ingest the entire corpus in one fetch instead of scraping page by page. What it is The Open Knowledge Format OKF is a convention for packaging a body of knowledge as a tree of Markdown files an agent can consume directly. Each file is a concept : a YAML front-matter block followed by Markdown prose. The only hard requirement is a non-empty type field; the format leans on a small set of recommended fields title , description , resource , tags , timestamp and lets producers add their own keys, which consumers must preserve rather than reject. A bundle is otherwise plain files and folders. index.md files give progressive disclosure — a reader can list a directory without parsing every concept. A root log.md records change history newest-first. A references/ directory mirrors external standards as first-class concepts so a check can cite them with a bundle-relative link. There is no manifest, no schema server, and no runtime: a bundle is the directory itself. Why it matters One ingest, not N scrapes. An agent that wants your whole corpus gets it in a single download instead of crawling every HTML page and stripping navigation. Typed, predictable structure. Every concept declares what it is. Front matter carries the metadata an agent would otherwise have to infer. Graceful for consumers. Conformance is deliberately loose — unknown types, extra keys, and missing optional fields must not cause rejection — so a bundle stays usable as it grows. OKF deliberately leaves serving and discovery out of scope . A bundle on its own is undiscoverable; pair it with a discovery surface — an AI Catalog entry /spec/agent-readiness/agentic-resource-discovery/ and an llms.txt /spec/agent-readiness/llms-txt/ pointer — so agents can find it. How to implement Generate the bundle from your existing source of truth; do not hand-maintain a second copy. For each item, emit