diff --git a/EVIDENCE_TIMELINE.md b/EVIDENCE_TIMELINE.md index 97e088f8..c463b3ad 100644 --- a/EVIDENCE_TIMELINE.md +++ b/EVIDENCE_TIMELINE.md @@ -1,22 +1,54 @@ + + # EVIDENCE_TIMELINE -🕰️ Historical evidence timeline for WFGY. +Historical evidence timeline for WFGY. This page records how WFGY became real, usable, public, and externally legible over time. -It is not limited to third-party adoption only. -It also tracks the major moments when the WFGY line itself became more concrete, more teachable, more reproducible, or more visible to the outside world. +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: -**build → structure → teaching → evaluation → public proof** +**cold start → structure → teaching → evaluation → public proof** -Related pages: +## 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) + +--- + + ## What this page is @@ -33,6 +65,17 @@ It combines three kinds of milestones: 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). + +--- + + + ## What this page is not This page is not: @@ -44,27 +87,35 @@ This page is not: * a claim that every milestone has equal weight For the shortest high-signal summary, use [ADOPTERS](./ADOPTERS.md). -For the full ledger, use the [Recognition Map](./recognition/README.md). +For the broader ledger, use the [Recognition Map](./recognition/README.md). +For cross-case interpretation, use [CASE_EVIDENCE](./CASE_EVIDENCE.md). --- + + # Timeline -## 2025/06/15 · 🧱 WFGY 1.0 becomes the baseline public reference + + +## 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/blob/main/legacy/README.md) established the project home and the earliest baseline reference for the WFGY line. +[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 +### 2025/07/02 · TXTOS opens the application layer **Track** Internal milestone @@ -76,9 +127,7 @@ Internal milestone 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 +### 2025/07/15 · Blah Blah Blah extends the TXTOS stack **Track** Internal milestone @@ -89,9 +138,18 @@ Internal milestone **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) + --- -## 2025/07/28 · 🗺️ Problem Map 1.0 becomes the practical wedge + + +## 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 @@ -103,9 +161,7 @@ Internal milestone 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 +### 2025/07/28 · Semantic Clinic expands the teaching layer **Track** Internal milestone @@ -116,9 +172,7 @@ Internal milestone **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 +### 2025/07/30 · Semantic Blueprint deepens the theory layer **Track** Internal milestone @@ -129,9 +183,7 @@ Internal milestone **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 +### 2025/09/05 · Global Fix Map extends beyond one checklist **Track** Internal milestone @@ -142,9 +194,7 @@ Internal milestone **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 +### 2025/09/14 · Grandma Clinic turns the map into memory-friendly teaching **Track** Internal milestone @@ -155,9 +205,21 @@ Internal milestone **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) + --- -## 2026/01/31 · 🌌 WFGY 3.0 Singularity Demo opens the frontier evaluation layer + + +## 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 @@ -169,9 +231,33 @@ Internal milestone 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, 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) + --- -## 2026/02/17 · 🌍 ToolUniverse shows tool-level public integration + + +## 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 @@ -183,9 +269,7 @@ ToolUniverse publicly merged a WFGY-related triage surface through [PR #75](http 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 +### 2026/02/20 · Rankify and Multimodal RAG Survey widen the external signal **Track** Public ecosystem milestone @@ -199,9 +283,7 @@ 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 +### 2026/02/23 · LlamaIndex makes the wedge more mainstream **Track** Public ecosystem milestone @@ -213,9 +295,7 @@ Public ecosystem milestone 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 +### 2026/02/25 · RAGFlow strengthens the operational debugging signal **Track** Public ecosystem milestone @@ -227,9 +307,7 @@ Public ecosystem milestone 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 +### 2026/03/01 · FlashRAG reinforces cross-stack reuse **Track** Public ecosystem milestone @@ -241,23 +319,7 @@ Public ecosystem milestone 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/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, more reusable format across platforms and models. - ---- - -## 2026/03/04 · 🤖 LightAgent extends the signal into multi-agent territory +### 2026/03/04 · LightAgent extends the signal into multi-agent territory **Track** Public ecosystem milestone @@ -268,9 +330,7 @@ Public ecosystem milestone **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 +### 2026/03/08 · Public proof becomes a first-class routing layer in WFGY **Track** Packaging milestone @@ -288,38 +348,38 @@ It also exposes a dedicated collaboration entry through [Work with WFGY](./WORK_ 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. + +[Back to top](#top) + --- + + # What this timeline currently shows -📌 At the current stage, the historical pattern is fairly clear. +The pattern is not random. -WFGY did not appear all at once as one finished artifact. -It grew in layers. +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. -The rough sequence looks like this: - -1. **baseline and theory** -2. **application surfaces** -3. **diagnostic maps** -4. **teaching and fix systems** -5. **frontier evaluation** -6. **external ecosystem proof** -7. **public packaging and collaboration routing** - -That matters because it shows continuity. +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, the internal timeline shows that WFGY is broader than that wedge alone. -The project has also been building theory surfaces, application surfaces, and frontier evaluation surfaces in parallel. +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. ## 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 @@ -327,9 +387,11 @@ The safest disciplined reading today is: --- + + # Maintenance rules -🧾 When updating this page: +When updating this page: 1. Keep the timeline chronological. 2. Prefer dates when something became publicly visible in stable form. @@ -337,17 +399,31 @@ The safest disciplined reading today is: 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. --- + + # 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) -* [Problem Map 2.0 Global Debug Card](https://github.com/onestardao/WFGY/releases/tag/WFGY-Global-Debug-Card) +* [Repository Citation Metadata](./CITATION.cff) ---