WFGY/CASE_EVIDENCE.md

<!--
AI NOTE · CASE_EVIDENCE

Purpose
- Translate public adoption evidence into capability signals.
- This page interprets what external integrations and citations suggest
  about where WFGY is useful in practice.

How this page differs from others
- ADOPTERS.md = short public adoption summary
- recognition/README.md = full ecosystem ledger
- CASE_EVIDENCE.md = interpretation of what the strongest cases mean

Boundary
- Do not overstate adoption.
- Do not imply paid customer relationships.
- Treat integrations as ecosystem signals, not endorsements.
-->

# CASE_EVIDENCE

This page interprets what the strongest public WFGY integrations and references **mean in practice**.

It does not duplicate the adoption list, and it does not attempt to track every mention.

Instead, it answers a more practical question:

**When external frameworks, labs, or research toolkits integrate or cite WFGY, what does that suggest about WFGY's role and usefulness?**

For the short adoption summary see  
[ADOPTERS.md](https://github.com/onestardao/WFGY/blob/main/ADOPTERS.md)

For the full ecosystem record see  
[WFGY Recognition Map](https://github.com/onestardao/WFGY/blob/main/recognition/README.md)

---

# Reading the ecosystem signals

Across current public evidence, the pattern is consistent.

The most visible adoption wedge today is:

**WFGY ProblemMap · the 16-problem failure map for RAG and agent systems**

In most cases, WFGY appears as a **diagnostic layer** rather than a full system component.

Teams use it to:

- classify failure patterns
- structure debugging workflows
- reduce ambiguity when RAG or agent systems behave unpredictably
- turn symptoms into actionable debugging steps

The following cases illustrate how that pattern appears across different parts of the ecosystem.

---

# Case 1 · RAGFlow

## Context

[RAGFlow](https://github.com/infiniflow/ragflow) is a production-oriented RAG framework focused on real pipeline deployments.

Frameworks at this layer care about practical debugging guidance because real systems often fail in ways that are difficult to diagnose.

## Where WFGY fit

A troubleshooting guide derived from the **WFGY 16-problem failure map** was previously merged into the RAGFlow repository to support structured RAG pipeline diagnostics.

The goal was to give developers a clear checklist of failure categories rather than leaving debugging entirely ad-hoc.

## Public proof

[RAGFlow PR #13204](https://github.com/infiniflow/ragflow/pull/13204)

## What this suggests

The merge record shows that WFGY's failure-mode structure was considered useful enough to be integrated into documentation for a mainstream RAG framework.

This indicates that WFGY is legible as a **practical debugging structure** rather than only a conceptual framework.

## Important boundary

Open-source documentation evolves over time.

This case is included as a **public merge record demonstrating ecosystem interaction**, not as a claim that the documentation placement is permanent.

---

# Case 2 · LlamaIndex

## Context

[LlamaIndex](https://github.com/run-llama/llama_index) is one of the most widely used infrastructure frameworks for RAG and agent systems.

Documentation patterns in this ecosystem strongly influence how developers reason about system failures.

## Where WFGY fit

The **WFGY 16-problem failure checklist** was integrated into LlamaIndex troubleshooting documentation as a structured failure taxonomy.

This provides developers with a systematic way to interpret symptoms such as:

- hallucinated answers
- empty retrieval results
- unstable agent responses
- inconsistent knowledge grounding

## Public proof

[LlamaIndex PR #20760](https://github.com/run-llama/llama_index/pull/20760)

## What this suggests

This case shows that WFGY can function as a **framework-agnostic debugging reference**.

The ProblemMap is not tied to a specific runtime stack.  
Instead it acts as a conceptual structure for diagnosing failures across different RAG implementations.

## Important boundary

This integration demonstrates documentation-level adoption rather than full system embedding.

---

# Case 3 · FlashRAG

## Context

[FlashRAG](https://github.com/RUC-NLPIR/FlashRAG) is a research-oriented RAG toolkit designed for experimentation and evaluation.

In research settings, debugging structures must support **reproducibility** rather than only practical troubleshooting.

## Where WFGY fit

FlashRAG documentation references the **WFGY ProblemMap** as a structured checklist for RAG failure analysis.

The taxonomy helps researchers reason about failure causes when evaluating retrieval pipelines.

## Public proof

[FlashRAG PR #224](https://github.com/RUC-NLPIR/FlashRAG/pull/224)

## What this suggests

This case shows that WFGY is useful not only in engineering operations but also in **research-side evaluation workflows**.

The ProblemMap can act as a bridge between experimentation and debugging.

## Important boundary

Research citation does not imply benchmark status or universal adoption.

It demonstrates that the framework is useful enough to be referenced in structured evaluation contexts.

---

# Case 4 · ToolUniverse

## Context

[ToolUniverse](https://github.com/mims-harvard/ToolUniverse) is an academic-lab project exploring tool ecosystems for LLM systems.

Unlike documentation references, this project exposed a **tool interface** around WFGY triage logic.

## Where WFGY fit

ToolUniverse includes a `WFGY_triage_llm_rag_failure` utility that wraps the failure map as an incident triage tool.

This shifts WFGY from a static checklist into a **tool-level diagnostic mechanism**.

## Public proof

[ToolUniverse PR #75](https://github.com/mims-harvard/ToolUniverse/pull/75)

## What this suggests

This suggests that the WFGY failure map is structured enough to be operationalized as tooling rather than remaining documentation.

It indicates potential for WFGY concepts to serve as **diagnostic infrastructure**.

## Important boundary

This example shows conceptual wrapping rather than production deployment.

---

# Case 5 · LightAgent

## Context

[LightAgent](https://github.com/wanxingai/LightAgent) is an agent framework where system failures often emerge from coordination problems rather than simple retrieval issues.

Examples include:

- role drift between agents
- inconsistent shared memory
- coordination loops
- incorrect task decomposition

## Where WFGY fit

The documentation includes a troubleshooting section inspired by WFGY-style failure mapping.

This applies the ProblemMap approach to **multi-agent coordination failures**.

## Public proof

[LightAgent PR #24](https://github.com/wanxingai/LightAgent/pull/24)

## What this suggests

This shows that WFGY-style structured debugging is not limited to RAG pipelines.

It can also help interpret failures in **agent orchestration systems**.

## Important boundary

The agent domain introduces new classes of failure beyond the original map.

This example demonstrates conceptual portability rather than full domain coverage.

---

# Case 6 · Rankify

## Context

[Rankify](https://github.com/DataScienceUIBK/Rankify) focuses on ranking and reranking pipelines for retrieval systems.

Failures in these pipelines are often subtle and difficult to categorize.

## Where WFGY fit

Rankify troubleshooting documentation references the **16-problem failure patterns** as a way to interpret common pipeline breakdowns.

## Public proof

[Rankify PR #76](https://github.com/DataScienceUIBK/Rankify/pull/76)

## What this suggests

This case indicates that the WFGY diagnostic framing can remain useful even when the system boundary shifts from retrieval to ranking-heavy workflows.

## Important boundary

This demonstrates conceptual reuse rather than domain-specific specialization.

---

# Case 7 · Multimodal RAG Survey

## Context

Survey repositories help shape how the field organizes knowledge.

Inclusion in a survey indicates that a resource has become visible enough to be referenced by researchers.

## Where WFGY fit

The survey cites WFGY as a practical diagnostic resource for multimodal RAG systems.

## Public proof

[Multimodal RAG Survey PR #4](https://github.com/llm-lab-org/Multimodal-RAG-Survey/pull/4)

## What this suggests

This indicates that WFGY has begun to appear as a **field-level reference point** for debugging and failure analysis.

## Important boundary

Survey citation is weaker evidence than direct integration.

It shows recognition rather than operational use.

---

# Cross-case interpretation

Taken together, these cases suggest a consistent pattern.

## The strongest adoption wedge is the ProblemMap

The WFGY ProblemMap is currently the most visible and reusable component of the ecosystem.

## WFGY functions primarily as a diagnostic layer

Across integrations, the most common role is:

- debugging structure
- failure taxonomy
- triage framework
- troubleshooting reference

## The framework has crossed the “pure idea” stage

WFGY now appears in:

- official documentation
- academic tools
- research toolkits
- curated ecosystem lists

This indicates meaningful ecosystem interaction.

## Frontier components are still earlier

The **WFGY 3.0 tension reasoning engine** has visibility but currently has fewer public integration signals than the diagnostic layer.

This is expected for frontier research infrastructure.

---

# What this means for teams evaluating WFGY

A realistic interpretation is:

- WFGY already has visible ecosystem traction
- the most mature interface today is the **diagnostic framework**
- the frontier reasoning components are still emerging

This combination provides a practical entry point for teams that need structured debugging for complex AI systems.

---

# Related pages

Short adoption summary  
[ADOPTERS.md](https://github.com/onestardao/WFGY/blob/main/ADOPTERS.md)

Full ecosystem recognition log  
[WFGY Recognition Map](https://github.com/onestardao/WFGY/blob/main/recognition/README.md)

Collaboration and ecosystem participation  
[WORK_WITH_WFGY.md](https://github.com/onestardao/WFGY/blob/main/WORK_WITH_WFGY.md)

RAG failure taxonomy  
[RAG 16 Problem Map](https://github.com/onestardao/WFGY/blob/main/ProblemMap/README.md)

Global debugging card  
[Global Debug Card](https://github.com/onestardao/WFGY/blob/main/ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)