Hi, thanks for curating this RAG tutorial list.
I wanted to ask whether an advanced failure mode taxonomy and debugging guide for RAG systems would be in scope as an additional resource.
What WFGY Problem Map is
WFGY is an open source project that defines a 16 mode failure map (No.1 to No.16) for LLM plus RAG pipelines. The modes include:
retrieval hallucination even when relevant evidence is present
vector store ingestion and index fragmentation
bootstrap ordering and infra race conditions between API gateway and vector DB
secrets and config drift only visible on first production deploy
and other quietly dangerous failure modes
Problem Map README:
https://github.com/onestardao/WFGY/tree/main/ProblemMap#readme
For each mode, there is a description, typical symptoms and suggested minimal countermeasures.
Why it might complement the tutorials
Most tutorials show how to get a RAG demo running. The Problem Map focuses on what goes wrong after that and how to systematically debug it. It can be used as:
a checklist for people who have followed the tutorials and hit strange bugs
a structure for documenting incidents in production RAG apps
a vocabulary to teach newcomers about RAG failure modes
Possible entry
If you think this fits the scope, one possible entry under an “Advanced / debugging” section could be:
WFGY 16 Problem Map – RAG failure mode taxonomy and debugging guide
Open source map of 16 real world failure modes (No.1 to No.16) for LLM plus RAG systems, with debugging checklists and mitigation ideas.
https://github.com/onestardao/WFGY/tree/main/ProblemMap#readme
If this feels out of scope for the repo, no worries and thanks for taking a look.
Hi, thanks for curating this RAG tutorial list.
I wanted to ask whether an advanced failure mode taxonomy and debugging guide for RAG systems would be in scope as an additional resource.
What WFGY Problem Map is
WFGY is an open source project that defines a 16 mode failure map (No.1 to No.16) for LLM plus RAG pipelines. The modes include:
retrieval hallucination even when relevant evidence is present
vector store ingestion and index fragmentation
bootstrap ordering and infra race conditions between API gateway and vector DB
secrets and config drift only visible on first production deploy
and other quietly dangerous failure modes
Problem Map README:
https://github.com/onestardao/WFGY/tree/main/ProblemMap#readme
For each mode, there is a description, typical symptoms and suggested minimal countermeasures.
Why it might complement the tutorials
Most tutorials show how to get a RAG demo running. The Problem Map focuses on what goes wrong after that and how to systematically debug it. It can be used as:
a checklist for people who have followed the tutorials and hit strange bugs
a structure for documenting incidents in production RAG apps
a vocabulary to teach newcomers about RAG failure modes
Possible entry
If you think this fits the scope, one possible entry under an “Advanced / debugging” section could be:
WFGY 16 Problem Map – RAG failure mode taxonomy and debugging guide
Open source map of 16 real world failure modes (No.1 to No.16) for LLM plus RAG systems, with debugging checklists and mitigation ideas.
https://github.com/onestardao/WFGY/tree/main/ProblemMap#readme
If this feels out of scope for the repo, no worries and thanks for taking a look.