Documentation
Running KIRA
Start with the quick start; it gets you from an unfamiliar repository to a grounded answer in about five minutes. The rest is reference, in the order you tend to need it.
Quick start
Install KIRA, let it propose the areas of your product, extract facts from the code, and ask your first question — in about five minutes, with no database.
Areas: the map of your product
An area is a topic someone asks about, not a directory. How kira init proposes them from your router, and what to fix by hand before extracting anything.
The knowledge format
One fact per file: frontmatter, body, and the fields that make it an in-product assistant — route, requires, sources, provenance, confidence, and eight fact types.
Configuration
Every key in .kira/config.yaml: the assistant's persona and language, source globs, per-stage models and effort, batching limits, and the area map itself.
Command line
kira init, extract, status and ask — every flag, what each command writes, and how to wire extraction into CI so knowledge is reviewed in a pull request.
How a question finds a fact
BM25 with no vector store, a rewrite hop that lets a question cross languages, boosting by the reader's current screen, plan gating, and diversity selection.
The answering contract
What KIRA promises when it replies: retrieved facts as the only source, an honest refusal over a plausible walkthrough, verbatim interface labels, and boundaries first.
Status, roadmap & limits
What v0.1 does today, what the eval loop in v0.2 changes about trusting it, the widget in v0.3 — and the three problems you should weigh before adopting it.