# ECOSYSTEM_MAP Canonical map of the public WFGY ecosystem. This page explains how the major public WFGY surfaces relate to each other. Its purpose is simple: help a new reader understand the difference between the version lineage, the diagnostic line, the application surfaces, and the public proof and collaboration layer. WFGY is not a single artifact. It is a connected ecosystem with multiple public entry points. Without a clear map, new readers may misread the project as a set of unrelated parallel products. This page exists to prevent that. For the main front door, use [README](./README.md). --- ## What this page is This page is a structural map. It is here to answer questions such as: 1. What is the difference between WFGY 1.0, 2.0, and 3.0 2. Where the Problem Map line belongs 3. Where TXTOS and application surfaces belong 4. Which pages are about theory, debugging, evaluation, proof, or collaboration 5. What a new reader should open first This page is not a homepage replacement, not a pitch deck, and not a full documentation index. --- ## Short version The shortest disciplined reading is this: * **WFGY 1.0** is the earliest public conceptual foundation * **WFGY 2.0** is the current core reasoning and diagnostic kernel * **WFGY 3.0** is the frontier reasoning and evaluation surface * **Problem Map line** is the strongest practical public debugging wedge * **TXTOS and related modules** are application surfaces within the wider ecosystem * **Adopters, Case Evidence, Recognition Map, Evidence Timeline, and Work with WFGY** form the public proof and collaboration layer If you only want the fastest practical entry, start with the [Problem Map](./ProblemMap/README.md). --- ## A simple way to read the ecosystem The public WFGY ecosystem is easiest to read in two directions at once: ### 1. Version lineage This is the main version order of the framework line: **WFGY 1.0 → WFGY 2.0 → WFGY 3.0** ### 2. Cross-cutting public lines These are the major public-facing lines that sit across or around the version lineage: * the **Problem Map diagnostic line** * the **application line**, including TXTOS and related modules * the **public proof and collaboration line** This distinction matters. The version lineage explains how the framework evolved. The cross-cutting lines explain how different parts of the ecosystem are exposed and used in practice. --- ## Version lineage ### WFGY 1.0 **Role** Earliest public conceptual foundation **What it is** WFGY 1.0 should be read as the earliest public baseline of the WFGY line. It is the conceptual starting point of the ecosystem. **What it is not** It is not the main practical entry point for most new users today. **Main surface** * [WFGY 1.0 Legacy](./legacy/README.md) --- ### WFGY 2.0 **Role** Current core reasoning and diagnostic kernel **What it is** WFGY 2.0 should be read as the central framework layer behind the current public debugging line. It is the main framework bridge between the earlier conceptual foundation and the more practical public diagnostic surfaces. **What it is not** It is not identical to the Problem Map line, even though the Problem Map line is one of its strongest practical public expressions. **Main surface** * [WFGY 2.0 Core](./core/README.md) --- ### WFGY 3.0 **Role** Frontier reasoning and evaluation surface **What it is** WFGY 3.0 expands the ecosystem into a broader reasoning, stress-testing, and long-horizon evaluation surface. **What it is not** It should not be treated as the default first-stop page for every new user. It is a more advanced and exploratory surface. **Main surfaces** * [WFGY 3.0 Singularity Demo](https://github.com/onestardao/WFGY/blob/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt) * [Event Horizon Overview](./TensionUniverse/EventHorizon/README.md) --- ## Cross-cutting lines The following lines cut across the version lineage and make the ecosystem legible in practice. ### 1. Problem Map diagnostic line This is the strongest practical public wedge in the WFGY ecosystem. Its job is to help teams classify failures, reduce debugging ambiguity, and move from symptoms to more reproducible diagnosis and triage. It is the part of WFGY that outside RAG and agent teams can usually understand first. **Key surfaces** * [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) * [Semantic Clinic](./ProblemMap/SemanticClinicIndex.md) * [Global Fix Map](./ProblemMap/GlobalFixMap/README.md) **Best current reading** The Problem Map line is not the whole WFGY ecosystem. It is the strongest practical public entry wedge. --- ### 2. Application line This line contains application-facing surfaces and practical modules. These should not be read as disconnected side branches. They belong to the wider WFGY ecosystem and should be understood as application surfaces rather than separate universes. **Key surfaces** * [TXTOS](./OS/README.md) * [TXT: Blah Blah Blah](./OS/BlahBlahBlah/README.md) Additional application surfaces may be added over time. --- ### 3. Public proof and collaboration line This line helps outside readers answer a different set of questions: * Is WFGY real * How has it become publicly legible * What public proof exists * How would collaboration begin This line is not the engine itself. It is the public evidence and collaboration surface around the engine. **Key surfaces** * [Adopters](./ADOPTERS.md) * [Case Evidence](./CASE_EVIDENCE.md) * [Recognition Map](./recognition/README.md) * [Evidence Timeline](./EVIDENCE_TIMELINE.md) * [Work with WFGY](./WORK_WITH_WFGY.md) * [Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md) * [Sample Deliverable](./SAMPLE_DELIVERABLE.md) * [Citation Metadata](./CITATION.cff) --- ## Recommended reading paths Different readers should start in different places. ### If you are a RAG or agent team with a broken system Start here: * [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) Then move to: * [Global Fix Map](./ProblemMap/GlobalFixMap/README.md) * [WFGY 2.0 Core](./core/README.md) --- ### If you want to understand the framework lineage first Start here: * [WFGY 1.0 Legacy](./legacy/README.md) * [WFGY 2.0 Core](./core/README.md) * [WFGY 3.0 Singularity Demo](https://github.com/onestardao/WFGY/blob/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt) Then move to: * [Problem Map 1.0](./ProblemMap/README.md) * [Ecosystem Map](./ECOSYSTEM_MAP.md) --- ### If you want the frontier reasoning and evaluation surface Start here: * [WFGY 3.0 Singularity Demo](https://github.com/onestardao/WFGY/blob/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt) * [Event Horizon Overview](./TensionUniverse/EventHorizon/README.md) Then move to: * [WFGY 2.0 Core](./core/README.md) * [Evidence Timeline](./EVIDENCE_TIMELINE.md) --- ### If you want proof, adoption, or collaboration context Start here: * [Adopters](./ADOPTERS.md) * [Case Evidence](./CASE_EVIDENCE.md) * [Recognition Map](./recognition/README.md) Then move to: * [Evidence Timeline](./EVIDENCE_TIMELINE.md) * [Work with WFGY](./WORK_WITH_WFGY.md) --- ## What should not be confused A few distinctions are especially important. ### WFGY 1.0, 2.0, and 3.0 are not interchangeable labels They belong to one version lineage, but they do different jobs. ### Problem Map is not the whole ecosystem It is the strongest practical wedge, not the totality of WFGY. ### WFGY 2.0 and WFGY 3.0 are not the same kind of surface WFGY 2.0 is the current framework kernel. WFGY 3.0 is the frontier reasoning and evaluation surface. ### TXTOS is not a disconnected side branch TXTOS belongs to the application line of the ecosystem. ### Public proof pages are not the engine Adopters, Case Evidence, Recognition Map, and Evidence Timeline help outside readers evaluate the ecosystem. They should not be mistaken for the framework itself. ### Collaboration pages are not deployment claims Work with WFGY, Pilot Offer One-Pager, and Sample Deliverable describe how collaboration may begin. They do not by themselves prove deployment, revenue, or enterprise-scale adoption. --- ## Best current reading of the ecosystem At the current stage, the clearest reading is this: WFGY is a multi-layer public ecosystem organized around a stable version lineage and a set of practical cross-cutting lines. The version lineage is: **WFGY 1.0 → WFGY 2.0 → WFGY 3.0** Across that lineage, the strongest practical public wedge today is the Problem Map diagnostic line. Around that wedge sit application surfaces, public proof surfaces, and collaboration surfaces that make the ecosystem easier to use, evaluate, and extend. A new reader does not need to understand everything at once. They only need to enter through the right door. --- ## Related pages ### Main entry * [README](./README.md) ### Version lineage * [WFGY 1.0 Legacy](./legacy/README.md) * [WFGY 2.0 Core](./core/README.md) * [WFGY 3.0 Singularity Demo](https://github.com/onestardao/WFGY/blob/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt) * [Event Horizon Overview](./TensionUniverse/EventHorizon/README.md) ### Diagnostic line * [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) * [Semantic Clinic](./ProblemMap/SemanticClinicIndex.md) * [Global Fix Map](./ProblemMap/GlobalFixMap/README.md) ### Application line * [TXTOS](./OS/README.md) * [TXT: Blah Blah Blah](./OS/BlahBlahBlah/README.md) ### Proof and collaboration line * [Adopters](./ADOPTERS.md) * [Case Evidence](./CASE_EVIDENCE.md) * [Recognition Map](./recognition/README.md) * [Evidence Timeline](./EVIDENCE_TIMELINE.md) * [Work with WFGY](./WORK_WITH_WFGY.md) * [Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md) * [Sample Deliverable](./SAMPLE_DELIVERABLE.md) * [Citation Metadata](./CITATION.cff) --- Maintained as the canonical structural map of the public WFGY ecosystem.