I’ve been building LLM-driven systems for customers for quite some time. We got tired of hallucinations from vector-based and hybrid RAGs last year, eventually arriving to the approach similar to yours.
It is even called Knowledge Mapping [1]. It works really well, and customers can understand it.
Probably the only difference with your approach is that we use different architectural patterns to map domain knowledge into bits of knowledge that LLMs will use to reason (Router, Knowledge Base, Search Scope, Workflows, Assistant etc)
My contacts are in the profile, if you want to bounce ideas!
It is even called Knowledge Mapping [1]. It works really well, and customers can understand it.
Probably the only difference with your approach is that we use different architectural patterns to map domain knowledge into bits of knowledge that LLMs will use to reason (Router, Knowledge Base, Search Scope, Workflows, Assistant etc)
My contacts are in the profile, if you want to bounce ideas!
[1] English article: https://www.trustbit.tech/en/wie-wir-mit-knowledge-maps-bess...