Google's Open Knowledge Format: the format is the easy part

Google Cloud just introduced the Open Knowledge Format (OKF): an open, vendor-neutral spec for packaging a company's knowledge as plain markdown files with a little structured metadata, so AI agents can actually use it. If you have read anything we have written, that idea should sound familiar. It is the exact foundation memrelay has been built on. So when the biggest cloud vendor in the world ships a standard that says "company knowledge for AI belongs in governed markdown," we do not feel threatened. We feel validated.

What the Open Knowledge Format actually is

OKF is small on purpose. It defines organizational knowledge as directories of markdown documents, each with a bit of YAML frontmatter: a type, a title, a description, tags, a timestamp, a pointer to the underlying resource. No new runtime. No SDK. No proprietary database. A human can read it, a machine can parse it, and any agent or tool can consume it without a vendor lock.

That minimalism is the whole point. The knowledge that AI needs is scattered across wikis, drives, repos, and catalogs, and every tool wants it in its own shape. A shared, boring, portable format fixes that. We made the same argument in your knowledge base should be plain markdown: the format that outlives every tool is the one you can still read in five years.

Why a Google standard is good news for us

For a long time the pitch for "make AI know your company" was a vector database and a pile of embeddings. We have never believed that is the answer, and we said so in RAG isn't memory. OKF is Google agreeing, in public, that the starting point is structured, human-readable knowledge, not a black box of chunks.

A standard does three useful things for a category:

• It settles the format debate. Markdown plus frontmatter is now the default, not a quirky opinion.
• It makes knowledge portable. Your company's memory is not trapped in one vendor's product.
• It raises the question everyone will ask next: the format is here, so who keeps the knowledge inside it true, fresh, and safe to share?

That last question is the interesting one.

The format is the easy part

Writing down a spec for markdown files is the easy 20 percent. The hard 80 percent is everything that happens after you have the files:

• Who decides what is true? When two documents disagree, a format cannot resolve it. A person has to. That is why your AI doesn't know your company even when the files exist.
• How does it stay fresh? Knowledge rots. Last quarter's number, the old policy, the deal that fell through. A spec does not update itself after a meeting.
• Who is allowed to see what? Finance data, board material, and a public FAQ cannot live at the same sensitivity. The format says nothing about that.
• How do changes get in safely? If any agent can rewrite your knowledge, it is not memory, it is a liability. Changes need review and an owner, not a free-for-all.

OKF is a clean way to represent knowledge. It is not, and does not try to be, the system that keeps that knowledge alive.

What memrelay adds on top

This is the part we have spent our time on. memrelay treats markdown as the source of truth, exactly as OKF does, and then makes it a living memory of your company:

• Governance. Nothing changes your knowledge without going through a change proposal that a human approves. You keep control.
• Freshness. Decisions from meetings fold back into the right document, so the memory tracks reality instead of drifting from it.
• Who-sees-what. Sensitivity and scoping are built in, so internal stays internal and customers only ever see what you meant them to.
• Answers you can trust. When your AI answers, it cites the source and now tells you whether that source is confirmed or still a best guess, so confident-and-wrong stops being the default failure mode.

The format is the substrate. The memory is the product. OKF makes the substrate a standard, which is genuinely good for everyone, and it makes the case for memrelay clearer, not weaker.

The takeaway

If Google's Open Knowledge Format tells you anything, it is that your company's knowledge should be plain, portable, and yours, not locked inside a model or a vector store. We agree so completely that we built the whole product on it. The open question OKF leaves on the table, keeping that knowledge true, current, and governed, is the one memrelay exists to answer.