knowledge-pro(vider)

Two axes that cross-reference each other. Portable technical knowledge is owned here: several hundred notes, each tagged with a slash path, marked personal (learned from our own work) or collected (absorbed from an upstream source, and only as current as the version it came from). Projects are stubs that point outward: path, stack, one paragraph, and where to read more in the repo. Pointers, not copies, because a copy goes stale silently. The axes join on tags, so working in a Python and MCP project resolves to the Python and MCP gotchas as a lookup, not a guess.

Agents reach it over MCP and get a slice, never the whole index. Writes pass a gate that refuses claims which are not portable, correct, non-obvious and durable. Every note carries an outcome record of whether it helped or was wrong, so trust rests on evidence and pruning is possible. Journaling is a tool call rather than a file, so project history never lands in a repository that might one day be public.