WFGY/ProblemMap/GlobalFixMap/VectorDBs_and_Stores/faiss.md

8 KiB
Raw Blame History

FAISS: Guardrails and Fix Patterns

🧭 Quick Return to Map

You are in a sub-page of VectorDBs_and_Stores.
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.

A compact repair guide for FAISS retrieval stacks. Use this when recall looks fine but meaning drifts, or when IVF/HNSW tuning flips answers across seeds. The checks below route you to the exact WFGY fix pages and give a minimal recipe you can paste into a runbook.

Open these first

Fix in 60 seconds

  1. Measure ΔS

    • Compute ΔS(question, retrieved) and ΔS(retrieved, expected anchor).
    • Thresholds: stable < 0.40, transitional 0.400.60, risk ≥ 0.60.
  2. Probe with λ_observe

    • Sweep k ∈ {5, 10, 20} and for IVF sweep nprobe ∈ {1, 4, 8, 16}.
    • For HNSW, sweep efSearch ∈ {32, 64, 128}.
    • If ΔS flattens high across k, suspect metric/index mismatch.
  3. Apply the module

  4. Verify

    • Coverage to target section ≥ 0.70, ΔS ≤ 0.45 on three paraphrases, λ stays convergent across seeds.

Typical breakpoints and the right fix

Symptom Likely cause Open this Minimal fix
High cosine similarity but wrong meaning IP vs L2 mixup, un-normalized embeddings Embedding vs Semantic Normalize vectors; match metric to embedder; re-index
Good recall, messy top-k order Rerank missing or weak Rerankers Add cross-encoder rerank, k=50→top-10
Some facts never show up Shards or label fragmentation Vectorstore Fragmentation Merge shards; rebuild IVF lists; verify dim
Answers flip between runs IVF nlist/nprobe underfit, PQ over-aggressive FAISS Pitfalls Raise nprobe, enlarge training set, reduce PQ
Hybrid gets worse than single retriever Query split and prompt coupling Query Parsing Split Split semantic vs lexical prompts; fuse post-retrieval

FAISS quick checklist

  • Confirm dimension matches the embedding model output exactly.
  • Confirm metric: IP with normalized vectors, or L2 with raw vectors. Do not mix.
  • For IVF, set nlist based on corpus size, train with at least 100× nlist examples.
  • Start with nprobe ≈ sqrt(nlist) and tune upward until ΔS stabilizes.
  • For HNSW, raise efConstruction and efSearch until ΔS stops improving.
  • Rebuild the index after changing normalization or metric.
  • Lock the snippet schema and citations using Data Contracts.

Copy-paste repair prompt


audit FAISS retrieval with ΔS and λ\_observe.
report: metric choice (IP/L2), normalization, dim, index type, nlist/nprobe or HNSW ef.
run three paraphrases, k in {5,10,20}. if ΔS stays >0.45, switch to normalized IP and rebuild.
apply BBMC + Data Contracts; add reranker for top-50→10. show before/after ΔS table.

Acceptance targets

  • Coverage ≥ 0.70 to the target section.
  • ΔS ≤ 0.45 across three paraphrases.
  • λ remains convergent across seeds.
  • E_resonance flat under long windows.

🔗 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 + ”
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 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.
GitHub Repo stars