GKOS-Engine and Kosmos-Oden: governed knowledge tooling
Status: GKOS-Engine release 2.1.1 (18 August 2026); 2.2.0 on main pending release qualification. Kosmos-Oden release 0.8.2 (9 September 2026).
- Problem
- Agents and people need to search and reason over a Markdown knowledge base without a tool silently changing source files or exposing restricted notes.
- My part
- I set the requirements and design, review the changes, run the qualification checks and decide releases. AI coding agents write much of the code under that review.
- Exists now
- A TypeScript library and CLI that parses and validates GKX records, builds canonical graphs, indexes and retrieves notes, and serves ten credential-bound, read-only MCP tools on a local port. Kosmos-Oden uses it to draw a vault as an explorable 3D map in Obsidian or a standalone viewer.
- Results
- Release-status records show CI and Linux and Windows runtime qualification passing for the recorded main baseline. Writes to source notes remain unavailable unless a host explicitly configures and authorizes them.
- Limits
- No published usage or adoption figures. The npm package lags the current source (2.0.1). Implementation independence from GKOS has not been demonstrated.
Evidence GKOS-Engine repository; GKOS-Engine 2.1.1 release; GKOS-Engine release status and verification evidence; Kosmos-Oden repository