WFGY/ProblemMap/GlobalFixMap/Eval/eval_rag_precision_recall.md

6.9 KiB
Raw Blame History

Eval RAG Precision & Recall — Guardrails and Fix Patterns

🧭 Quick Return to Map

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

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.

Evaluation disclaimer (RAG precision and recall)
Precision and recall here are computed in a controlled RAG scenario with specific data and judgement rules.
They should be used to debug retrieval behavior, not as general claims about model intelligence.


This page defines how to measure precision and recall in RAG pipelines under the WFGY framework. It sets acceptance thresholds, common pitfalls, and structural fixes to keep evaluations meaningful and reproducible.


Open these first


Acceptance targets

  • Precision ≥ 0.75 at citation level
  • Recall ≥ 0.70 of gold anchor snippets
  • ΔS(question, retrieved) ≤ 0.45 for majority of pairs
  • λ remains convergent across 3 paraphrases and 2 random seeds
  • Evaluations must be auditable & reproducible with JSON logs

Why precision/recall break in RAG

  1. Goldset drift Anchors no longer align with the corpus after updates. → Fix: refresh goldsets with goldset_curation.md.

  2. Retrieval contract missing Snippet payloads do not include section IDs or offsets. → Fix: enforce Data Contracts.

  3. Precision false positives Semantically near matches but wrong factual anchor. → Fix: rerank with Rerankers.

  4. Recall false negatives Correct snippet exists but chunking or index prevents surfacing. → Fix: re-chunk corpus with chunking-checklist.md.

  5. Evaluation noise Different seeds or paraphrases give unstable results. → Fix: clamp λ variance with variance_and_drift.md.


Quick workflow

  1. Load goldset Each gold QA item must cite snippet_id, section_id, source_url.

  2. Run retrieval Collect top-k results (k = 5, 10, 20).

  3. Log ΔS & λ For each query and paraphrase, record ΔS values and λ states.

  4. Compute metrics

    • Precision = correct citations / total citations
    • Recall = correct citations / gold references
  5. Regression gate Block deploy if precision < 0.75 or recall < 0.70.


Example JSON log

{
  "question": "What causes hallucination re-entry?",
  "gold": ["hallucination-reentry"],
  "retrieved": ["hallucination-reentry", "entropy-drift"],
  "precision": 0.50,
  "recall": 1.00,
  "ΔS": 0.38,
  "λ_state": "→"
}

Common pitfalls

  • Evaluating only precision → recall collapses unnoticed.
  • Counting fuzzy hits as correct → ΔS may be high, but factually wrong.
  • No paraphrases tested → λ instability hidden.
  • Relying on one seed → fragile numbers that dont generalize.

🔗 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 its for
Proof WFGY Recognition Map External citations, integrations, and ecosystem proof
Engine WFGY 1.0 Original PDF based tension engine
Engine WFGY 2.0 Production tension kernel and math engine for RAG and agents
Engine WFGY 3.0 TXT based Singularity tension engine, 131 S class set
Map Problem Map 1.0 Flagship 16 problem RAG failure checklist and fix map
Map Problem Map 2.0 RAG focused recovery pipeline
Map Problem Map 3.0 Global Debug Card, image as a debug protocol layer
Map Semantic Clinic Symptom to family to exact fix
Map Grandmas Clinic Plain language stories mapped to Problem Map 1.0
Onboarding Starter Village Guided tour for newcomers
App TXT OS TXT semantic OS, fast boot
App Blah Blah Blah Abstract and paradox Q and A built on TXT OS
App Blur Blur Blur Text to image with semantic control
App Blow Blow Blow Reasoning game engine and memory demo

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