9.5 KiB
Agents & Orchestration — Global Fix Map
🏥 Quick Return to Emergency Room
You are in a specialist desk.
For full triage and doctors on duty, return here:
- WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
- WFGY Problem Map 1.0 — 16 reproducible failure modes
Think of this page as a sub-room.
If you want full consultation and prescriptions, go back to the Emergency Room lobby.
Agent and orchestration bugs are structural failures in multi-agent or tool-augmented systems, where coordination, role boundaries, execution order, or control flow break down even when the underlying model behaves correctly.
Most agent failures are not caused by model quality. They arise from role mixups, tool schema drift, uncontrolled loops, shared-state collisions, and cold-boot ordering errors. This page maps observable symptoms to structural fixes with measurable acceptance targets.
Orientation: pick your orchestration layer
| Framework | What it is | Typical use | Link |
|---|---|---|---|
| Autogen | Multi-agent collaboration patterns | Debate, reviewer loops, tool arbitration | autogen.md |
| CrewAI | Role-based project crews | Task pipelines with clear roles | crewai.md |
| Haystack Agents | RAG-centric agents from deepset | Retrieval-heavy assistants | haystack_agents.md |
| LangChain | Largest ecosystem of tools/memory | Rapid prototyping, complex chains | langchain.md |
| LangGraph | Graph execution over LC | Stateful paths, loops, guards | langgraph.md |
| LlamaIndex | Knowledge-first orchestration | RAG pipelines, index control | llamaindex.md |
| OpenAI Assistants v2 | First-party assistants API | Files, tools, code-interpreter | openai_assistants_v2.md |
| Rewind Agents | Context replay paradigms | User-state reconstruction | rewind_agents.md |
| Semantic Kernel | MS orchestration SDK | Plugins, plans, .NET/TS stacks | semantic_kernel.md |
| Smolagents | Minimalistic agent runtime | Constrained envs, fast spin-up | smolagents.md |
Core acceptance targets
- ΔS(question, retrieved) ≤ 0.45
- Coverage ≥ 0.70 for the target section
- λ stays convergent across 3 paraphrases and 2 seeds
- E_resonance remains flat on long windows
These targets let you ship safely regardless of framework.
Fix Hub — symptoms mapped to structural pages
| Symptom | Likely cause | Open this |
|---|---|---|
| JSON mode breaks, invalid tool objects | Tool protocol too loose | Data Contracts |
| Agents overwrite each other’s memory | Namespace collision, missing locks | Pattern: memory-namespace split in patterns |
| Run loops never end | Unbounded cycles, missing guards | logic-collapse.md |
| High similarity yet wrong snippet | Metric/store mismatch or fragmentation | embedding-vs-semantic.md |
| Alternating answers across runs | Prompt header reorder, λ flips | context-drift.md, retrieval-traceability.md |
| First live call fails after deploy | Cold boot and ordering issues | bootstrap-ordering.md, predeploy-collapse.md |
| Tool storms and rate limits | Missing backoff and budgets | Ops: rate-limit backpressure, timeouts in ops/ |
Minimal agent contract
- Separate memory namespaces
One namespace per agent. Writes guarded bymem_revandmem_hash. - Strict tool schemas
Enforce JSON schemas. Reject free-text arguments and responses. - Path guards
Max steps, variance clamp, and illegal cross-path suppression. - Traceability first
Cite then explain. Require{snippet_id, section_id, source_url, offsets, tokens}. - Boot ordering
Do not accept traffic until index hash, analyzer, and model versions match. - Observability
Log ΔS and λ across retrieve → rerank → reason. Alert at ΔS ≥ 0.60.
60-second triage
- Measure ΔS for question vs retrieved and vs anchor.
- Probe λ by varying top-k and prompt headers. If λ flips, clamp variance and lock the schema.
- Apply
Retrieval drift → BBMC + Data Contracts
Reasoning collapse → BBCR bridge + BBAM
Dead ends → BBPF alternate paths - Verify
Coverage ≥ 0.70 on three paraphrases. λ convergent on two seeds.
FAQ
Why do agents step on each other’s memory?
Shared state without namespaces. Split memory by agent and lock writes.
Why do I get infinite loops after adding a reviewer agent?
No path guards. Add step caps and illegal cross-path suppression.
Why does tool calling randomly fail JSON?
Your tool protocol allows prose. Enforce strict JSON schemas both ways.
Why is dev stable but prod flips answers?
Boot order and analyzer mismatch. Warm the index and verify hashes before traffic.
🔗 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
| 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 (legacy reference) |
| ⚙️ 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 |
| 🧰 App | TXT OS | .txt semantic OS with fast 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 |
If this repository helped, starring it improves discovery so more builders can find the docs and tools.
