WFGY/EVIDENCE_TIMELINE.md

<a id="top"></a>

# EVIDENCE_TIMELINE

Historical evidence timeline for WFGY.

This page records how WFGY became real, usable, public, and externally legible over time.

WFGY did not begin with a large installed base, a built-in distribution channel, or a ready-made institutional wrapper.  
It was built in public, piece by piece, through theory, application surfaces, diagnostic maps, teaching layers, evaluation artifacts, and eventually public ecosystem proof.

You can read this page as a compact historical route:

**cold start → structure → teaching → evaluation → public proof**

## Quick navigation

- [What this page is](#what-this-page-is)
- [What this page is not](#what-this-page-is-not)
- [Timeline](#timeline)
  - [Cold Start Era](#cold-start-era)
  - [Diagnostic Wedge Era](#diagnostic-wedge-era)
  - [Expansion Era](#expansion-era)
  - [Public Proof Era](#public-proof-era)
- [What this timeline currently shows](#what-this-timeline-currently-shows)
- [Maintenance rules](#maintenance-rules)
- [Related pages](#related-pages)

## Related pages

Core proof and interpretation:

* [ADOPTERS](./ADOPTERS.md)
* [CASE_EVIDENCE](./CASE_EVIDENCE.md)
* [Recognition Map](./recognition/README.md)

Collaboration and next-layer packaging:

* [Work with WFGY](./WORK_WITH_WFGY.md)
* [Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md)
* [Sample Deliverable](./SAMPLE_DELIVERABLE.md)

Structure and reference:

* [Ecosystem Map](./ECOSYSTEM_MAP.md)
* [Problem Map 1.0](./ProblemMap/README.md)
* [Repository Citation Metadata](./CITATION.cff)

---

<a id="what-this-page-is"></a>

## What this page is

This page is a **chronological evidence record**.

It combines three kinds of milestones:

1. **WFGY internal milestones**  
   when a core module, map, framework, or teaching surface became public

2. **Public ecosystem milestones**  
   when an external project, survey, or tool publicly integrated, cited, adapted, or reused WFGY ideas

3. **Packaging milestones**  
   when WFGY itself became easier to audit, route, reuse, or evaluate from the outside

This page sits between two other proof surfaces:

* [ADOPTERS](./ADOPTERS.md), which gives the shortest high-signal summary
* [Recognition Map](./recognition/README.md), which remains the broader ecosystem ledger

It also supports the interpretation layer in [CASE_EVIDENCE](./CASE_EVIDENCE.md).

---

<a id="what-this-page-is-not"></a>

## What this page is not

This page is not:

* a customer logo wall
* a revenue timeline
* a complete archive of every mention
* a promise that every external event means production deployment
* a claim that every milestone has equal weight

For the shortest high-signal summary, use [ADOPTERS](./ADOPTERS.md).  
For the broader ledger, use the [Recognition Map](./recognition/README.md).  
For cross-case interpretation, use [CASE_EVIDENCE](./CASE_EVIDENCE.md).

---

<a id="timeline"></a>

# Timeline

<a id="cold-start-era"></a>

## Cold Start Era

The earliest phase of WFGY was a cold-start build.  
This period matters because it shows the stack did not begin as a polished ecosystem surface. It began as a public baseline, then slowly gained structure.

### 2025/06/15 · WFGY 1.0 becomes the baseline public reference

**Track**  
Internal milestone

**What became public**  
[WFGY 1.0](https://github.com/onestardao/WFGY/) established the project home and the earliest baseline reference for the WFGY line.

**Why this matters**  
This is the starting point of the public WFGY stack.  
It marks the moment when the project stopped being private intuition and became a public reference surface.

### 2025/07/02 · TXTOS opens the application layer

**Track**  
Internal milestone

**What became public**  
[TXTOS](https://github.com/onestardao/WFGY/blob/main/OS/README.md) introduced a text-native reasoning OS layer with modules and runtime-oriented structure.

**Why this matters**  
This widened WFGY from theory into application surfaces.  
It showed that the project was not only about concepts, but also about structured usage.

### 2025/07/15 · Blah Blah Blah extends the TXTOS stack

**Track**  
Internal milestone

**What became public**  
[TXT: Blah Blah Blah](https://github.com/onestardao/WFGY/blob/main/OS/BlahBlahBlah/README.md) appeared as an embedding and semantics-related submodule integrated with TXTOS.

**Why this matters**  
This is one of the earlier signs that WFGY was growing as a family of connected modules rather than a single page or one-off idea.

[Back to top](#top)

---

<a id="diagnostic-wedge-era"></a>

## Diagnostic Wedge Era

This is the phase where WFGY became much easier for outside teams to understand.  
The project gained a practical wedge, especially through structured failure diagnosis and teaching surfaces.

### 2025/07/28 · Problem Map 1.0 becomes the practical wedge

**Track**  
Internal milestone

**What became public**  
[Problem Map 1.0](https://github.com/onestardao/WFGY/blob/main/ProblemMap/README.md) published the original 16-mode diagnostic map for failure modes and fixes.

**Why this matters**  
This is one of the most important turning points in the whole timeline.  
It gave WFGY a practical front door that real RAG and agent teams could understand quickly.

### 2025/07/28 · Semantic Clinic expands the teaching layer

**Track**  
Internal milestone

**What became public**  
[Semantic Clinic](https://github.com/onestardao/WFGY/blob/main/ProblemMap/SemanticClinicIndex.md) added a structured teaching surface for injection, memory bugs, drift patterns, triage, and treatment.

**Why this matters**  
It showed that WFGY was not only classifying failures, but also teaching people how to reason about them.

### 2025/07/30 · Semantic Blueprint deepens the theory layer

**Track**  
Internal milestone

**What became public**  
[Semantic Blueprint](https://github.com/onestardao/WFGY/blob/main/SemanticBlueprint/README.md) introduced a layer-based symbolic reasoning blueprint and semantic modulation notes.

**Why this matters**  
This strengthened the internal architecture story behind the public-facing maps and teaching pages.

### 2025/09/05 · Global Fix Map extends beyond one checklist

**Track**  
Internal milestone

**What became public**  
[Global Fix Map](https://github.com/onestardao/WFGY/blob/main/ProblemMap/GlobalFixMap/README.md) expanded the system into cross-tool guardrails and fix patterns for VectorDBs, agents, embeddings, dev tools, and more.

**Why this matters**  
This is where the scope clearly widened from a single 16-problem entry map into a broader systems-facing fix library.

### 2025/09/14 · Grandma Clinic turns the map into memory-friendly teaching

**Track**  
Internal milestone

**What became public**  
[Your Grandma Knows the 16 AI Bugs](https://github.com/onestardao/WFGY/tree/main/ProblemMap/GrandmaClinic) translated the 16 failure modes into everyday analogies and teaching-friendly narratives.

**Why this matters**  
This made the WFGY diagnostic layer more memorable and easier to teach beyond narrowly technical audiences.

**Related layer**  
For the broader diagnostic line, see [Problem Map 1.0](./ProblemMap/README.md) and the future-facing structure in [Ecosystem Map](./ECOSYSTEM_MAP.md).

[Back to top](#top)

---

<a id="expansion-era"></a>

## Expansion Era

This phase matters because WFGY stopped being only a diagnostic and teaching surface.  
It began to open toward broader evaluation and higher-order reasoning layers.

### 2026/01/31 · WFGY 3.0 Singularity Demo opens the frontier evaluation layer

**Track**  
Internal milestone

**What became public**  
[WFGY 3.0 · Singularity Demo](https://github.com/onestardao/WFGY/blob/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt) introduced a reproducible TXT-based entry point for self-evaluation, stress testing, and long-horizon reasoning exploration.

**Why this matters**  
This is a major expansion of the WFGY line.  
It pushed the project from diagnostic and teaching surfaces into a more ambitious evaluation and reasoning arena.

### 2026/03/03 · Problem Map 2.0 Global Debug Card turns the map into image protocol

**Track**  
Internal milestone

**What became public**  
[Problem Map 2.0 Global Debug Card](https://github.com/onestardao/WFGY/releases/tag/WFGY-Global-Debug-Card) was released as an image-first diagnostic protocol for RAG runs.

**Why this matters**  
This is a major packaging milestone.  
It compressed the WFGY diagnostic line into a faster, more shareable, and more reusable format across platforms and models.

**Related layer**  
This milestone connects naturally to [CASE_EVIDENCE](./CASE_EVIDENCE.md), [ADOPTERS](./ADOPTERS.md), and the future-facing collaboration surface in [Work with WFGY](./WORK_WITH_WFGY.md).

[Back to top](#top)

---

<a id="public-proof-era"></a>

## Public Proof Era

This is the phase where outside projects began to make the signal legible in public.  
It does not mean universal adoption. It does mean the WFGY wedge became harder to ignore.

### 2026/02/17 · ToolUniverse shows tool-level public integration

**Track**  
Public ecosystem milestone

**What became public**  
ToolUniverse publicly merged a WFGY-related triage surface through [PR #75](https://github.com/mims-harvard/ToolUniverse/pull/75).

**Why this matters**  
This is stronger than a loose mention.  
It suggests that WFGY could be wrapped into an actionable tool pathway, not only cited as an idea.

### 2026/02/20 · Rankify and Multimodal RAG Survey widen the external signal

**Track**  
Public ecosystem milestone

**What became public**  
[Rankify PR #76](https://github.com/DataScienceUIBK/Rankify/pull/76) added WFGY-style structured troubleshooting into docs.  
[Multimodal RAG Survey PR #4](https://github.com/llm-lab-org/Multimodal-RAG-Survey/pull/4) added WFGY as a robustness-oriented resource.

**Why this matters**  
This date matters because the signal diversified.  
WFGY was no longer visible in only one style of external context.  
It was starting to appear across both practical docs and research-facing material.

### 2026/02/23 · LlamaIndex makes the wedge more mainstream

**Track**  
Public ecosystem milestone

**What became public**  
[LlamaIndex PR #20760](https://github.com/run-llama/llama_index/pull/20760) merged a WFGY-style advanced failure checklist into docs.

**Why this matters**  
This is one of the clearest mainstream ecosystem signals in the timeline.  
It shows that structured WFGY-style failure mapping is legible inside a major public RAG stack.

### 2026/02/25 · RAGFlow strengthens the operational debugging signal

**Track**  
Public ecosystem milestone

**What became public**  
[RAGFlow PR #13204](https://github.com/infiniflow/ragflow/pull/13204) merged a structured RAG failure modes guide adapted from the WFGY Problem Map line.

**Why this matters**  
This strongly reinforces the practical wedge of WFGY.  
It shows the map is useful in operational debugging contexts, not only in teaching or theory.

### 2026/03/01 · FlashRAG reinforces cross-stack reuse

**Track**  
Public ecosystem milestone

**What became public**  
[FlashRAG PR #224](https://github.com/RUC-NLPIR/FlashRAG/pull/224) merged a public debug checklist and failure-mode-oriented surface.

**Why this matters**  
By this point, the pattern is harder to dismiss as an isolated one-off.  
The same wedge is being adapted across multiple public stacks.

### 2026/03/04 · LightAgent extends the signal into multi-agent territory

**Track**  
Public ecosystem milestone

**What became public**  
[LightAgent PR #24](https://github.com/wanxingai/LightAgent/pull/24) merged a multi-agent failure map entry with WFGY-related linkage.

**Why this matters**  
This matters because it widened the visible wedge beyond classic RAG debugging and into multi-agent coordination and failure diagnosis.

### 2026/03/08 · Public proof becomes a first-class routing layer in WFGY

**Track**  
Packaging milestone

**What became public**  
The main [WFGY homepage](https://github.com/onestardao/WFGY/blob/main/README.md) now routes users through a distinct public-proof layer:

* [ADOPTERS](./ADOPTERS.md)
* [CASE_EVIDENCE](./CASE_EVIDENCE.md)
* [Recognition Map](./recognition/README.md)

It also exposes a dedicated collaboration entry through [Work with WFGY](./WORK_WITH_WFGY.md).

**Why this matters**  
This does not create new third-party proof by itself.  
What it does is make the accumulated evidence auditable, legible, and much easier to evaluate in one pass.

**Related layer**  
This stage naturally leads into [Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md) and [Sample Deliverable](./SAMPLE_DELIVERABLE.md), where public proof can later connect to a more structured collaboration surface.

### 2026/03/09 · DeepAgent and awesome-ai-ml-dl widen the post-RAG signal

**Track**  
Public ecosystem milestone

**What became public**  
[DeepAgent PR #15](https://github.com/RUC-NLPIR/DeepAgent/pull/15#issuecomment-4020600680) merged a compact multi-tool agent failure modes troubleshooting note inspired by WFGY-style debugging concepts.  
[awesome-ai-ml-dl PR #163](https://github.com/neomatrix369/awesome-ai-ml-dl/pull/163) added the WFGY Problem Map under Testing & Quality as a structured troubleshooting resource.

**Why this matters**  
This date matters because the signal widened in two different directions at once.  
One direction was deeper agent-workflow diagnosis in an academic research setting.  
The other was broader discoverability through a curated AI and machine learning resource list.

Together, these events suggest that WFGY had become legible not only as a RAG debugging checklist, but also as a reusable troubleshooting concept and a recognizable public reference.

### 2026/03/10 · Awesome-LLM-RAG-Application strengthens discoverability in the RAG tool layer

**Track**  
Public ecosystem milestone

**What became public**  
[Awesome-LLM-RAG-Application PR #9](https://github.com/lizhe2004/Awesome-LLM-RAG-Application/pull/9) added the WFGY RAG troubleshooting checklist into a curated list of LLM and RAG frameworks and tools.

**Why this matters**  
This matters because it improves discoverability exactly where many developers look for practical tooling references.  
It reinforces the idea that the WFGY Problem Map is not only interpretable inside documentation, but also legible as a standalone troubleshooting resource in the wider RAG ecosystem.

### 2026/03/11 · everything-claude-code shows community-level troubleshooting adoption

**Track**  
Public ecosystem milestone

**What became public**  
[everything-claude-code PR #373](https://github.com/affaan-m/everything-claude-code/pull/373) merged a comprehensive troubleshooting guide that also **fixes #326**, the earlier issue where the original structured troubleshooting proposal was introduced.

**Why this matters**  
This is an important signal for a different reason than a direct WFGY listing.  
It suggests that WFGY-style structured troubleshooting ideas were legible enough to influence how a much larger developer-facing repository organized memory, context, and agent workflow debugging.

This is weaker evidence than a direct named integration.  
But it is still meaningful as a public ecosystem signal because it shows concept-level adoption in a large and highly visible repository.

### 2026/03/30 · Open-source support surface becomes publicly legible

**Track**  
Packaging milestone

**What became public**  
WFGY publicly exposed a distinct open-source support surface across its proof-facing pages and homepage trust wall, making program-level support and infrastructure backing visible in one place.

The visible support surface now includes:

* GitLab
* Snyk
* Sentry
* 1Password
* DigitalOcean
* Algolia

**Why this matters**  
This does **not** mean these providers adopted the full WFGY stack, deployed it in production, or should be read as public adoption proof.

What it does mean is that WFGY crossed an important legibility threshold.  
Outside observers can now see that the project is not only accumulating integrations and citations, but is also receiving a recognizable layer of open-source program support, sponsored access, and infrastructure backing.

This matters because it strengthens the external trust surface of the project without collapsing the boundary between **support** and **adoption**.

**Related layer**  
This milestone should be read together with the trust surface shown in [ADOPTERS](./ADOPTERS.md), the broader ledger in [Recognition Map](./recognition/README.md), and the homepage packaging in [README](./README.md).

[Back to top](#top)

---

<a id="what-this-timeline-currently-shows"></a>

# What this timeline currently shows

The pattern is not random.

WFGY first became public as a baseline reference.  
Then it grew application surfaces.  
Then it found a practical wedge through the Problem Map line.  
Then it expanded into teaching systems, broader fix systems, evaluation surfaces, and finally visible public proof across outside ecosystems.

This matters because it shows continuity under cold-start conditions.

The strongest external wedge today still appears to be the **Problem Map line**, especially the structured debugging and failure-classification layer.  
That is the part that became easiest for outside projects to understand, adapt, and reuse.

At the same time, this timeline also shows that WFGY is broader than that wedge alone.  
The wider stack has been built in parallel, even if public proof is currently strongest on the diagnostic side.

It also shows that external legibility now spans more than one channel.  
The signal appears through direct documentation integration, tool wrapping, academic references, curated list inclusion, concept-level troubleshooting adoption, and a now-visible open-source support surface.

## Safest reading

The safest disciplined reading today is:

* WFGY has a real historical build-up, not a sudden one-page appearance
* it was built under cold-start conditions, in public, layer by layer
* the system became practical through the Problem Map line
* the strongest public adoption signal still clusters around diagnostic and debugging use
* the broader WFGY stack is larger than that single wedge, but public proof is currently strongest there
* open-source support is now publicly legible, but should not be confused with adoption
* the timeline shows continuity, structure, and increasing external legibility, but should not be exaggerated into universal adoption claims

---

<a id="maintenance-rules"></a>

# Maintenance rules

When updating this page:

1. Keep the timeline chronological.
2. Prefer dates when something became publicly visible in stable form.
3. Separate internal milestones from external proof in wording, even if they share the same page.
4. Do not retroactively inflate old events into stronger claims.
5. If a milestone is important but weak, move it to the [Recognition Map](./recognition/README.md) instead.
6. If an event belongs mainly to explanation rather than chronology, keep it in [CASE_EVIDENCE](./CASE_EVIDENCE.md).
7. If a future page becomes the canonical destination for a subtopic, keep this page concise and link outward instead of duplicating full explanations.

---

<a id="related-pages"></a>

# Related pages

Proof surfaces:

* [ADOPTERS](./ADOPTERS.md)
* [CASE_EVIDENCE](./CASE_EVIDENCE.md)
* [Recognition Map](./recognition/README.md)

Collaboration surfaces:

* [Work with WFGY](./WORK_WITH_WFGY.md)
* [Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md)
* [Sample Deliverable](./SAMPLE_DELIVERABLE.md)

Structure and reference:

* [Ecosystem Map](./ECOSYSTEM_MAP.md)
* [Problem Map 1.0](./ProblemMap/README.md)
* [Repository Citation Metadata](./CITATION.cff)

---

Last updated: 2026/03/30  
Maintained manually.