Hi, and thanks for building Graphiti. Real time knowledge graphs for agents and RAG are a very nice direction, and the docs are already quite clear.
I am the author of an open source project called WFGY 16 Problem Map. It is a small but dense map of sixteen typical failure modes in RAG and LLM based systems, each with a short description and concrete structural fixes.
Repo: https://github.com/onestardao/WFGY
Problem Map: https://github.com/onestardao/WFGY/tree/main/ProblemMap/README.md
The map focuses on things like retrieval hallucination on top of good context, vector store ingestion and schema mistakes, infra startup races between API and vector DB, missing secrets on first deploy, and similar issues that often show up once a system moves from demo to production.
Suggestion: would you be open to adding WFGY 16 Problem Map as an external reference in your documentation, for example in a “Troubleshooting / RAG reliability / Resources” subsection? It could give Graphiti users a common language when they debug failures in more complex graph plus RAG setups.
If you think this is in scope I can prepare a tiny PR that just adds one link line.
Thanks for considering it.
Hi, and thanks for building Graphiti. Real time knowledge graphs for agents and RAG are a very nice direction, and the docs are already quite clear.
I am the author of an open source project called WFGY 16 Problem Map. It is a small but dense map of sixteen typical failure modes in RAG and LLM based systems, each with a short description and concrete structural fixes.
Repo: https://github.com/onestardao/WFGY
Problem Map: https://github.com/onestardao/WFGY/tree/main/ProblemMap/README.md
The map focuses on things like retrieval hallucination on top of good context, vector store ingestion and schema mistakes, infra startup races between API and vector DB, missing secrets on first deploy, and similar issues that often show up once a system moves from demo to production.
Suggestion: would you be open to adding WFGY 16 Problem Map as an external reference in your documentation, for example in a “Troubleshooting / RAG reliability / Resources” subsection? It could give Graphiti users a common language when they debug failures in more complex graph plus RAG setups.
If you think this is in scope I can prepare a tiny PR that just adds one link line.
Thanks for considering it.