RAGnarok Part 1 — Scoping an Enterprise RAG System (Before Any Code)

Starting a series called RAGnarok — building an Enterprise Knowledge Assistant (RAG system) in public, part by part. This first post is scope/architecture only, no code — that starts in Part 2.

The problem

Internal docs (HR policy, engineering docs, deployment runbooks, incident postmortems, API references) are scattered, and finding the right one is slow. Goal: a retrieval system that answers questions like "how do I rotate AWS credentials?" by pulling from the actual internal docs instead of a person searching manually.

Tech stack

Embeddings: Sentence Transformers

RAGnarok Part 1 — Scoping an Enterprise RAG System (Before Any Code)

Related reading

Anatomy of a Full RAG Application: Every Concept, One Self-Hosted Stack

Why my first RAG system hallucinated (and how I fixed it)

Architecture Breakdown: Building an Enterprise-Grade Legal RAG System (From…

RAG Classifications, Architectures: A Field Guide for Production-Grade Systems

The Access Control Gap That Makes Most Enterprise RAG Systems Dangerous

RAG Pipeline: The Uncle-Nephew Complete Learning Guide