mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-28 19:50:17 +00:00
310 lines
16 KiB
Markdown
310 lines
16 KiB
Markdown
# WFGY Problem Map 1.0 — Bookmark it. You'll need it.
|
||
**16 reproducible failure modes in AI systems — with fixes (MIT).**
|
||
*If this page saves you time, a ⭐ helps others find it.*
|
||
> Cold start → ⭐ 380 stars in just 55 days — built to solve real problems, not just look cool.
|
||
|
||
<div align="center">
|
||
<!-- keep one visual; remove if you prefer text-only -->
|
||
<img src="https://github.com/onestardao/WFGY/raw/main/OS/images/tree-semantic-memory.gif"
|
||
alt="Semantic memory & reasoning fix in action"
|
||
width="100%" style="max-width:900px" loading="lazy">
|
||
</div>
|
||
|
||
---
|
||
|
||
## Quick access
|
||
|
||
- 🏥 **Semantic Clinic (AI Triage Hub):** [Fix symptoms when you don’t know what’s broken →](./SemanticClinicIndex.md)
|
||
- **Beginner Guide:** [Identify & fix your first failure](./BeginnerGuide.md)
|
||
- **Diagnose by symptom:** [Fast triage table → `Diagnose.md`](./Diagnose.md)
|
||
- **Visual RAG Guide (multi-dimensional):** [`RAG Architecture & Recovery – Problem Map 2.0`](./rag-architecture-and-recovery.md) — high-altitude view linking symptom × pipeline stage × failure class, with the exact recovery path.
|
||
- **Field Reports:** [Real bugs & fixes from users](https://github.com/onestardao/WFGY/discussions/10)
|
||
- **TXT OS directory:** [Browse the OS repo](../OS/)
|
||
|
||
|
||
> 📌 This map isn’t just a list of bugs. It’s a diagnostic framework — a semantic X-ray for AI failure.
|
||
> Each entry represents a *systemic breakdown* across input, retrieval, or reasoning.
|
||
> WFGY doesn’t patch symptoms. It restructures the entire reasoning chain.
|
||
|
||
|
||
---
|
||
|
||
## Quick-Start Downloads (60 sec)
|
||
| Tool | Link | 3-Step Setup |
|
||
|------|------|--------------|
|
||
| **WFGY 1.0 PDF** | [Engine Paper](https://zenodo.org/records/15630969) | 1) Download 2) Upload to your LLM 3) Ask: “answer using WFGY + <your question>” |
|
||
| **TXT OS (plain-text OS)** | [TXTOS.txt](https://zenodo.org/records/15788557) | 1) Download 2) Paste into any LLM chat 3) Type “hello world” to boot |
|
||
|
||
---
|
||
|
||
## 🧪 One-click sandboxes — run WFGY instantly
|
||
|
||
Run lightweight diagnostics with **zero install**, **zero API key**. Powered by Colab.
|
||
|
||
> These 4 CLI tools demonstrate WFGY's diagnostic power — each maps directly to one of the 16 failure modes.
|
||
> Other problems (like deployment bugs or reasoning collapse) are already handled inside WFGY,
|
||
> but are not exposed as CLI yet — either because they require full context, or operate at system level.
|
||
> More tools coming soon.
|
||
|
||
|
||
<details>
|
||
<summary><strong>⭐ ΔS Diagnostic (MVP)</strong> — Measure semantic drift</summary>
|
||
|
||
<br>
|
||
|
||
[](https://colab.research.google.com/github/onestardao/WFGY/blob/main/tools/wfgy_diagnose_colab.ipynb)
|
||
|
||
> **How to use**
|
||
> 1. Click the badge ▸ Runtime ▸ Run all
|
||
> 2. Replace `prompt` and `answer`
|
||
> 3. See ΔS score and suggested fix
|
||
>
|
||
> **What it detects:**
|
||
> No.2 – [Interpretation Collapse](https://github.com/onestardao/WFGY/blob/main/ProblemMap/retrieval-collapse.md)
|
||
> (Prompt and output look fine, but meaning is mismatched)
|
||
|
||
</details>
|
||
|
||
<details>
|
||
<summary><strong>⭐ λ_observe Checkpoint</strong> — Mid-step re-grounding</summary>
|
||
|
||
<br>
|
||
|
||
[](https://colab.research.google.com/github/onestardao/WFGY/blob/main/tools/wfgy_lambda_observe_colab.ipynb)
|
||
|
||
> **How to use**
|
||
> 1. Run all cells
|
||
> 2. Edit `prompt`, `step1`, `step2`
|
||
> 3. Compare ΔS before vs after
|
||
>
|
||
> If ΔS drops → checkpoint worked
|
||
> If not → try BBCR fallback
|
||
>
|
||
> **What it fixes:**
|
||
> No.6 – [Logic Collapse & Recovery](https://github.com/onestardao/WFGY/blob/main/ProblemMap/logic-collapse.md)
|
||
> (Multi-step reasoning veers off and needs semantic midpoints)
|
||
|
||
</details>
|
||
|
||
<details>
|
||
<summary><strong>⭐ ε_resonance</strong> — Domain-level semantic harmony</summary>
|
||
|
||
<br>
|
||
|
||
[](https://colab.research.google.com/github/onestardao/WFGY/blob/main/tools/wfgy_e_resonance_colab.ipynb)
|
||
|
||
> **How to use**
|
||
> 1. Run all cells
|
||
> 2. Edit `prompt` and `answer`
|
||
> 3. Optionally update the `anchors` list
|
||
>
|
||
> Higher ε → deeper resonance with domain anchors
|
||
>
|
||
> **What it explains:**
|
||
> No.12 – [Philosophical Recursion](https://github.com/onestardao/WFGY/blob/main/ProblemMap/philosophical-recursion.md)
|
||
> (Looping abstraction caused by mismatched domains)
|
||
|
||
</details>
|
||
|
||
<details>
|
||
<summary><strong>⭐ λ_diverse</strong> — Answer-set diversity check</summary>
|
||
|
||
<br>
|
||
|
||
[](https://colab.research.google.com/github/onestardao/WFGY/blob/main/tools/wfgy_lambda_diverse_colab.ipynb)
|
||
|
||
> **How to use**
|
||
> 1. Run all cells
|
||
> 2. Fill in `prompt` and `answers` (≥ 3 examples)
|
||
> 3. See λ_diverse score
|
||
>
|
||
> Low (≤ 0.40) — near duplicates
|
||
> Medium (0.40–0.70) — partial variety
|
||
> High (≥ 0.70) — rich semantic variation
|
||
>
|
||
> **What it detects:**
|
||
> No.3 – [Long Reasoning Chains](https://github.com/onestardao/WFGY/blob/main/ProblemMap/context-drift.md)
|
||
> (Early steps diverge silently across variants)
|
||
|
||
</details>
|
||
|
||
<details>
|
||
<summary><strong>🍷 More modules coming soon — Drunk Transformer preview</strong></summary>
|
||
|
||
<br>
|
||
|
||
> These formulas may sound like something a language model would say after a few drinks…
|
||
> But they’re actually designed to keep your model sober — no more collapsing logic, no more derailed reasoning.
|
||
> Think of it as semantic seatbelts for your transformer.
|
||
>
|
||
> ---
|
||
>
|
||
> **WDT** – Where Did You Take me?
|
||
> → Asymmetric cross-path suppression. Prevents illegal logic jumps between divergent tracks.
|
||
>
|
||
> **WTF** – What the F*** happened?
|
||
> → Collapse detection and graceful reset. When everything breaks, it gently hits the semantic panic button.
|
||
>
|
||
> ---
|
||
>
|
||
> Drunk Transformer math layer (coming soon)
|
||
>
|
||
> • **WRI** – Where am I? → Locks token positions to maintain structural coherence
|
||
> • **WAI** – Who am I? → Forces head diversity to avoid collapse-by-consensus
|
||
> • **WAY** – Who are you? → Boosts entropy across attention heads for better external awareness
|
||
> • **WDT** – Where did you take me? → (see above)
|
||
> • **WTF** – What the f*** happened? → (see above)
|
||
>
|
||
> ---
|
||
>
|
||
> Each one is backed by a real formula.
|
||
> You’ll be able to try them soon — stay tuned.
|
||
>
|
||
> P.S. These formulas are real.
|
||
> Like, math-real. Not just wine-fueled wordplay. :P
|
||
|
||
</details>
|
||
|
||
> ⚠️ Warning ⚠️ These tools may trigger existential reflection — especially if you've spent months chasing ghost bugs in your RAG stack.
|
||
|
||
|
||
|
||
---
|
||
|
||
## Failure catalog (with fixes)
|
||
|
||
| # | Problem Domain | What breaks | Doc |
|
||
|----|---------------------------------|-----------------------------------------------|-----|
|
||
| 1 | Hallucination & Chunk Drift | Retrieval returns wrong/irrelevant content | [hallucination.md](./hallucination.md) |
|
||
| 2 | Interpretation Collapse | Chunk is right, logic is wrong | [retrieval-collapse.md](./retrieval-collapse.md) |
|
||
| 3 | Long Reasoning Chains | Drifts across multi-step tasks | [context-drift.md](./context-drift.md) |
|
||
| 4 | Bluffing / Overconfidence | Confident but unfounded answers | [bluffing.md](./bluffing.md) |
|
||
| 5 | Semantic ≠ Embedding | Cosine match ≠ true meaning | [embedding-vs-semantic.md](./embedding-vs-semantic.md) |
|
||
| 6 | Logic Collapse & Recovery | Dead-end paths; needs controlled reset | [logic-collapse.md](./logic-collapse.md) |
|
||
| 7 | Memory Breaks Across Sessions | Lost threads, no continuity | [memory-coherence.md](./memory-coherence.md) |
|
||
| 8 | Debugging is a Black Box | No visibility into failure path | [retrieval-traceability.md](./retrieval-traceability.md) |
|
||
| 9 | Entropy Collapse | Attention melts, incoherent output | [entropy-collapse.md](./entropy-collapse.md) |
|
||
| 10 | Creative Freeze | Flat, literal outputs | [creative-freeze.md](./creative-freeze.md) |
|
||
| 11 | Symbolic Collapse | Abstract/logical prompts break | [symbolic-collapse.md](./symbolic-collapse.md) |
|
||
| 12 | Philosophical Recursion | Self-reference/paradoxes crash reasoning | [philosophical-recursion.md](./philosophical-recursion.md) |
|
||
| 13 | Multi-Agent Chaos | Agents overwrite/misalign logic | [multi-agent-chaos.md](./multi-agent-chaos.md) |
|
||
| 14 | Bootstrap Ordering | Services fire before deps ready | [bootstrap-ordering.md](./bootstrap-ordering.md) |
|
||
| 15 | Deployment Deadlock | Circular waits (index⇆retriever, DB⇆migrator) | [deployment-deadlock.md](./deployment-deadlock.md) |
|
||
| 16 | Pre-Deploy Collapse | Version skew / missing secret on first call | [predeploy-collapse.md](./predeploy-collapse.md) |
|
||
|
||
> Problem families: **Prompting · Retrieval · Reasoning · Infra/Deploy** — locate the root cause first, then apply the specific patch.
|
||
|
||
---
|
||
|
||
## Why these 16 errors were solvable
|
||
WFGY does not just react; it gives **semantic altitude**. Core tools `ΔS`, `λ_observe`, and `e_resonance` help detect, decode, and defuse collapse patterns from **outside** the maze.
|
||
|
||
**See the pipeline and recovery end-to-end:**
|
||
→ [`RAG Architecture & Recovery`](./rag-architecture-and-recovery.md)
|
||
|
||
---
|
||
|
||
## Problem Maps Index (Map-A … Map-G)
|
||
These short IDs let you route quickly in issues/PRs/support threads.
|
||
|
||
| Map ID | Map Name | Linked Issues | Focus | Link |
|
||
|-------:|------------------------------|----------------------|------------------------------------------------|------|
|
||
| Map-A | RAG Problem Table | #1, #2, #3, #5, #8 | Retrieval-augmented generation failures | [View](./RAG_Problems.md) |
|
||
| Map-B | Multi-Agent Chaos Map | #13 | Coordination failures, memory conflicts | [View](./Multi-Agent_Problems.md) |
|
||
| Map-C | Symbolic & Recursive Map | #11, #12 | Symbolic logic traps, abstraction, paradox | [View](./Symbolic_Logic_Problems.md) |
|
||
| Map-D | Logic Recovery Map | #6 | Dead-end logic, reset loops, controlled recovery | [View](./logic-collapse.md) |
|
||
| Map-E | Long-Context Stress Map | #3, #7, #10 | 100k-token memory, noisy PDFs, long-task drift | [View](./LongContext_Problems.md) |
|
||
| Map-F | Safety Boundary Map | #4, #8 | Overconfidence, jailbreak resistance, traceability | [View](./Safety_Boundary_Problems.md) |
|
||
| Map-G | Infra Boot Map | #14–#16 | Ordering, boot loops, version skew, deadlocks | [View](./Infra_Boot_Problems.md) |
|
||
|
||
---
|
||
|
||
## Minimal quick-start
|
||
1. Open **Beginner Guide** → follow the symptom checklist.
|
||
2. Use the **Visual RAG Guide** to locate the failing stage.
|
||
3. Open the matching page above and apply the patch.
|
||
|
||
Ask any LLM to apply WFGY (TXT OS makes it smoother):
|
||
```
|
||
|
||
I’ve uploaded TXT OS / WFGY notes.
|
||
My issue: \[e.g., OCR tables from scanned PDFs look fine but answers are wrong].
|
||
Which WFGY modules should I apply and in what order?
|
||
|
||
```
|
||
|
||
<details>
|
||
<summary><strong>Status & difficulty</strong></summary>
|
||
|
||
| # | Problem | Difficulty* | Implementation |
|
||
|----|---------------------------------|-------------|----------------|
|
||
| 1 | Hallucination & Chunk Drift | Medium | ✅ Stable |
|
||
| 2 | Interpretation Collapse | High | ✅ Stable |
|
||
| 3 | Long Reasoning Chains | High | ✅ Stable |
|
||
| 4 | Bluffing / Overconfidence | High | ✅ Stable |
|
||
| 5 | Semantic ≠ Embedding | Medium | ✅ Stable |
|
||
| 6 | Logic Collapse & Recovery | Very High | ✅ Stable |
|
||
| 7 | Memory Breaks Across Sessions | High | ✅ Stable |
|
||
| 8 | Debugging Black Box | Medium | ✅ Stable |
|
||
| 9 | Entropy Collapse | High | ✅ Stable |
|
||
| 10 | Creative Freeze | Medium | ✅ Stable |
|
||
| 11 | Symbolic Collapse | Very High | ✅ Stable |
|
||
| 12 | Philosophical Recursion | Very High | ✅ Stable |
|
||
| 13 | Multi-Agent Chaos | Very High | ✅ Stable |
|
||
| 14 | Bootstrap Ordering | Medium | ✅ Stable |
|
||
| 15 | Deployment Deadlock | High | ⚠️ Beta |
|
||
| 16 | Pre-Deploy Collapse | Medium-High | ✅ Stable |
|
||
|
||
\*Distance from default LLM behavior to a production-ready fix.
|
||
</details>
|
||
|
||
---
|
||
|
||
## Contributing / support
|
||
- Open an **Issue** with a minimal repro (inputs → calls → wrong output).
|
||
- PRs for clearer docs, repros, or patches are welcome.
|
||
- WFGY Project home: [github.com/onestardao/WFGY](https://github.com/onestardao/WFGY)
|
||
- TXT OS: [github.com/onestardao/WFGY/tree/main/OS](https://github.com/onestardao/WFGY/tree/main/OS)
|
||
- If this map helped you, a ⭐ helps more devs find it.
|
||
|
||
|
||
---
|
||
|
||
### 🧭 Explore More
|
||
|
||
| Module | Description | Link |
|
||
|-----------------------|----------------------------------------------------------|----------|
|
||
| WFGY Core | Standalone semantic reasoning engine for any LLM | [View →](https://github.com/onestardao/WFGY/tree/main/core/README.md) |
|
||
| Problem Map 1.0 | Initial 16-mode diagnostic and symbolic fix framework | [View →](https://github.com/onestardao/WFGY/tree/main/ProblemMap/README.md) |
|
||
| Problem Map 2.0 | RAG-focused failure tree, modular fixes, and pipelines | [View →](https://github.com/onestardao/WFGY/blob/main/ProblemMap/rag-architecture-and-recovery.md) |
|
||
| Semantic Clinic Index | Expanded failure catalog: prompt injection, memory bugs, logic drift | [View →](https://github.com/onestardao/WFGY/blob/main/ProblemMap/SemanticClinicIndex.md) |
|
||
| Semantic Blueprint | Layer-based symbolic reasoning & semantic modulations | [View →](https://github.com/onestardao/WFGY/tree/main/SemanticBlueprint/README.md) |
|
||
| Benchmark vs GPT-5 | Stress test GPT-5 with full WFGY reasoning suite | [View →](https://github.com/onestardao/WFGY/tree/main/benchmarks/benchmark-vs-gpt5/README.md) |
|
||
|
||
|
||
---
|
||
|
||
> 👑 **Early Stargazers: [See the Hall of Fame](https://github.com/onestardao/WFGY/tree/main/stargazers)** —
|
||
> Engineers, hackers, and open source builders who supported WFGY from day one.
|
||
|
||
> <img src="https://img.shields.io/github/stars/onestardao/WFGY?style=social" alt="GitHub stars"> ⭐ Help reach 10,000 stars by 2025-09-01 to unlock Engine 2.0 for everyone ⭐ <strong><a href="https://github.com/onestardao/WFGY">Star WFGY on GitHub</a></strong>
|
||
|
||
|
||
<div align="center">
|
||
|
||
[](https://github.com/onestardao/WFGY)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS/BlahBlahBlah)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS/BlotBlotBlot)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS/BlocBlocBloc)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS/BlurBlurBlur)
|
||
|
||
[](https://github.com/onestardao/WFGY/tree/main/OS/BlowBlowBlow)
|
||
|
||
</div>
|
||
|