Every context-v Doc Now Declares Its Type

Why Care?

The context-vigilance kit now treats every context-v/ folder as an Open Knowledge Format (OKF) v0.2 bundle. The rule that makes that true is small: every doc declares a type, the name of the folder it lives in. With it, any OKF tool can read LFM’s context-v/ without knowing anything about our conventions.

The last commit filed the twelve docs that sat loose in the context-v/ root into folders. That was the prerequisite: a doc with no folder has no type to declare. This entry finishes the job.

This is a compliance change, not a content change. No doc’s body, dates, version, or status was touched.

What’s New?

• type: on all 15 docs, added as the last frontmatter line: eight Specs, three Blueprints, three Issues, one Reminders.
• context-v/index.md: the bundle’s root index, declaring okf_version: "0.2" and listing the four folders.
• An index.md in each folder, one line per doc, using the doc’s lede, or its title alone where it has none.

Under the Hood

• Every edit was made by hand, one doc at a time. No script touched any frontmatter.
• The splash reads context-v/ as a content collection. Its schema is lenient and every field optional, so the new frontmatter-less index.md files load without error. They do appear in the splash’s context-v listing as entries named after their path.
• Part of the tree-wide sweep planned in the context-vigilance kit: ai-labs/context-vigilance-kit/context-v/plans/Retrofit-Every-Repo-to-OKF-Then-the-Kit-Frontmatter.md.