OKF: The new AI standard we will all need to adopt

OKF: The new AI standard we will all need to adopt Right now, every serious business is trying to figure out how to incorporate AI into their workflow. part of that is how you structure your company's knowledge. As of today, June 12th, we have the very first standard for how that structured. This is the moment And as I guessed, it's Google who's putting forth this standard. No surprise there. They just put out a blog post announcing the Open Knowledge Format, or OKF. about this. I already recorded a video, and I had to record though it's 100 degrees outside right now. If Google is successful in getting businesses to adopt this standard and I think they will. success with Universal Commerce Protocol and Getting your company's knowledge base set up using this standard is going to be the most important step for you to take before integrating AI. If you watch my videos bullish I am on setting up this for your company. We build this out for all of our clients. We call it their brand ambassador. And me and my team are already talking about how we might adapt ambassadors to this new standard. standard so great? The standard itself is pretty simple. I mean, it makes But what actually makes it great is just that there's a standard If we can all agree how your knowledge should be structured, then every AI agent or harness or skill can assume knowledge is structured and then we move from having to create custom processes in isolation, and into a share and iterate on each other's processes. This absolutely has to happen for us to make quick progress. if Google's standard will be adopted, but I mean, It's Google. competing standards right now, and it does make sense. Tell us what it is already. First of all, it's just files. There's no SDK or compression schema that you have to worry about. It's just a series of markdown files in a nested hierarchy. Within each folder, you can have an optional index file that describes all the other files in that folder, and at the top of each Markdown file, there's a mandatory YAML frontmatter. complex at all, trust me, it's not. It's just some text at the top of each file defining fields like title, description, tags, type, resource, and timestamp. Only a few of these are mandatory. and the agent quickly look up relevant files. And then you can add as many custom What Google has released so far is just version 0.1 of the standard. It'll probably change makes sense in its current form. changes will come from people actually implementing it and seeing what best practices emerge. And then over time, those best practices will likely be integrated But where will these files live? Well, ultimately knowledge to be platform agnostic. file to live in a single location. heading, I'm guessing most businesses will set this up inside That's what we're planning to do ourselves. huge rush to adapt to this standard. However, it's so close to the best practices that already exist, and it makes so much sense given where AI is headed, that I think you'd be safe adopting And if you haven't already started knowledge base, I highly recommend immediately