Haystack Agents

🧭 Quick Return to Map

You are in a sub-page of Agents & Orchestration.
To reorient, go back here:

• Agents & Orchestration — orchestration frameworks and guardrails
• 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 desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.

Use this when your pipeline is built with deepset Haystack Agents and Tools and you observe wrong snippets, unstable top k orders, tool loops, or citation gaps. The map below routes symptoms to exact WFGY fixes.

Open these first

• Visual map and recovery: RAG Architecture & Recovery
• Retrieval knobs: Retrieval Playbook
• Traceability schema: Retrieval Traceability
• Schema contracts: Data Contracts
• Hybrid control: Rerankers
• Chunking and hallucination: Hallucination

Core acceptance

• ΔS(question, retrieved) ≤ 0.45
• Coverage ≥ 0.70 for the intended section
• λ convergent across three paraphrases

---

Fix in 60 seconds

1. Measure ΔS
   Compare question to retrieved and to the intended anchor.

2. Lock the pipeline
   Fix the header order. Enforce cite-first. Require strict tool JSON.

3. Apply the module

• Retrieval drift → BBMC plus Data Contracts
• Order instability → add Rerankers with explicit metric
• Hybrid regression → Query Parsing Split

4. Verify
   Three paraphrases pass ΔS and coverage thresholds.

---

Typical Haystack breakpoints → exact fixes

• Retriever pipelines mix different analyzers
  Rebuild with a unified analyzer and metric.
  Open: Embedding ≠ Semantic

• Agent loops on tool outputs
  Add BBCR bridge steps and timeouts.
  Open: Multi-Agent Problems

• Citations missing or misaligned
  Enforce snippet schema and cite then explain.
  Open: Retrieval Traceability, Data Contracts

• Hybrid search underperforms
  Use deterministic reranking with score normalization.
  Open: Rerankers

---

Minimal Haystack agent pattern with WFGY gate

Pipeline:
  - Retriever(k sweep 5, 10, 20 with one analyzer)
  - Prompt with fixed headers: system → task → constraints → citations → answer
  - Model call
  - WFGY gate to compute ΔS and log λ
  - Stop when ΔS ≥ 0.60 or λ divergent and return fix tip

---

Gotchas

• Mixing BM25 and dense without normalization gives unstable orders.
• Tool output not validated causes downstream JSON errors.
• Document stores with heterogeneous tokenization contaminate scores.

---

When to escalate

• Persistent ΔS ≥ 0.60 after chunk and metric fixes Open: Retrieval Playbook

• Live flips between runs Open: Pre-Deploy Collapse

---

🔗 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.