Liam Wilkinson

Open Knowledge Format

The specification this collection is published in: markdown files with YAML frontmatter, a small set of required keys, and trust signals carried in the record itself.

Standard · 2026High confidence

Checked 2 October 2026 · AI-assisted review

Canonical repository migration and v0.2 specification’s type, extension and provenance rules.

GoogleCloudPlatform: Open Knowledge Format v0.2 specification
Type is the only always-required key, unknown types/fields are tolerated, generated and verified are separate, and the specification identifies itself as v0.2.
Previous OKF directory migration notice
Old directory is a frozen snapshot; canonical work moved to the separate open-knowledge-format repository.

What this check doesn’t establish

Main-branch specification can change. This confirms the inspected version’s rules, not an exhaustive conformance audit of this collection.

Confidence applies to the scope above, not every claim made by the underlying source. How confidence works

The format this collection conforms to. Its relevant properties are that a bundle is a directory of markdown files, that type is the only always-required field and is deliberately an open string, and that provenance and verification are carried in frontmatter rather than inferred.

Two of its provisions shaped this collection more than the rest. Consumers must not reject unknown types, which is why record types here are open. And verified is separate from generated, because authorship is not confirmation.

Attested Computation, the part of the specification aimed at sanctioned re-runnable computations, is not used here. The Finding records are the closest thing to it and would be the place to revisit that decision.

Projects