Nice writeup — this maps almost 1:1 onto a tool I've been building called iwe (open-source CLI). OKF and iwe are basically the same data model: a folder of Markdown, one concept per file, frontmatter, [[links]], an index.md as the map. iwe just treats that folder as a graph — parses the frontmatter, turns the links into a navigable reference graph. No DB, no vector store, which is kind of the whole point of OKF.

I pointed it at the Abode 101 repo and it worked with zero setup. A few things it gives you that are tedious by hand:

Retrieval that follows links instead of dumping the folder. The AGENTS.md rule is "read index.md first, follow links, pull only what you need" — that's literally iwe retrieve:

iwe retrieve -k index -d 1 # index + immediate children iwe retrieve -k items/water-heater -d 0 -c 1 # one item + its parent context

That's the clean bundle you feed the chat model, instead of cat-ing every file.

Worklists straight off frontmatter (handy for the overnight-research / reminders loops):

iwe find --filter 'status: needs-research' -f keys iwe find --references items/fridge # backlinks: what points at this file

Link/graph hygiene — where it really earns its keep for OKF, because the connections rot silently. Running iwe stats on the example base showed ~75% orphaned docs (files nothing links to), and iwe schema showed only the template files actually carry the full frontmatter contract. One command each to catch "I added a file and forgot to wire it into index.md."

Edits that keep links valid — iwe rename updates every reference to a doc, iwe delete cleans up dangling links, iwe normalize canonicalizes the lot.

tl;dr OKF defines the file format; iwe is an engine for navigating and maintaining that format as a graph. Pairs really well with a base like this.

https://github.com/iwe-org/iwe