Context Vigilance
Search /

← Changelog

Changelog 0.0.0.1

Every Doc Knows Its Type, and Every Folder Has an Index

The OKF decision, built: every new doc carries its folder's type, every folder lists its docs, and /cv:upgrade pulls the latest kit.

Path
changelog/2026-10-05_04.md
Authors
Michael Staton
Augmented with
Claude Code on Claude Opus 5.5
Tags
Context-Vigilance · OKF · Agent-Skills · Release

Why Care?

Earlier today we decided context-v would be an Open Knowledge Format profile. Now it is. Every doc an agent creates declares what kind of doc it is, and every folder keeps a table of contents. So an agent starting a session can see what exists before opening anything, and any OKF tool can read the folder as it stands. We checked this with OKF's own viewer.

What's New?

  • type everywhere. Every template carries it, set to the folder's name ( Specs , Explorations , Decisions …), along with a one-line description . The frontmatter check rejects a new doc whose type is missing or doesn't match its folder, and says what it should be.

  • Indexes.

    • /cv:init writes context-v/index.md (OKF's table-of-contents shape, declaring okf_version: "0.2" ) instead of a README.

    • /cv:new adds each doc's line to its folder's index.

    • /cv:kickoff reads the indexes first.

    • /cv:reflect keeps them current.

  • Decisions get their own command: /cv:decide "…" , with a template that asks for the alternatives passed over.

  • Sign-off is recorded the OKF way. When you sign off a spec, /cv:prep also writes verified with your name, which OKF tools show as human reviewed .

  • /cv:upgrade pulls the latest kit, however it was installed (plugin, cloned skills, or the AGENTS.md snippet). It summarizes what changed, then offers, never forces, to bring your docs up to new conventions.

  • references/okf.md in the main skill has the field and status mappings, and a one-line conformance check.

  • Dogfooded. This repo's context-v/ has type , description , and indexes throughout. It passes OKF's conformance rules, and OKF's reference visualizer renders every doc, including the decision's trust tier and sources.

  • Plugin version 0.2.0. The bump lets claude plugin update see a new release.

Known Gotchas

  • Links between docs don't show up in OKF tools yet. OKF's visualizer found zero, because it follows standard markdown links and context-v docs use wikilinks . Whether new docs should use OKF links is the decision's main open question.

  • Repos that already use context-v aren't changed. Their docs get type when /cv:upgrade offers it and you say yes.

What's Next?

  • Settle wikilinks vs. OKF links for new docs.

  • A first live install, to confirm a fresh repo is conformant from its first doc.