Metafetch's Plans and Exploration Become a Bundle Any Agent Can Read
The exploration and two plans behind Metafetch's profiles and recipes now say what they are, and each folder gets an index an agent can scan.
Metafetch's Plans and Exploration Become a Bundle Any Agent Can Read
Why Care?
metafetch/context-v/ holds the thinking behind Metafetch's folder profiles and fetch recipes: the exploration that split the work into profiles, recipes, and command kinds, and the two plans that built 0.2.0 and slice 1. Until today an agent had to open each file to learn what kind of doc it was. Now the folder is an Open Knowledge Format (OKF) v0.2 bundle, so any OKF reader can list what's here and what each doc is for without opening a thing.
What's New?
All 3 docs declare their
type, the Train-Case name of the folder they live in:ExplorationsandPlans.context-v/index.mdmarks the bundle withokf_version: "0.2"and lists its two folders.Two folder indexes, one line per doc with its lede.
Under the Hood
Part of the tree-wide OKF sweep; see the Context Vigilance Kit's plan, [[Retrofit-Every-Repo-to-OKF-Then-the-Kit-Frontmatter]].
Every edit was made by hand, one file at a time. The doc diff is 3 added
type:lines and nothing removed. No dates moved: this is a compliance change, not a content change.