KYB
Git-backed infrastructure knowledge base for engineering teams and AI agents.
The problem
An agent starting a new session needs the current service configuration and the reasoning behind it. KYB stores verified notes, incidents and tasks as Markdown with Git history, so another session can retrieve both a current answer and earlier versions.
Example uses
01. Service handover
Record verified service changes so the next person or agent can continue the work with current context.
02. Postmortem history
Inspect historical configuration while investigating an incident or postmortem.
03. Incident resolution
Close an incident with a searchable resolution for later operational work.
Where it fits
KYB keeps operational notes and their history in Git. Its search index can be rebuilt from that history; optional local embeddings complement lexical search. It stores knowledge and incident resolutions, rather than executing code like prod-code.
Get started
Configure a Git-backed server, then install the CLI and connect agents. Semantic search uses an optional local model; BM25 works without it.
Authoritative installation steps, architecture diagrams, and full configuration references are maintained in the repository:
Read the KYB README on GitHub →
Limitations
- Usefulness depends on humans or agents recording verified changes.
- An optional local model is needed for semantic search.
- Notes are not live monitoring.
Cite this software
Alexander Panasenko (2026). KYB: Git-backed infrastructure knowledge base for engineering teams and AI agents (v0.2.3). Zenodo. https://doi.org/10.5281/zenodo.23027682This record reflects the archived software version deposited on Zenodo for citation and reproducibility, which may differ from subsequent development releases.
