Retrieval

March 6, 2026 · View on GitHub

🏥 Quick Return to Emergency Room

You are in a specialist desk.
For full triage and doctors on duty, return here:

Think of this page as a sub-room.
If you want full consultation and prescriptions, go back to the Emergency Room lobby.

Evaluation disclaimer (retrieval)
All retrieval scores and examples in this section come from controlled setups with chosen corpora and prompts.
They help you compare retrieval strategies locally but are not universal rankings of models or vector stores.


A compact hub to stabilize retrieval quality across stacks, models, and stores.
Use this page to route symptoms to the exact structural fix and verify with measurable targets. No infra change required.


Orientation: what each page does

PageWhat it solvesTypical symptom
Retrieval PlaybookEnd to end rebuild order and knobsYou fixed one thing and another breaks
Retrieval TraceabilityCite-then-explain schema with required fieldsCitations miss the exact section or cannot be verified
RerankersDeterministic reranking across BM25 + ANNHybrid worse than single retriever
Query Parsing SplitOne query, two meanings; detect and routeAnswers jump between two unrelated sections
Chunk AlignmentChunking aligned with the model’s semantic windowSnippets cut mid-thought; anchors missing
ΔS ProbesQuick health check using ΔS and λ_observeLooks fine by eye but flips across runs
Retrieval Eval RecipesDeterministic, SDK-free evaluationNo stable way to tell if “better” shipped
Store-Agnostic GuardrailsLocks for metrics, analyzers, versionsIndex “healthy” but recall still low

When to use this folder

  • High similarity but wrong meaning.
  • Correct facts exist in the corpus but never show up.
  • Citations inconsistent or missing across steps.
  • Hybrid retrieval underperforms a single retriever.
  • Index looks healthy while coverage remains low.

Acceptance targets

  • ΔS(question, retrieved) ≤ 0.45
  • Coverage of target section ≥ 0.70
  • λ_observe convergent across 3 paraphrases and 2 seeds
  • E_resonance flat on long windows

Symptoms → exact fixes

SymptomLikely causeOpen this
High similarity yet wrong answerMetric or analyzer mismatchEmbedding ≠ Semantic
Correct fact never retrievedFragmentation or missing anchorsVectorstore Fragmentation · Chunking Checklist
Hybrid worse than singleQuery parsing split or mis-weighted rerankQuery Parsing Split · Rerankers
Citations missing or unstableSchema not enforcedRetrieval Traceability · Data Contracts
Answers flip between runsPrompt header reordering or λ varianceContext Drift · Rerankers

60-second fix checklist

  1. Lock metrics and analyzers
    One embedding model per field. One distance metric. Same analyzer for write and read.
    Guide: Store-Agnostic Guardrails

  2. Enforce the snippet contract
    Require snippet_id, section_id, source_url, offsets, tokens.
    Guide: Data Contracts

  3. Measure ΔS and λ
    Run three paraphrases and two seeds.
    Guide: ΔS Probes

  4. Sweep k and rerankers
    Try k in {5, 10, 20}. Keep BM25 and ANN candidate lists.
    Guide: Rerankers

  5. Rebuild where needed
    Follow the sequence in the playbook and re-test coverage.
    Guide: Retrieval Playbook


Checklists — copy before deploy

ChecklistScopeLink
Retrieval ReadinessPre-flight: embeddings, analyzers, index, gold setretrieval_readiness.md
Reranker SanityHybrid reranking health and overlap checksreranker_sanity.md
Traceability GateContract enforcement for cite-then-explaintraceability_gate.md

Vector DBs — jump if store specific


Minimal probe pack you can paste

Context: I loaded TXT OS and the WFGY pages.

Task:
- Given question "Q", log ΔS(Q, retrieved) and λ across 3 paraphrases.
- Enforce cite-then-explain with the traceability schema.
- If ΔS ≥ 0.60 or λ flips, return the smallest structural change to push ΔS ≤ 0.45 and coverage ≥ 0.70.
- Use BBMC, BBCR, BBPF, BBAM when relevant.

Return JSON:
{ "citations": [...], "ΔS": 0.xx, "λ_state": "<>", "coverage": 0.xx, "next_fix": "..." }

🔗 Quick-Start Downloads (60 sec)

ToolLink3-Step Setup
WFGY 1.0 PDFEngine Paper1️⃣ Download · 2️⃣ Upload to your LLM · 3️⃣ Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS)TXTOS.txt1️⃣ Download · 2️⃣ Paste into any LLM chat · 3️⃣ Type “hello world” — OS boots instantly

Explore More

LayerPageWhat it’s for
⭐ ProofWFGY Recognition MapExternal citations, integrations, and ecosystem proof
⚙️ EngineWFGY 1.0Original PDF tension engine and early logic sketch (legacy reference)
⚙️ EngineWFGY 2.0Production tension kernel for RAG and agent systems
⚙️ EngineWFGY 3.0TXT based Singularity tension engine (131 S class set)
🗺️ MapProblem Map 1.0Flagship 16 problem RAG failure taxonomy and fix map
🗺️ MapProblem Map 2.0Global Debug Card for RAG and agent pipeline diagnosis
🗺️ MapProblem Map 3.0Global AI troubleshooting atlas and failure pattern map
🧰 AppTXT OS.txt semantic OS with fast bootstrap
🧰 AppBlah Blah BlahAbstract and paradox Q&A built on TXT OS
🧰 AppBlur Blur BlurText to image generation with semantic control
🏡 OnboardingStarter VillageGuided entry point for new users

If this repository helped, starring it improves discovery so more builders can find the docs and tools.
GitHub Repo stars