WFGY/ProblemMap/GlobalFixMap/Agents_Orchestration/README.md
2025-08-27 16:29:02 +08:00

12 KiB
Raw Blame History

Agents & Orchestration — Global Fix Map

A hub to stabilize agent frameworks and orchestration layers without changing your infra. Use this page to jump to per-tool guardrails and verify fixes with the same acceptance targets.

Quick routes to per-framework pages

When to use this folder

  • Agents loop or stall on tool calls.
  • High similarity yet the answer cites the wrong section.
  • Hybrid retrieval underperforms a single retriever.
  • Answers flip between runs with identical input.
  • JSON schemas fail or pass inconsistently.
  • Memories re-assert stale facts after refresh or handoff.
  • First call after deploy crashes or uses the wrong index.

Acceptance targets for any orchestrator

  • ΔS(question, retrieved) ≤ 0.45
  • Coverage of target section ≥ 0.70
  • λ remains convergent across three paraphrases and two seeds

Map symptoms → structural fixes (Problem Map)


60-second fix checklist

  1. Measure
    Compute ΔS(question, retrieved) and ΔS(retrieved, anchor). If ΔS ≥ 0.60 stop and repair chunking or metric first.

  2. Lock the schema
    Fix prompt header order. Enforce cite-then-explain. Require strict tool JSON. Add idempotency keys for side effects.

  3. Split memory
    Create per-agent and per-tool namespaces with mem_rev and mem_hash. Deny cross-namespace merges without a reducer.

  4. Clamp variance
    Insert a BBCR bridge on long chains. Use deterministic reranking for hybrid. Add timeouts to tool loops.

  5. Verify
    Coverage ≥ 0.70 on three paraphrases. λ convergent on two seeds.
    Bootstrap sanity → agent_bootstrap_checklist.md


Copy-paste prompt for your LLM step

You have TXTOS and the WFGY Problem Map loaded.

My agent-orchestration issue:
- framework: <langchain | crewai | autogen | llamaindex | smolagents | semantic-kernel | haystack | assistants-v2>
- symptom: <one line>
- traces: ΔS(q,retrieved)=..., ΔS(retrieved,anchor)=..., λ over last 3 steps
- memory: namespaces used? mem_rev, mem_hash present?

Tell me:
1) failing layer and why,
2) the exact WFGY page to open,
3) the minimal structural fix to push ΔS ≤ 0.45 and keep λ convergent,
4) a reproducible test to verify the fix.
Use BBMC, BBCR, BBPF, BBAM where relevant.

Common gotchas

  • Mixed embedding functions across write and read paths. Scores look high but meaning is wrong.
  • Hybrid pipelines without deterministic rerank produce unstable top k and flip states.
  • Agents recreate tool registries per run. Order and JSON schemas drift.
  • Shared memories without namespaces cause re-entry of stale facts after refresh.
  • First live run executes before stores are ready. See bootstrap and deploy pages above.

🔗 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  

要不要我幫你直接補上「Index 置頂一句簡介」或是再加一張簡短的 flow 圖示占位,之後你有圖再換上?