knowledge systems
markdown vaults, retrieval, and evidence beside the code.
the repo is the database. every project here keeps its working knowledge in markdown and git, searchable, diffable, and durable, with indexes treated as replaceable caches rather than the source of truth.
this category is about knowledge systems agents can use: hybrid retrieval, typed relationships, source capture that records where each note came from, and review workflows for notes that agents generate.
lessons
- markdown and git are the database; everything else is a derived indexstart here · the write path is the product
- hybrid retrieval: exact, text, and semantic search togethersubscriber · rank fusion that stays inspectable
- source capture with provenance: a manifest for everything the agent read · chain of custody for web material
- typed relationships vs. wikilinks: what a knowledge graph buys an agent · bounded graph context, not unlimited traversal
projects
- wordcell · a git-backed markdown knowledge base built for coding agents.
- qmd · local search over markdown by exact wording, meaning, or both.
- soulscrape · a dated, revisable working model of a person from authorized sources.
- kb evaluation · the frozen retrieval pilot metrics published beside the vault.
by hraness · drafted with ai assistance