mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-26 10:40:55 +00:00
110 lines
8.3 KiB
Markdown
110 lines
8.3 KiB
Markdown
<!--
|
|
AI NOTE · ADOPTERS
|
|
|
|
Purpose:
|
|
* This page is the short public adoption summary for WFGY.
|
|
* It is meant for evaluators, collaborators, and first-time visitors who want the strongest public evidence first.
|
|
* This page is intentionally shorter than the full recognition log.
|
|
|
|
How to read this page:
|
|
* The entries below are the strongest current public examples of WFGY adoption, integration, or research-facing reuse.
|
|
* Most public adoption today points to the WFGY ProblemMap / 16-problem failure checklist line.
|
|
* For the full and continuously maintained ecosystem record, go to recognition/README.md.
|
|
|
|
Important boundary:
|
|
* This is not a customer logo page.
|
|
* This is not an enterprise logo page.
|
|
* This does not claim that every listed project uses the full WFGY ecosystem.
|
|
* Open-source program support, sponsored plans, and infrastructure credits are a separate signal from public adoption.
|
|
* This page is a short summary layer, not the canonical source-of-truth ledger.
|
|
-->
|
|
|
|
# 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:
|
|
|
|
* [WFGY Recognition Map](https://github.com/onestardao/WFGY/blob/main/recognition/README.md)
|
|
|
|
## Open-source support surface
|
|
|
|
> Separate from adoption evidence, WFGY is also supported through selected open-source programs, sponsored plans, and infrastructure credits.
|
|
|
|
<p align="center">
|
|
<img width="1536" alt="WFGY Trust Wall" src="https://github.com/user-attachments/assets/28e47e15-e287-4e7b-b0f5-4f3b4dfed178" />
|
|
</p>
|
|
|
|
> This support surface should not be read as the same thing as adoption.
|
|
> It is a parallel trust signal, not a substitute for the adoption evidence below.
|
|
|
|
---
|
|
|
|
## 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 | How it uses WFGY ProblemMap | Proof (PR / doc) |
|
|
| --- | --- | --- | --- | --- |
|
|
| [LlamaIndex](https://github.com/run-llama/llama_index) | [](https://github.com/run-llama/llama_index) | Mainstream RAG infra | Integrates the WFGY 16-problem RAG failure checklist into its official RAG troubleshooting docs as a structured failure mode reference. | [PR #20760](https://github.com/run-llama/llama_index/pull/20760) |
|
|
| [RAGFlow](https://github.com/infiniflow/ragflow) | [](https://github.com/infiniflow/ragflow) | Mainstream RAG engine | Introduced a RAG failure modes checklist guide to the RAGFlow documentation via PR, adapted from the WFGY 16-problem failure map for step-by-step RAG pipeline diagnostics. | [PR #13204](https://github.com/infiniflow/ragflow/pull/13204) |
|
|
| [FlashRAG (RUC NLPIR Lab)](https://github.com/RUC-NLPIR/FlashRAG) | [](https://github.com/RUC-NLPIR/FlashRAG) | Academic lab / RAG research toolkit | Adapts the **WFGY ProblemMap** as a structured RAG failure checklist in its documentation. The 16-mode taxonomy is cited to support reproducible debugging and systematic failure-mode reasoning for RAG experiments. | [PR #224](https://github.com/RUC-NLPIR/FlashRAG/pull/224) |
|
|
| [DeepAgent (RUC NLPIR Lab)](https://github.com/RUC-NLPIR/DeepAgent) | [](https://github.com/RUC-NLPIR/DeepAgent) | Academic lab / agent research | Adds a **multi-tool agent failure modes troubleshooting note** inspired by WFGY-style debugging concepts for diagnosing tool selection loops, tool misuse, and multi-tool workflow failures in agent pipelines. | [PR #15](https://github.com/RUC-NLPIR/DeepAgent/pull/15#issuecomment-4020600680) |
|
|
| [ToolUniverse (Harvard MIMS Lab)](https://github.com/mims-harvard/ToolUniverse) | [](https://github.com/mims-harvard/ToolUniverse) | Academic lab / tools | Provides a `WFGY_triage_llm_rag_failure` tool that wraps the 16 mode map for incident triage. | [PR #75](https://github.com/mims-harvard/ToolUniverse/pull/75) |
|
|
| [Rankify (University of Innsbruck)](https://github.com/DataScienceUIBK/Rankify) | [](https://github.com/DataScienceUIBK/Rankify) | Academic lab / system | Uses the 16 failure patterns in RAG and re-ranking troubleshooting docs. | [PR #76](https://github.com/DataScienceUIBK/Rankify/pull/76) |
|
|
| [Multimodal RAG Survey (QCRI LLM Lab)](https://github.com/llm-lab-org/Multimodal-RAG-Survey) | [](https://github.com/llm-lab-org/Multimodal-RAG-Survey) | Academic lab / survey | Cites WFGY as a practical diagnostic resource for multimodal RAG. | [PR #4](https://github.com/llm-lab-org/Multimodal-RAG-Survey/pull/4) |
|
|
| [LightAgent](https://github.com/wanxingai/LightAgent) | [](https://github.com/wanxingai/LightAgent) | Agent framework | Incorporates WFGY ProblemMap concepts into its documentation via a **Multi-agent troubleshooting (failure map)** section, providing a structured symptom → failure-mode → debugging checklist for diagnosing role drift, cross-agent memory issues, and coordination failures in multi-agent systems. | [PR #24](https://github.com/wanxingai/LightAgent/pull/24#event-23265428525) |
|
|
| [OmniRoute](https://github.com/diegosouzapw/OmniRoute) |  | Gateway / routing infra | Adds an optional WFGY 16-problem RAG / LLM failure taxonomy to its official troubleshooting documentation, allowing teams to classify downstream RAG and agent failures with `No.1` to `No.16` alongside OmniRoute logs when the gateway itself appears healthy. | [PR #164](https://github.com/diegosouzapw/OmniRoute/pull/164) |
|
|
|
|
## 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
|
|
* open-source program support is real, but it is a separate signal from adoption
|
|
* 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
|
|
* every support logo implies adoption of the WFGY stack
|
|
|
|
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:
|
|
|
|
* [WFGY Recognition Map](https://github.com/onestardao/WFGY/blob/main/recognition/README.md)
|
|
|
|
<details>
|
|
<summary><strong> Related pages </strong></summary>
|
|
|
|
<br/>
|
|
|
|
* [WFGY main repository](https://github.com/onestardao/WFGY)
|
|
* [WFGY Recognition Map](https://github.com/onestardao/WFGY/blob/main/recognition/README.md)
|
|
* [RAG 16 Problem Map](https://github.com/onestardao/WFGY/blob/main/ProblemMap/README.md)
|
|
* [Global Debug Card](https://github.com/onestardao/WFGY/blob/main/ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)
|
|
* [Work with WFGY](https://github.com/onestardao/WFGY/blob/main/WORK_WITH_WFGY.md)
|
|
|
|
</details>
|