Google Cloud Releases OKF v0.3: Trust Tiers Count Only the Latest Verification, Plus Two New Agent Skills

Google Cloud announced v0.3 of the Open Knowledge Format (OKF). It adds conformance rules, trust tiers that count only current verifications and a superseded_by mechanism, along with use-case guides and two Agent Skills.

News date: About 7 min read

Share on LINE
Contents
  1. 1. What changed in OKF v0.3 compared with v0.2?
  2. 2. How do trust tiers update as agents edit content?
  3. 3. Which changes could affect existing bundles?
  4. 4. What are the use cases and Agent Skills?

Google Cloud announced on its Data Analytics blog that version 0.3 of the Open Knowledge Format (OKF) was released on the day of the post. OKF is an open specification that uses plain markdown and YAML files to give AI agents the background context they need. AI agents are AI assistants that carry out tasks automatically. A set of knowledge files delivered together in one folder is called a bundle. The specification, use cases and skills all live in a new standalone GitHub organization. This update matters most for teams that let several agents edit a knowledge base together and exchange it between organizations. It makes clearer who reviewed something and whether the content changed after that review.

What changed in OKF v0.3 compared with v0.2?

According to Google Cloud, OKF launched in June. In July, v0.2 added trust signals: provenance (where knowledge came from), trust, freshness, lifecycle and attestation (a formal check that a result is correct). v0.3 focuses on three situations: bundles moving between organizations, multiple agents editing the same corpus (body of content), and independent tools that need to read a bundle the same way.

  • Conformance: v0.3 adds a formal conformance section. The spec is self-contained and uses RFC 2119 keywords, the standard terms such as "MUST" and "SHOULD" that mark how strict a requirement is. It builds on YAML 1.2 frontmatter (the metadata block at the start of a file), CommonMark with GFM tables and footnotes, and RFC 3339 timestamps.
  • Coexistence: OKF consumers (tools that read bundles) skip .md files without a type. This means README.md, AGENTS.md, CONTRIBUTING.md and SKILL.md can sit inside a bundle without breaking it.
  • Tolerance: consumers accept nulls, empty strings and a single value where a list was expected without failing. Validators only log warnings for malformed entries. A bundle never fails because an optional field is missing or a link is broken.
  • Self-description: the index.md file at the bundle root can carry frontmatter such as okf_version, title, description and license. This helps an agent decide which bundle to use.
  • Supersession: the new superseded_by field lets a deprecated (retired) concept point to its replacement. The same mechanism handles moves and renames.

How do trust tiers update as agents edit content?

v0.2 gave every concept one of three trust tiers: unverified, machine-confirmed or human-reviewed. Google notes that in v0.3, only current verifications count. A verification is current when it happened at or after the last meaningful change to the content, which is recorded in generated.at.

In Google's example, a person reviews and signs off on a metric definition, and a week later an agent refines that definition. The concept then counts only as machine-confirmed until a person confirms it again. The old sign-off stays in the file as history, and an interface can show it as "reviewed before the last change." v0.3 also adds a team: actor prefix alongside human: and process:. However, only human: earns human-reviewed, because a team name doesn't say which person actually checked the content.

Which changes could affect existing bundles?

Google says v0.3 has two breaking changes, and existing v0.2 bundles stay readable. The table below summarizes these two changes and other highlights.

Main changes in OKF v0.3 and compatibility (summarized from Google Cloud's description)
Itemv0.3 approachCompatibility / notes
Path fields and link resolutionValues with a scheme are absolute URLs. Values starting with / resolve from the bundle root. Anything else resolves from the directory of the containing file.Breaking change. For bundles marked v0.2 or earlier, or with no version, consumers can also resolve from the bundle root.
Trust tiersOnly current verifications countBreaking change. No fallback is needed, since tiers can only go down.
Bundle metadataindex.md can carry okf_version, title, description and licenseTools that regenerate index.md must keep this frontmatter.
Extension fields (custom keys)Allowed at any level. A producer that edits a file must keep keys it doesn't understand.Future versions will never define keys starting with x-.
Versioning policyBefore 1.0, minor versions may include breaking changes, each documented with a consumer fallback where possibleFrom 1.0, minor versions will be strictly additive. Released normative text (the binding wording of the spec) will not change in place.

What are the use cases and Agent Skills?

The OKF core spec is deliberately kept small. It links to existing domain schemas such as Avro, Protobuf and OpenAPI instead of duplicating them. Google's new use cases are community guides for using OKF with other industry standards. Each guide explains where the boundary sits, how to link the two and what an agent should do with the combination. Each also includes a complete worked example you can copy. Use cases are layered on the core spec rather than being part of it, and a bundle that ignores them is still conformant. Each use case lives in its own folder under usecases/ in the repository. Google welcomes proposals by pull request, and a rough first draft is fine.

The two skills follow the open Agent Skills format, so any agent that supports skills can load them. According to Google, okf-generate writes, updates, migrates and validates bundles from available sources. It cites a source for each claim and records a human review only when that person confirms it. okf-consume answers questions from a bundle. For each concept it uses, it reports the trust tier, status, freshness and attestation result. It runs attested computations only through the bundle's configured executor and attester.

How do I install the skills in Gemini CLI?

Google's post lists the following Gemini CLI commands. For installation steps for other agents, see the repository README.

Gemini CLI install commands from Google's post (okf-generate and okf-consume) · bash
gemini skills install https://github.com/open-knowledge-format/open-knowledge-format --path skills/okf-generate
gemini skills install https://github.com/open-knowledge-format/open-knowledge-format --path skills/okf-consume

Frequently asked questions

Can my existing v0.2 bundles still be used?

According to Google, yes. Existing v0.2 bundles stay readable, and type is still the only required field. Path resolution has a fallback for older bundles. Because only current verifications now count, some concepts can show a lower trust tier than before.

Why does the tier drop when an agent edits content after a human review?

In v0.3, a verification counts only if it happened at or after the last meaningful change to the content. The old sign-off is kept as history. The concept counts only as machine-confirmed until a person confirms it again.

Are use cases part of the core spec?

No. Google explains that use cases are layered on the core spec, and a bundle that ignores them is still a conformant OKF bundle. If a convention proves itself across several use cases, it can be proposed for the core spec through the usual process.

Where are OKF's code and spec?

Google says the project has moved out of the Google Cloud Platform GitHub org into a standalone organization. The repository is github.com/open-knowledge-format/open-knowledge-format, and it holds the spec, samples, use cases and reference implementations.

Browse the latest news in this topic

Found this guide helpful? Share it with someone who needs it

Share on LINE

Sources

Compiled from the references and verification dates listed above; fares, schedules, product features, and terms can change, so please confirm the latest details on the relevant official website before travelling, booking, or purchasing.

Lifestyle