Context-V Speaks the Open Knowledge Format

Why Care?

Context-v has always been a folder of markdown files with YAML frontmatter. So is the Open Knowledge Format (OKF), an open spec from Google Cloud for knowledge that people write and agents read. They turned out to fit together almost exactly. Now a context-v/ folder is meant to be readable by any OKF tool, with no translation step.

What's New?

• A decision, logged where decisions go. context-v/decisions/ exists now, and its first doc says context-v is a profile of OKF v0.2: OKF's few requirements, with context-v's folders, lifecycle, versions, and IDs on top. It names the alternatives we passed over and what's still open.

• Every doc declares a type , and it's the folder's name: type: Specs , type: Explorations , type: Decisions , type: Loops . It's never a judgment call, so a check can verify it.

• Folders are plural, and new ones are welcome. The canonical set is a starting point. Create narratives/ or research-notes/ when the work calls for it, and its docs carry that name as their type. extra/ and sitemap/ stay as the long-standing singular exceptions.

• Our lifecycle maps onto OKF's. OKF's status is draft, stable, or deprecated; context-v keeps its richer one and publishes the mapping.

• README has a new section on folders, types, and OKF, and links the decision.

• On the site: a new Context-v is an OKF bundle pattern, and the folders and frontmatter patterns now cover type and open folders.

Known Gotchas

• Not built yet. The templates, /cv:new , and the frontmatter check don't set or require type yet, and the root index.md that replaces context-v/README.md isn't written. The decision doc lists these as the next step.

What's Next?

• Build the decision: type in templates and the check, and the OKF-shaped index.md .

• Open the kit's own context-v/ in OKF's reference visualizer as a conformance test.