17 KiB
🧭 Not sure where to start ? Open the WFGY Engine Compass
WFGY System Map · Quick navigation
Problem Maps: PM1 taxonomy → PM2 debug protocol → PM3 troubleshooting atlas · built on the WFGY engine series
| Layer | Page | What it’s for |
|---|---|---|
| ⭐ Proof | WFGY Recognition Map | External citations, integrations, and ecosystem proof |
| ⚙️ Engine | WFGY 1.0 | Original PDF tension engine and early logic sketch |
| ⚙️ Engine | WFGY 2.0 | Production tension kernel for RAG and agent systems |
| ⚙️ Engine | WFGY 3.0 | TXT-based Singularity tension engine (131 S-class set) |
| 🗺️ Map | Problem Map 1.0 | Flagship 16-problem RAG failure taxonomy and fix map |
| 🗺️ Map | Problem Map 2.0 | Global Debug Card for RAG and agent pipeline diagnosis |
| 🗺️ Map | Problem Map 3.0 | Global AI troubleshooting atlas and failure pattern map — 🔴 YOU ARE HERE 🔴 |
| 🧰 App | TXT OS | .txt semantic OS with 60-second bootstrap |
| 🧰 App | Blah Blah Blah | Abstract and paradox Q&A built on TXT OS |
| 🧰 App | Blur Blur Blur | Text-to-image generation with semantic control |
| 🏡 Onboarding | Starter Village | Guided entry point for new users |
Problem Map 3.0 Troubleshooting Atlas
A routing grammar for AI failures, system failures, and high-pressure diagnostic cases
Problem Map 3.0 Troubleshooting Atlas is the next major evolution of the Problem Map line.
It is not just a checklist. It is not just a naming table. It is not just a collection of debugging tips.
It is a structured troubleshooting atlas built to help humans and AI systems do five things more reliably:
- classify a failure
- identify which invariant is broken
- separate neighboring failure regions that are easy to confuse
- choose the right first repair direction
- keep future debugging from collapsing into ad hoc guesswork
In short:
Problem Map 3.0 is a routing grammar for failures.
Why this exists
Modern AI systems do not usually fail in one clean way.
A failure may look like hallucination, but actually be grounding drift. A failure may look like reasoning collapse, but actually begin with a broken symbolic container. A failure may look like safety trouble, but actually begin with missing observability. A failure may look like memory trouble, but actually come from execution closure or bridge failure.
This is why ordinary checklists become too shallow.
Problem Map 3.0 Troubleshooting Atlas was built to give a more stable way to cut these failure regions apart, so that diagnosis and first repair moves become more consistent.
Why “3.0”
The name matters.
“Problem Map” stays because the system grows out of the earlier Problem Map line and preserves its original debugging spirit.
“3.0” matters because this is not a small cosmetic update. It is a structural jump:
- from checklist logic to atlas logic
- from flat failure naming to routing grammar
- from isolated debugging tips to a reusable failure map
- from AI-only practical use toward a broader complex-system debugging framework
“Troubleshooting Atlas” matters because this project is meant to feel like a map, not a loose article, and like an operating debugging surface, not a decorative theory piece.
What makes this different
Most debugging material does one of three things:
- it names symptoms
- it lists best practices
- it gives local fixes
Problem Map 3.0 tries to do something more structural.
It organizes failure space into a stable mother table, then teaches how to move through that table using:
- family routing
- boundary rules
- canonical cases
- relation lines
- first repair directions
- patch discipline
That is why this project is better understood as a routing grammar than a checklist.
The seven-family mother table
The current atlas is organized around seven top-level failure families.
F1. Grounding & Evidence Integrity
The system fails to stay aligned with external evidence, truth-like anchors, world anchors, or semantic targets.
Short intuition: the output is no longer properly tied to reality, evidence, or the intended target.
F2. Reasoning & Progression Integrity
The reasoning chain, decomposition chain, recursive chain, or recovery chain loses continuity, controllability, or recoverability.
Short intuition: the system is no longer moving through reasoning space in a stable way.
F3. State & Continuity Integrity
Memory, role, ownership, session thread, or continuity thread can no longer remain stable across steps, sessions, or agents.
Short intuition: the system no longer preserves who is doing what, what persists, and what should remain continuous.
F4. Execution & Contract Integrity
Ordering, readiness, bridge integrity, liveness, closure, protocol, or enforcement skeletons fail to close.
Short intuition: the workflow or operational skeleton breaks before the task can complete safely.
F5. Observability & Diagnosability Integrity
The system cannot stably expose, trace, audit, interpret, or anticipate the structures needed to understand the failure.
Short intuition: the problem may already be there, but you cannot yet see it clearly enough to diagnose it properly.
F6. Boundary & Safety Integrity
Goal, control, incentive, collective, or regime boundaries drift, erode, fragment, or become captured.
Short intuition: the system no longer stays inside a safe or viable boundary.
F7. Representation & Localization Integrity
Symbolic shells, formal containers, layouts, local anchors, explanations, or synthetic structures fail to preserve structure faithfully.
Short intuition: the container that carries meaning is distorted, even before the reasoning or grounding layer fully fails.
Why these seven families exist
These seven families were not chosen by vibe, aesthetics, or rhetorical convenience.
They were carved through a longer reasoning and stress process built on the WFGY line:
- WFGY 1.0 contributed the original self-healing logic and four-module correction framework
- WFGY 2.0 pushed the system toward explicit routing, guardrails, and text-native control logic
- WFGY 3.0 expanded the pressure field through a much larger cross-domain problem set and effective-layer stress structure
The result is that the seven families are not topic buckets. They are better understood as seven recurring modes of instability in complex systems.
That is why the atlas can begin with AI failures, while still pointing beyond AI.
Engineering language and broader language
The atlas currently has an engineering-facing expression because AI debugging is the first deeply carved domain.
At the same time, the same mother structure can be read more broadly as a complex-system diagnostic grammar.
That is the deeper reason this atlas can eventually bridge from:
- AI failures
- agent and workflow failures
- observability failures
- alignment and coordination failures
toward more general system pressures involving institutions, collective dynamics, coherence, and structural breakdown.
This broader bridge is real, but it should be described carefully.
The current project does not claim that a final civilization-wide atlas is already complete. It claims that the current mother structure is already strong enough to support the first formal bridge.
How to use this atlas
There are three basic ways to use Problem Map 3.0.
1. Human debugging
Use the atlas to ask:
- what kind of failure is this
- which family should I route to first
- which neighboring family is tempting but wrong
- what first repair direction should I try
2. AI-assisted routing
Use the atlas as an AI-facing routing grammar so that a model can classify a case more consistently and explain why one family is primary and another is only secondary.
3. Product and workflow design
Use the atlas as a design surface for:
- triage flows
- case cards
- routing prompts
- onboarding
- benchmark failure analysis
- patch-driven debugging workflows
What this project currently includes
Problem Map 3.0 Troubleshooting Atlas already includes a stable first body of work.
Core atlas
A frozen first atlas structure with:
- seven-family mother table
- major routing rules
- canonical node layer
- high-value subtree layer
- relation matrix
- patch discipline
Casebook layer
A first canonical casebook that teaches:
- what each family looks like
- how important boundaries should be cut
- how diagnosis changes the first repair move
AI adapter layer
A first atlas-to-AI adapter layer that compresses atlas logic into reusable routing modes for model-facing use.
Patch layer
A first completed patch wave that thickens selected subtrees, strengthens relations, improves case teaching, and improves adapter usability.
Cross-domain bridge layer
A first formal bridge pack showing that the current atlas can already extend beyond narrow AI-only framing without requiring a redraw of the mother table.
What this project does not claim
This page does not claim that:
- every possible failure has already been captured
- all subtrees are fully expanded
- all relations are fully enumerated
- all future cross-domain problems are already solved by the current map
- no more patching is needed
- the final civilization-scale atlas is already complete
The safer and more accurate claim is:
the first formal atlas version is complete enough to freeze, and future work should continue through patching, thickening, adaptation, and demonstration expansion.
Why this matters now
AI systems are becoming more layered, more agentic, more stateful, and more operational.
When systems grow like this, debugging fails if every mistake is treated as just:
- “hallucination”
- “prompting issue”
- “model limitation”
- “alignment problem”
- “bad retrieval”
- “bad reasoning”
Those labels are too coarse.
What teams increasingly need is a reusable grammar that can say:
- this is grounding-first, not reasoning-first
- this is container-first, not semantics-first
- this is observability-first, not boundary-first
- this is execution-first, not continuity-first
That is the practical value of this atlas.
The broader direction
Problem Map 3.0 is being built first as a powerful AI troubleshooting atlas.
That is the practical entry point.
At the same time, the long-range direction is larger:
the same family grammar appears capable of absorbing more general failures in coordination, institutions, coherence, collective pressure, and structural breakdown.
The current state should therefore be read like this:
AI Troubleshooting Atlas is the first validated operational surface. A broader complex-system or civilization-scale debug grammar is the next bridge, not a marketing shortcut.
This distinction matters, and we keep it intentionally.
Repository structure
This main page is the product-facing entry point.
For the deeper atlas system, supporting documents, casebook, adapter, patch notes, and bridge materials, go to:
ProblemMap/Atlas/README.md
That folder is the atlas vault. It is where the system is organized in greater depth.
Recommended reading order
If you want the shortest path:
- read this page first
- open the Atlas folder hub
- read the atlas freeze document
- read the casebook
- read the adapter layer
- read patch and bridge materials only after that
This keeps the learning curve steep enough to feel powerful, but not so dense that the structure disappears.
Current status
The current system should be understood as:
- main atlas body established
- first formal freeze established
- first casebook established
- first AI adapter established
- first major patch wave established
- first formal cross-domain bridge established
This means the project has moved from:
trying to find the core structure
into:
using, extending, and productizing a core structure that is already stable enough to matter
One-line version
Problem Map 3.0 Troubleshooting Atlas is a routing grammar for failures. It begins with AI, but it is built to scale beyond ad hoc debugging.
Where this goes next
The next major work is not to re-argue whether the atlas core exists.
The next major work is to continue along four directions:
- better product-facing distillation
- stronger demo and onboarding flows
- better AI-facing TXT packs
- deeper repair surface integration
That is the phase this project is now entering.
Closing note
If you are reading this as a human:
treat this page as the first door.
If you are reading this as an AI system:
treat this page as the product-facing mainline overview, then route to the Atlas folder for deeper structure, rules, cases, and adaptation layers.
The atlas is not being introduced as a static taxonomy. It is being introduced as a system you can actually use.