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.
This page is a structural map.
It is here to answer questions such as:
- What is the difference between WFGY 1.0, 2.0, and 3.0
- Where the Problem Map line belongs
- Where TXTOS and application surfaces belong
- Which pages are about theory, debugging, evaluation, proof, or collaboration
- What a new reader should open first
This page is not a homepage replacement, not a pitch deck, and not a full documentation index.
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.
The public WFGY ecosystem is easiest to read in two directions at once:
This is the main version order of the framework line:
WFGY 1.0 → WFGY 2.0 → WFGY 3.0
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.
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
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
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
The following lines cut across the version lineage and make the ecosystem legible in practice.
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
Best current reading
The Problem Map line is not the whole WFGY ecosystem.
It is the strongest practical public entry wedge.
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
Additional application surfaces may be added over time.
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
- Case Evidence
- Recognition Map
- Evidence Timeline
- Work with WFGY
- Pilot Offer One-Pager
- Sample Deliverable
- Citation Metadata
Different readers should start in different places.
Start here:
Then move to:
Start here:
Then move to:
Start here:
Then move to:
Start here:
Then move to:
A few distinctions are especially important.
They belong to one version lineage, but they do different jobs.
It is the strongest practical wedge, not the totality of WFGY.
WFGY 2.0 is the current framework kernel.
WFGY 3.0 is the frontier reasoning and evaluation surface.
TXTOS belongs to the application line of the ecosystem.
Adopters, Case Evidence, Recognition Map, and Evidence Timeline help outside readers evaluate the ecosystem.
They should not be mistaken for the framework itself.
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.
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.
- Adopters
- Case Evidence
- Recognition Map
- Evidence Timeline
- Work with WFGY
- Pilot Offer One-Pager
- Sample Deliverable
- Citation Metadata
Maintained as the canonical structural map of the public WFGY ecosystem.