toolknowledge-basestandardspecagentsmarkdownprovenanceattestationsinteroperabilityexportUpdated 2026-08-11

Open Knowledge Format (OKF)

OKF v0.2 is a portable Markdown-bundle contract for agent knowledge. Kevin Wiki keeps its richer evidence graph and operating registries canonical, then emits a privacy-filtered, deterministic OKF projection at /api/okf.

View original tweet

Current specification

Google Cloud launched OKF v0.1 in June 2026 to formalize the LLM-wiki pattern: ordinary files, one Markdown concept per path, YAML frontmatter for the small queryable surface, and links as the graph. The repository specification moved to v0.2 in July; the launch post and screenshot remain useful lineage evidence but are no longer the current schema. Source: Google Cloud launch post, 2026-06-12; GoogleCloudPlatform/knowledge-catalog/okf/SPEC.md at 3fcbb9f, reviewed 2026-08-11

The v0.2 bundle contract is deliberately small:

  • Every non-reserved .md file is one concept. Its bundle-relative path without .md is its identity.
  • type is the only field required on every concept. Consumers tolerate unknown types and keys and preserve unknown keys on round trip.
  • title, description, resource, and tags are recommended rather than mandatory.
  • index.md provides progressive disclosure and log.md provides newest-first dated history.
  • Concepts use ordinary Markdown links, either bundle-root-relative or file-relative. Broken links do not invalidate a bundle.
  • A root index.md may declare okf_version: "0.2".
  • references/ is the conventional home for supporting external material and code. Source: OKF v0.2 SPEC §§2–5, frozen from knowledge-catalog@374e0bc4

Trust, freshness, and provenance

v0.2 is materially more useful than the launch version because it separates evidence, production, verification, and lifecycle:

Field Meaning Kevin Wiki rule
sources[] Evidence resources plus optional stable IDs and credibility facts such as author, usage count, and last modified Export mechanically resolvable public source URLs; retain only a digest of the canonical source note until claim-level normalization is proven.
generated.by / generated.at Producer identity and production time Use a deterministic exporter identity and a source-derived timestamp so replay is stable.
verified[] A distinct verification event; human and machine verification imply different trust tiers Omit it unless an actual verifier and event exist. Generation is not verification.
status draft, stable, or deprecated; absence means stable Do not infer lifecycle from directory names or page age.
stale_after Absolute freshness deadline Emit only when the owning source/workflow has an explicit freshness contract.

OKF records credibility facts, not a universal credibility score. Per-claim attribution can use Markdown footnotes keyed to sources[].id; this is stronger than an unstructured bibliography because the reader can identify which source supports which sentence. Source: OKF v0.2 SPEC §§4.2–4.6

Attested Computation

v0.2 introduces an Attested Computation concept for a reproducible calculation whose runtime, declared parameters, computation, executor resource, and deterministic attester are described in the bundle. The agent supplies parameter values but does not rewrite the computation. An executor returns a receipt; a separate no-LLM attester returns a verdict. Per-run receipts remain runtime artifacts outside the knowledge bundle, and concept verification is separate from run attestation. The exact receipt wire format, attester ABI/sandbox, caching, and semantic templates remain deferred. Source: OKF v0.2 SPEC §6

This maps to Workflow Run Contract without replacing it. Kevin Wiki's run receipt covers every workflow, including subjective research and UI work. Attested Computation is the narrower portable shape for deterministic calculations. Never label an ordinary agent run attested merely because it produced logs.

Kevin Wiki architecture decision

Kevin Wiki is OKF-shaped but not canonically OKF-formatted. The canonical system deliberately carries more structure than a portable bundle:

Concern Canonical Kevin Brain Public OKF projection
Source truth Content-addressed source revisions and frozen artifacts Resolvable public source resources only
Compiled truth Markdown owners with Kevin-specific frontmatter and wikilinks One v0.2 concept per public owner with ordinary Markdown links
Operating graph Stable object, source, goal, loop, workflow, and review registries Path identity plus cross-links
Decisions Machine-checked source-review records with before/after digests Not flattened into concept claims
Execution proof Private or scoped run receipts outside public truth Receipts remain outside the bundle, matching v0.2
Discovery _index.md, qmd, /system, JSON APIs Generated index.md trees and /api/okf/...
Change log Private operational wiki/log.md Sanitized conformant log.md; the private log is never copied
Privacy Shared fail-closed public projection policy The same policy runs before any OKF file is emitted

Mutating all canonical pages to OKF would discard useful distinctions and create a second migration problem. The adopted boundary is therefore:

source revisions + reviews + stable objects + canonical Markdown
                         │
             deterministic public projector
                         ▼
      OKF v0.2 indexes + concepts + safe manifest
                         │
             /api/okf/{path}.md

The projector converts wikilinks outside code fences to relative Markdown links, creates progressive-disclosure indexes, extracts public source URLs into sources[], records generated, and retains only a digest of any unmapped canonical source note in the tolerated kevin_wiki extension. It validates every emitted concept, omits gated/private pages before serialization, and exposes only the generated tree. Source: ui/scripts/lib/okf-export.mjs; ui/src/app/api/okf/[[...slug]]/route.ts, 2026-08-11

Run locally:

npm run okf:check
npm run okf:export

The first full replay emitted 1,252 public concepts, omitted 328 private/reserved inputs, produced zero structural conformance errors, and replayed to the same bundle digest. The production build regenerates the bundle into .content/okf, and llms.txt advertises its root at https://wiki.kevinliu.biz/api/okf. Source: OKF export receipt, 2026-08-11

Honest compatibility boundary

The current export is structurally conformant v0.2, not semantically perfect provenance normalization:

  • Existing inline [Source: ...] notes remain in bodies; they are not yet rewritten into keyed per-claim footnotes.
  • Custom ::tweet and ::artifact blocks remain Markdown extensions. Consumers that do not understand them still receive the surrounding text and source URLs.
  • Unmapped canonical source notes become kevin_wiki.source_note_sha256; local/private evidence labels, private files, and the operational log are not copied.
  • verified, status, and stale_after are omitted unless evidence or an owner contract supports them. The exporter does not invent trust.
  • The bundle is an interoperability surface, not a writeback authority. Agents must route durable changes through the source-review and stable-object contracts.

These gaps are explicit because “parseable” is not the same as “all provenance semantics normalized.” A future upgrade should add claim-to-source footnote mapping only with a reversible parser and false-attribution tests.

Reference implementation and adoption signal

The official Apache-2.0 repository includes BigQuery metadata extraction, a bounded same-domain web-enrichment pass, sample bundles, and a self-contained Cytoscape/Marked viewer. At the 2026-08-11 review it had 8,466 stars, 721 forks, no tagged releases, and four sample bundles; the reference Python package still identified itself as 0.1.0, so the specification is ahead of parts of the tooling. Use the spec commit, not package marketing, as the compatibility target. Source: GitHub repository/API and frozen tarball at knowledge-catalog@374e0bc4, 2026-08-11

Timeline

Related Pages

Karpathy LLM Wiki Setup GuideWiki Brain Operating ModelBrain Source FabricWorkflow Run ContractGenerated Surface ContractContext Engineering

8 pages link here

Brain Source FabricArchitectureGenerated Surface ContractMetaKarpathy LLM Wiki Setup GuideToolsSkill ResolverSkill ResolverSource Compile WorkflowWorkflowsWiki Page FormatMetaWorkflow Run ContractWorkflowsX Bookmarks: AI Agents & Tools (Jan 2025 – Jun 2026)Tools