BuchDocs: repository documentation with an AI assistant

The problem

Engineering knowledge scatters. It sits in repositories nobody outside the team reads, in documents that go stale the week after they are written, and in the heads of whoever shipped it. New people pay for that, and so does every handover.

What we built

BuchDocs: a documentation workspace organised by organisation, project and repository, with an assistant that answers questions against the selected codebases and cites the files it used.

How it works

The assistant is grounded rather than generative-by-default: it searches the chosen repositories and an attached knowledge base on every question, and shows its sources so an answer can be checked. Templates turn a single prompt into a full SRS or user manual, which is what turns it from a search box into something that produces deliverables.

How we approached it

The assistant was built grounded from the outset: retrieval over the selected repositories and knowledge base first, generation second, with citations attached to every answer. That order is what makes the output checkable instead of plausible.

What you get

A workspace where documentation is organised by organisation, project and repository, questions get sourced answers, and templates turn a prompt into a full SRS or user manual.