6 KiB
ADOPTERS
Short public adoption summary for WFGY.
This page highlights the strongest current public examples of where WFGY has already been integrated, adapted, cited, or wrapped in the open ecosystem.
It is not a customer list, not an enterprise logo page, and not a claim that every listed project uses the full WFGY ecosystem.
At the current stage, the clearest public adoption is concentrated around the WFGY ProblemMap / 16-problem failure checklist line.
For the full and continuously maintained recognition log, see:
Strongest current public adoption examples
These are the strongest public examples because they involve one or more of the following:
- merged documentation integrations
- direct tool wrapping
- official troubleshooting references
- research-facing citation or adaptation
- structured reuse of the WFGY ProblemMap
| Project | Stars | Segment | What is publicly visible | Proof |
|---|---|---|---|---|
| RAGFlow | Mainstream RAG engine | RAG troubleshooting material adapted from the WFGY 16-problem failure map for structured pipeline diagnostics. | PR #13204 | |
| LlamaIndex | Mainstream RAG infra | Official troubleshooting docs integrate the WFGY 16-problem checklist as a structured failure reference. | PR #20760 | |
| FlashRAG | Academic lab / RAG research toolkit | Documentation adapts the WFGY ProblemMap as a structured RAG failure checklist for reproducible debugging. | PR #224 | |
| ToolUniverse (Harvard MIMS Lab) | Academic lab / tools | Includes a WFGY_triage_llm_rag_failure tool that wraps the 16-mode map for incident triage. |
PR #75 | |
| LightAgent | Agent framework | Documentation includes a multi-agent troubleshooting section built around WFGY-style failure mapping. | PR #24 | |
| Rankify (Univ. of Innsbruck) | Academic lab / system | Uses the 16 failure patterns in RAG and re-ranking troubleshooting docs. | PR #76 | |
| Multimodal RAG Survey (QCRI LLM Lab) | Academic lab / survey | Publicly cites WFGY as a practical diagnostic resource for multimodal RAG. | PR #4 |
What this page means
The safest reading is:
- WFGY already has real public ecosystem traction
- the strongest traction today is around the ProblemMap line
- WFGY is most visible as a diagnostic and debugging layer for RAG and agent systems
- this is stronger than a purely theoretical project, but should not be exaggerated into full enterprise-adoption claims
What this page does not claim
This page does not claim that:
- every listed project is a paid customer
- every listed project uses the full WFGY ecosystem
- every listed project has deployed WFGY in production
- every public reference implies endorsement of all WFGY directions
This page is intentionally narrow: it shows the strongest public adoption evidence first.
Need the full list?
For the full, continuously maintained ecosystem record, including broader curated lists, discussions, and weaker-but-still-useful public mentions, go to: