WFGY/ProblemMap/GlobalFixMap/DevTools_CodeAI
2025-09-01 19:24:22 +08:00
..
checklists Create .gitkeep 2025-08-25 19:11:17 +08:00
eval Create .gitkeep 2025-08-25 19:12:08 +08:00
mvp_demo Create .gitkeep 2025-08-25 19:11:56 +08:00
ops Create .gitkeep 2025-08-25 19:12:18 +08:00
patterns Create .gitkeep 2025-08-25 19:10:30 +08:00
playbooks Create .gitkeep 2025-08-25 19:11:33 +08:00
tools Create .gitkeep 2025-08-25 19:10:56 +08:00
.gitkeep Create .gitkeep 2025-08-25 19:10:18 +08:00
aws_codewhisperer.md Create aws_codewhisperer.md 2025-08-28 12:38:20 +08:00
codeium.md Create codeium.md 2025-08-28 13:01:01 +08:00
cursor.md Create cursor.md 2025-08-28 12:14:07 +08:00
github_copilot.md Create github_copilot.md 2025-08-28 12:02:56 +08:00
jetbrains_ai_assistant.md Create jetbrains_ai_assistant.md 2025-08-28 13:30:17 +08:00
README.md Update README.md 2025-09-01 19:24:22 +08:00
sourcegraph_cody.md Create sourcegraph_cody.md 2025-08-28 12:38:48 +08:00
tabnine.md Create tabnine.md 2025-08-28 13:21:01 +08:00
vscode_copilot_chat.md Create vscode_copilot_chat.md 2025-08-28 12:26:25 +08:00

DevTools · Code AI — Global Fix Map

A hub to stabilize IDE copilots and code-AI assistants without changing infra.
Every tool has its own guardrail page. Each target here has simple explanations so even new users can follow.


When to use this folder

  • Unstable answers: IDE chat gives different results on the same question.
  • Loops or stalls: Tool calls stop halfway or keep retrying after edits.
  • Broken JSON: You expect JSON output but get plain text.
  • Wrong citations: Answer looks correct but cites the wrong part of code/docs.
  • Drift in long refactors: After 20–40 reasoning steps, output drifts off track.

Acceptance targets (with plain meaning)

  • ΔS (semantic drift score) ≤ 0.45
    How far the answer drifts from your question. Lower is better.
  • Coverage ≥ 0.70
    How much of the correct section is included in the answer.
  • λ (stability factor) stays convergent
    If you re-ask with small rephrasing, results stay consistent.
  • E_resonance flat
    On long sessions, answers do not wander or change meaning.

Quick routes to per-tool pages

Tool Open this page
GitHub Copilot github_copilot.md
Cursor cursor.md
Sourcegraph Cody sourcegraph_cody.md
VS Code Copilot Chat vscode_copilot_chat.md
Codeium codeium.md
Tabnine tabnine.md
AWS CodeWhisperer aws_codewhisperer.md
JetBrains AI Assistant jetbrains_ai_assistant.md

Map symptoms → structural fixes

Symptom Why it happens Fix page
Wrong-meaning hits despite high similarity Embedding captures surface form but not real meaning. embedding-vs-semantic.md
Citations do not line up Traceability layer too loose, snippet schema missing. retrieval-traceability.md · data-contracts.md
Answers flip between sessions/tabs Context not anchored, entropy builds up. context-drift.md · entropy-collapse.md
JSON mode breaks, prose returned Model leaves structured mode or prompt injection occurs. logic-collapse.md · prompt-injection.md
Multi-agent or tool handoff stalls Agents lose roles, no schema lock in exchange. Multi-Agent_Problems.md · role-drift.md
Hybrid retrievers worse than single Query parsing split or reranker mis-weighted. pattern_query_parsing_split.md · rerankers.md

Fix in 60 seconds

  1. Measure ΔS
    If drift ≥ 0.60, you have unstable retrieval.
  2. Probe λ
    Re-ask with 2–3 paraphrases. If answers flip, lock schema.
  3. Apply guardrails
  4. Verify
    Coverage ≥ 0.70, λ stable, ΔS ≤ 0.45.

Copy-paste prompt for IDE chat


I loaded TXT OS and the WFGY Problem Map.

My code-AI issue:

* symptom: \[one line]
* traces: ΔS(question,retrieved)=..., ΔS(retrieved,anchor)=..., λ states

Tell me:

1. failing layer and why,
2. the exact WFGY page to open,
3. minimal steps to push ΔS ≤ 0.45 and keep λ convergent,
4. how to verify with a reproducible test.


FAQ

Q1. What is ΔS?
It is the “semantic drift score”. Think of it as how far the answer strays from the original question. Lower numbers = more accurate.

Q2. What is λ (lambda)?
A stability check. If you slightly rephrase the same question, λ shows if the model’s answers converge or scatter.

Q3. What does E_resonance mean?
It is a long-run stability check. If E_resonance is flat, your assistant stays consistent even after many steps.

Q4. Do I need to understand BBMC/BBPF/BBCR/BBAM?
No. These are internal WFGY modules. Just know:

  • BBMC = stabilizes retrieval,
  • BBPF = creates fallback paths,
  • BBCR = bridges reasoning collapse,
  • BBAM = variance clamp for stability.

Q5. I only use one IDE plugin. Why should I care?
Because the same drift and instability happens across all copilots. Fixes here apply no matter which tool you use.

Q6. How do I test quickly?
Ask the same question 3 times with small wording changes. If answers flip, you need λ guardrails.


🔗 Quick-Start Downloads (60 sec)

Tool Link 3-Step Setup
WFGY 1.0 PDF Engine Paper 1️⃣ Download · 2️⃣ Upload to your LLM · 3️⃣ Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS) TXTOS.txt 1️⃣ Download · 2️⃣ Paste into any LLM chat · 3️⃣ Type “hello world” — OS boots instantly

🧭 Explore More

Module Description Link
WFGY Core WFGY 2.0 engine is live: full symbolic reasoning architecture and math stack View →
Problem Map 1.0 Initial 16-mode diagnostic and symbolic fix framework View →
Problem Map 2.0 RAG-focused failure tree, modular fixes, and pipelines View →
Semantic Clinic Index Expanded failure catalog: prompt injection, memory bugs, logic drift View →
Semantic Blueprint Layer-based symbolic reasoning & semantic modulations View →
Benchmark vs GPT-5 Stress test GPT-5 with full WFGY reasoning suite View →
🧙‍♂️ Starter Village 🏡 New here? Lost in symbols? Click here and let the wizard guide you through Start →

👑 Early Stargazers: See the Hall of Fame —
GitHub stars ⭐ WFGY Engine 2.0 is already unlocked. ⭐ Star the repo to help others discover it and unlock more on the Unlock Board.

WFGY Main   TXT OS   Blah   Blot   Bloc   Blur   Blow