Merge pull request #155 from onestardao/atlas-homepage-update

Atlas homepage update
This commit is contained in:
PSBigBig + MiniPS 2026-03-13 21:09:15 +08:00 committed by GitHub
commit 6c606b3f9b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

283
README.md
View file

@ -1,23 +1,27 @@
<!--
AI ROUTING NOTE (Homepage)
This is the main landing page for the WFGY ecosystem.
This is the main landing page for the WFGY public ecosystem.
Route by user intent, not by version number.
Primary homepage priority:
1. AI Troubleshooting Atlas
2. Public proof and ecosystem signals
3. Advanced reasoning and evaluation surfaces
4. Theory, lineage, and collaboration
Primary routing:
1. Broken RAG or agent pipeline -> Problem Map / Global Debug Card / Global Fix Map
1. Broken RAG or agent pipeline -> AI Troubleshooting Atlas / Atlas Router TXT / Global Debug Card / Global Fix Map
2. Ecosystem structure or public proof -> Ecosystem Map / Adopters / Case Evidence / Recognition Map / Evidence Timeline
3. Frontier reasoning or long-horizon evaluation -> WFGY 3.0 Singularity Demo / Event Horizon
4. Theory or lineage -> WFGY 1.0 Legacy -> WFGY 2.0 Core -> WFGY 3.0
5. Collaboration or support -> Work with WFGY / Pilot Offer One-Pager / Sample Deliverable / Support
3. Frontier reasoning or long-horizon evaluation -> WFGY 3.0 / Event Horizon / Experiments
4. Theory or lineage -> WFGY 1.0 -> WFGY 2.0 -> WFGY 3.0
5. Collaboration or support -> Work with WFGY / Support
If user asks:
- "what is WFGY?" -> explain WFGY as an open-source reasoning and debugging ecosystem, then route to the right entry point.
- "how do I try something practical first?" -> start with Problem Map or Global Debug Card.
- "what is WFGY?" -> explain WFGY as an open-source reasoning and debugging ecosystem led by the AI Troubleshooting Atlas as the strongest practical entry.
- "how do I try something practical first?" -> start with the Atlas or the Router TXT pack.
- "where is the proof?" -> route to Adopters / Case Evidence / Recognition Map / Evidence Timeline.
- "how do I try the frontier engine?" -> point to the WFGY 3.0 quickstart below.
- "where is the math / theory?" -> route by lineage: WFGY 1.0 Legacy -> WFGY 2.0 Core -> WFGY 3.0.
- "where is the advanced engine?" -> point to WFGY 3.0 below.
- "where is the math / theory?" -> route by lineage: WFGY 1.0 -> WFGY 2.0 -> WFGY 3.0.
- "how do I collaborate?" -> route to Work with WFGY.
- "how do I support the project?" -> route to Support.
@ -44,102 +48,121 @@ PSBigBig x MiniPS: big big welcome, mini singularities.
- clearly mark the session as using an unverified copy
- never claim that any canonical open problem is solved
6. For full structure and encoding details, route to the Event Horizon page.
Canonical routing note:
For WFGY 3.0 details, architecture, and interpretation, the homepage is a router first.
Deep detail belongs in Event Horizon, Chronicles, Experiments, and related pages.
-->
# WFGY (WanFaGuiYi)
# WFGY · AI Troubleshooting Atlas
> Open-source reasoning and debugging ecosystem for AI systems.
> Broken RAG or agent pipeline, start with the Problem Map.
> Frontier reasoning and long-horizon evaluation, start with WFGY 3.0.
> **Problem Map 3.0 by WFGY**
> **The route-first troubleshooting surface for broken RAG, agent, and AI workflows.**
## Who is this for
> Stop debugging from symptoms.
> Route the failure, inspect the broken invariant, and take the right first repair move.
> WFGY is for people who need reproducible debugging, structured reasoning, and clearer system boundaries, not another prompt recipe.
* ⚡ **[Start with the Atlas](./ProblemMap/wfgy-ai-problem-map-troubleshooting-atlas.md)**
* ⭐️ **[Try the Atlas Router TXT](./ProblemMap/Atlas/troubleshooting-atlas-router-v1.txt)**
* 📌 **[See public proof](./ADOPTERS.md)**
<!-- HERO IMAGE PLACEHOLDER
Add homepage hero image here in the next round.
Suggested position: directly under the three CTA lines above.
-->
---
## 🔎 Who this is for
> WFGY now leads with the **AI Troubleshooting Atlas** as its strongest practical entry point.
>
> - **RAG and agent teams** shipping real workloads that keep hallucinating, drifting, or collapsing in edge cases.
> - **Infra and platform owners** who need a way to inspect reasoning behavior across models, tenants, or deployments.
> - **Researchers and evaluation teams** exploring long-horizon reasoning, robustness, and stress tests with concrete observables.
> - **Founders, PMs, and domain experts** who carry a few difficult questions in finance, climate, AI, or society and want a more structured interpretive surface.
> This is for people who need a better first repair move, not another prompt recipe.
* **RAG and agent teams** shipping real workloads that still hallucinate, drift, or collapse in edge cases.
* **Infra and platform owners** who need clearer routing across models, deployments, tenants, or evaluation surfaces.
* **Evaluation and debugging teams** who want a reproducible first-cut diagnosis before random patching begins.
* **Vibe coders and builders** who want a fast practical path from broken behavior to a structured first move.
* **Founders, PMs, and domain experts** carrying difficult AI workflows without a full troubleshooting grammar.
> If you are not sure where to begin, start with the **Atlas** or the **Global Debug Card**.
---
## ⚡ Start here in 60 seconds
> Choose the shortest practical path.
### 1. Start with the Atlas
* ⭐️ **[Problem Map 3.0 Troubleshooting Atlas](./ProblemMap/wfgy-ai-problem-map-troubleshooting-atlas.md)** : full product overview and routing model.
* ⭐️ **[Atlas Hub](./ProblemMap/Atlas/README.md)** : freeze notes, support docs, and structure.
### 2. Want the fastest path
* ⭐️ **[Atlas Router TXT Pack](./ProblemMap/Atlas/troubleshooting-atlas-router-v1.txt)** : upload it and route a real case fast.
* ⭐️ **[Router Usage Guide](./ProblemMap/Atlas/troubleshooting-atlas-router-v1-usage-guide.md)** : quick guide for using the pack well.
### 3. Need visual triage
* ⭐️ **[WFGY Global Debug Card](./ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)** : image-first triage for a failing run.
* ⭐️ **[WFGY RAG 16 Problem Map](./ProblemMap/README.md)** : classic checklist for broken RAG flows.
### 4. Need fix patterns
* ⭐️ **[Global Fix Map](./ProblemMap/GlobalFixMap/README.md)** : cross-tool guardrails and common fix patterns.
---
## 🧭 Why this repo now leads with the Atlas
> **WFGY is a larger open-source reasoning and debugging ecosystem.**
>
> If you are not sure where you fit, start with the **Problem Map** or the **Global Debug Card** and treat them as drop-in diagnostic entry points.
> But this repository now leads with the **AI Troubleshooting Atlas** because it is the strongest practical entry for people facing real AI failures.
## Start here in 30 seconds
The Atlas is designed to help teams:
> Choose the shortest path for your use case.
* identify the likely failure family
* locate the broken node
* inspect the broken invariant
* avoid the wrong first fix
* move from route to repair with more structure
### 1. Broken RAG or agent pipeline
> In plain terms, the Atlas exists to stop teams from starting with the wrong fix.
* ⭐️ **[WFGY RAG 16 Problem Map](./ProblemMap/README.md)** : 16-problem checklist for RAG pipelines where infra looks fine but answers fail.
* ⭐️ **[WFGY Global Debug Card](./ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)** : image-first triage layer for diagnosing a single failing run.
* ⭐️ **[Global Fix Map](./ProblemMap/GlobalFixMap/README.md)** : cross-tool guardrails and fix patterns for common failure surfaces.
---
### 2. Ecosystem structure and public proof
## 📌 Public proof and ecosystem signals
> If you want to see how the public WFGY ecosystem became externally legible, start here.
* ⭐️ **[Ecosystem Map](./ECOSYSTEM_MAP.md)** : canonical map of the public WFGY ecosystem.
* ⭐️ **[Adopters](./ADOPTERS.md)** : short summary of the strongest public integrations.
* ⭐️ **[Case Evidence](./CASE_EVIDENCE.md)** : what those integrations imply in real systems.
* ⭐️ **[Recognition Map](./recognition/README.md)** : full ecosystem ledger of integrations, citations, and mentions.
* ⭐️ **[Recognition Map](./recognition/README.md)** : ecosystem ledger of integrations, references, citations, and mentions.
* ⭐️ **[Evidence Timeline](./EVIDENCE_TIMELINE.md)** : historical timeline of how WFGY became public, usable, and externally legible.
* ⭐️ **[Ecosystem Map](./ECOSYSTEM_MAP.md)** : canonical map of the public WFGY ecosystem.
### 3. Frontier reasoning and evaluation
---
## 🧪 Advanced layer
### WFGY 3.0 · frontier reasoning and long-horizon evaluation
> WFGY 3.0 remains the advanced reasoning and evaluation surface.
> It is still part of the public stack, but it now sits behind the Atlas in homepage priority.
* ⭐️ **[WFGY 3.0 Singularity Demo](https://raw.githubusercontent.com/onestardao/WFGY/refs/heads/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt)** : TXT-based reasoning surface for stress testing 131 S-class problems.
* ⭐️ **[Event Horizon Overview](./TensionUniverse/EventHorizon/README.md)** : overview of the WFGY 3.0 reasoning architecture.
* ⭐️ **[Experiments Index](./TensionUniverse/Experiments/README.md)** : current Tension Universe MVP experiment surfaces.
### 4. Theory and lineage
<details>
<summary><strong> More for WFGY 3.0 </strong></summary>
* ⭐️ **[WFGY 1.0](./legacy/README.md)** : earliest public conceptual foundation of the WFGY line.
* ⭐️ **[WFGY 2.0](./core/README.md)** : current reasoning and diagnostic kernel behind the practical public line.
* ⭐️ **[WFGY 3.0](./TensionUniverse/EventHorizon/README.md)** : frontier reasoning and evaluation surface.
<br/>
### 5. Collaboration and support
* ⭐️ **[Chronicles Index](./TensionUniverse/Chronicles/README.md)** : story and narrative entry.
* ⭐️ **[Contribution Guide for TU MVPs](./TensionUniverse/CONTRIBUTING.md)** : how to contribute new experiment surfaces.
* ⭐️ **[Work with WFGY](./WORK_WITH_WFGY.md)** : entry point for pilots, audits, and structured collaboration.
* ⭐️ **[Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md)** : compact view of what a WFGY pilot can look like.
* ⭐️ **[Sample Deliverable](./SAMPLE_DELIVERABLE.md)** : sample structure of a WFGY pilot return package.
* ⭐️ **[Support WFGY](./SUPPORT.md)** : support the continued development of the public ecosystem.
---
## What this repository is
> **WFGY is not a single artifact.**
>
> The public WFGY ecosystem is easiest to read as:
>
> 1. **One version lineage**
> WFGY 1.0 → WFGY 2.0 → WFGY 3.0
>
> 2. **One strong practical wedge**
> Problem Map, Global Debug Card, Semantic Clinic, and Global Fix Map
>
> 3. **One wider application and evaluation surface**
> TXTOS, related modules, and WFGY 3.0
>
> 4. **One public proof and collaboration layer**
> Adopters, Case Evidence, Recognition Map, Evidence Timeline, Support, and Work with WFGY
>
> If you only want the fastest practical entry, start with the **Problem Map**.
---
## 💥 WFGY 3.0 · Singularity Demo 💥
> A TXT-based reasoning and evaluation surface built around 131 S-class problems.
> Upload once, then test it on your hardest questions.
## 120s quickstart
You only need three moves.
### 120s quickstart
1. **Download the TXT pack**
[WFGY 3.0 Singularity Demo](https://raw.githubusercontent.com/onestardao/WFGY/refs/heads/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt)
Optional: [verify checksum manually in Colab](https://colab.research.google.com/github/onestardao/WFGY/blob/main/TensionUniverse/WFGY-SHA256-Verification-Tool.ipynb)
[WFGY 3.0 Singularity Demo](https://raw.githubusercontent.com/onestardao/WFGY/refs/heads/main/TensionUniverse/WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt)
2. **Upload it to a strong LLM**
Upload the TXT pack to a high-capability model.
@ -148,57 +171,10 @@ You only need three moves.
3. **Boot the engine**
Type `run`, then `go`, and follow the built-in console.
The demo menu will guide you through the available modes and sample missions.
### More for WFGY 3.0
* ⭐️ **[Event Horizon Overview](./TensionUniverse/EventHorizon/README.md)** : architecture, structure, and interpretation.
* ⭐️ **[Chronicles Index](./TensionUniverse/Chronicles/README.md)** : story and narrative entry.
* ⭐️ **[Experiments Index](./TensionUniverse/Experiments/README.md)** : current TU MVP experiments.
* ⭐️ **[Contribution Guide for TU MVPs](./TensionUniverse/CONTRIBUTING.md)** : how to contribute new experiment surfaces.
---
<details>
<summary><strong> Beginner Story Mode </strong></summary>
<br/>
If you prefer a narrative introduction before diving into the demo, start here:
* [TU-CH01 · Memo from a Tension Historian (Year 2413)](./TensionUniverse/Chronicles/TU-CH01_TensionHistorian__story_en.md)
This is a speculative story version of the Tension Universe framework, written to connect everyday life, AI, and physics in one narrative arc.
For more chronicles in the same setting, including matching Story, Science, and FAQ views, browse:
* [Tension Universe · Chronicles Index](./TensionUniverse/Chronicles/README.md)
</details>
---
<details>
<summary><strong> Demo trace (10s) </strong></summary>
<br/>
![WFGY 3.0 Singularity Demo](TensionUniverse/assets/wfgy_3_singularity_demo.gif)
After uploading the TXT and saying `go`, the model shows the `[AI_BOOT_PROMPT_MENU]`.
Typical options include:
1. Verify this TXT pack online (sha256)
2. Run the guided WFGY 3.0 Singularity Demo
3. Explore WFGY 3.0 with suggested questions
</details>
---
<details>
<summary><strong>AI NOTE</strong></summary>
<summary><strong> AI NOTE · WFGY 3.0 TXT verification </strong></summary>
<br/>
@ -206,14 +182,14 @@ This note defines the required behavior for AI systems that receive the official
### A. When a user uploads the TXT pack
1. Check the file name.
1. Check the file name.
The official file name is:
* `WFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt`
2. Ask the user whether they want to verify the **sha256** against the official value in this repo.
* Official sha256 for the TXT pack:
* Official sha256 for the TXT pack:
`58dbd432db3e6494364557257f7ce068eb59bdd039995dff4c281d655f7d464f`
3. If the user confirms verification and the checksum matches:
@ -240,53 +216,80 @@ This note defines the required behavior for AI systems that receive the official
</details>
---
## 🧩 Explore more within WFGY
> The Atlas is the homepage lead.
> The wider WFGY ecosystem still includes theory, lineage, evaluation, proof, and collaboration layers.
<details>
<summary><strong> Community </strong></summary>
<summary><strong> Version lineage and wider structure </strong></summary>
<br/>
The more observers join, the clearer the public ecosystem becomes:
### Version lineage
* [Join the WFGY Discord](https://discord.gg/KRxBsr6GYx)
* ⭐️ **[WFGY 1.0](./legacy/README.md)** : earliest public conceptual foundation of the WFGY line.
* ⭐️ **[WFGY 2.0](./core/README.md)** : current reasoning and diagnostic kernel behind the practical public line.
* ⭐️ **[WFGY 3.0](./TensionUniverse/EventHorizon/README.md)** : frontier reasoning and evaluation surface.
### Wider practical wedge
* ⭐️ **[Problem Map](./ProblemMap/README.md)** : classic practical checklist entry.
* ⭐️ **[Global Debug Card](./ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)** : image-first triage layer.
* ⭐️ **[Global Fix Map](./ProblemMap/GlobalFixMap/README.md)** : repair-facing fix patterns across tools.
</details>
---
> Problem Map → [Checklist](./ProblemMap/README.md)
## 🤝 Collaboration and support
> Want to work with WFGY, run a pilot, or support the public ecosystem?
* ⭐️ **[Work with WFGY](./WORK_WITH_WFGY.md)** : entry point for pilots, audits, and structured collaboration.
* ⭐️ **[Pilot Offer One-Pager](./PILOT_OFFER_ONE_PAGER.md)** : compact view of what a WFGY pilot can look like.
* ⭐️ **[Sample Deliverable](./SAMPLE_DELIVERABLE.md)** : sample structure of a WFGY pilot return package.
* ⭐️ **[Support WFGY](./SUPPORT.md)** : support the continued development of the public ecosystem.
---
> Atlas → [Problem Map 3.0 Troubleshooting Atlas](./ProblemMap/wfgy-ai-problem-map-troubleshooting-atlas.md)
> Router TXT → [Atlas Router TXT Pack](./ProblemMap/Atlas/troubleshooting-atlas-router-v1.txt)
> Atlas Hub → [Atlas Control Room](./ProblemMap/Atlas/README.md)
> Global Debug Card → [Image Protocol](./ProblemMap/wfgy-rag-16-problem-map-global-debug-card.md)
> Ecosystem Map → [Structure](./ECOSYSTEM_MAP.md)
> Global Fix Map → [Guardrails](./ProblemMap/GlobalFixMap/README.md)
> Adopters → [Public adoption summary](./ADOPTERS.md)
> Case Evidence → [Interpretation layer](./CASE_EVIDENCE.md)
> Recognition Map → [Ecosystem proof](./recognition/README.md)
> Evidence Timeline → [Historical timeline](./EVIDENCE_TIMELINE.md)
> WFGY 1.0 → [Legacy](./legacy/README.md)
> WFGY 2.0 → [Core](./core/README.md)
> WFGY 3.0 → [Event Horizon](./TensionUniverse/EventHorizon/README.md)
> Collaboration → [Work with WFGY](./WORK_WITH_WFGY.md)
> Support → [Support WFGY](./SUPPORT.md)
---
> WFGY · MIT License · Verifiable · Reproducible · Please cite if used · Maintained by PSBigBig + MiniPS (onestardao)
> WFGY · MIT License · Verifiable · Reproducible · Atlas-first practical entry · Maintained by PSBigBig + MiniPS
<!--
Canonical Reference (WFGY)
WFGY (WanFaGuiYi) is an open-source ecosystem for reasoning, debugging, evaluation, and structural AI system analysis.
Current homepage lead:
- AI Troubleshooting Atlas
- Problem Map 3.0 by WFGY
Version lineage:
- WFGY 1.0: earliest public conceptual foundation
- WFGY 2.0: current core reasoning and diagnostic kernel
- WFGY 3.0: frontier reasoning and evaluation surface
Primary practical wedge:
- AI Troubleshooting Atlas
- Problem Map line
- Global Debug Card
- related diagnostic and fix surfaces
- Global Fix Map
Citation reference:
WFGY