Open Knowledge Format (OKF) is a draft v0.1 specification for packaging knowledge as a directory of Markdown files with YAML frontmatter. Its core purpose is interoperability: producers can write knowledge once, and humans or agents can consume it without a custom SDK.

Structure

| Element | Meaning |

|---|---|

| Knowledge bundle | A directory tree of Markdown files. |

| Concept | One non-reserved Markdown file representing one unit of knowledge. |

| Concept ID | The concept file path without the `.md` suffix. |

| Frontmatter | YAML metadata at the top of a concept file. |

| Body | Free-form Markdown, preferably structured with headings, lists, tables, and citations. |

| Link | A normal Markdown link that creates a directed relationship in the bundle graph. |

Conformance Boundary

For OKF v0.1, the hard conformance surface is intentionally small:

• Non-reserved concept files need parseable frontmatter.
• Concept frontmatter needs a non-empty `type`.
• `index.md` and `log.md` are reserved files with special navigation/history roles.
• Consumers should tolerate unknown types, optional fields, missing indexes, and broken links.

Meta Museum Usage

Meta Museum uses OKF as a project-knowledge layer under docs/knowledge(../index.md). This bundle is for agent-readable synthesis about standards, decisions, workflows, and evidence. It complements, but does not replace, the canonical project docs, Linked Art records, ActivityStreams evidence, or partner artifacts.

Related

• LLM Wiki Pattern(llm-wiki-pattern.md)
• Meta Museum Knowledge System(meta-museum-knowledge-system.md)
• LLM Wiki Maintainer Schema(../schema/llm-wiki-maintainer.md)

Citations

[1] Open Knowledge Format v0.1 specification

[2] Google Cloud OKF announcement(../sources/open-knowledge-format-google-2026-06-12.md)