agentic developer documentation knowledge base
Drop library docs, changelogs, and RFCs in.
Agents extract APIs, breaking changes, and patterns —
linking libraries and concepts into a searchable reference.
github.com/drader/docvault
They live in a 3,000-word changelog. You read the highlights. The breaking part wasn't highlighted.
API notes in one doc, gotchas in a Stack Overflow tab, migration guide in a Notion page nobody updates.
Your notes say v3. The library is on v5. You don't know that until something breaks in production.
Three libraries solved the same problem three different ways. You implement it a fourth time.
docvault solves all four.
Changelogs are written for humans skimming on release day. Breaking changes get one line between two feature announcements. By the time you hit the runtime error, you've forgotten you even read the changelog. Post-mortem always says: "it was in the changelog."
Every ingest explicitly extracts breaking changes into a ⚠ BREAKING block at the top of the changelog page — never in prose, always structured. The library's version history table is updated automatically. Run /query "what broke in react 19" and get a direct answer with citations.
Every library in your stack has notes spread across browser bookmarks, Notion docs, team wikis, and your own memory. When a new version ships, nothing updates automatically. You discover staleness when the old API throws at runtime.
wiki/libraries/react.md is the single source of truth — current version, key APIs, gotchas, migration notes, and a full version history table. Every new changelog updates it automatically. When the queue is empty, the orchestrator scans for libraries with outdated entries and flags them in the journal.
Optimistic UI appears in React docs, SWR docs, and TanStack Query docs. Each explains it from their own angle. You learn it three times and never build a mental model that transcends any single library.
Any design pattern demonstrated in a doc gets its own page in wiki/patterns/, linked from every library that uses it. Concept pages in wiki/concepts/ capture the cross-library idea. The Monday orchestrator writes synthesis pages when the same pattern appears across multiple libraries.
MCP hybrid search (BM25 + vector + RRF) over the full wiki.
Breaking changes always explicit. Library knowledge always consolidated.