Problem
Company knowledge often sits across scattered local documents, status data, and decisions. AI answers are only useful when search scope, sources, permissions, and evidence status are correct.
Solution
BetriebsGehirn starts with the knowledge infrastructure: local source management, parsers, chunking, embeddings, vector index, source status, document store, and separate setup/health states.
Result
A RAG-oriented working state that treats answer quality, source confidence, and honest non-answers as core product concerns.
Technical details and decisions
Technical Architecture
Next.js app with modular core/module/adapter layers, local JSON stores, persistent vector index, optional LLM provider, and API endpoints for knowledge, sources, documents, setup, and health.
Engineering Decisions
- Knowledge infrastructure before chat UI
- Source status, source scope, and evidence assessment as architecture concerns
- Adapters instead of hard-wired providers, databases, or parsers
Demonstrates
RAG architecture, local knowledge processing, retrieval quality, source grounding, and realistic AI boundaries.
Status
Local development project; not a finished SME product and not running customer data.