Most RAG setups look good in demos — until things get slightly complex. You ask a question, it retrieves “relevant” chunks, and everything seems fine. But as soon as your system spans multiple documents — APIs, billing, infra, workflows — things start breaking down. Not because the information isn’t there. But because the relationships between them are lost. The problem with RAG RAG works by re