Eval Observability

March 6, 2026 · View on GitHub

🧭 Quick Return to Map

You are in a sub-page of Eval_Observability.
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 (λ_observe)
λ_observe is a heuristic stability signal defined inside the WFGY framework.
It helps you notice drift and volatility but is not a formal guarantee of long term robustness.


A core probe for evaluating semantic convergence across multiple seeds, paraphrases, and retrieval variations.
While ΔS measures semantic distance, λ_observe captures stability vs divergence of reasoning paths.


Why λ_observe matters

  • Detect fragile reasoning: Even when ΔS looks safe, λ divergence indicates unstable chains.
  • Identify paraphrase sensitivity: If λ flips across harmless rewordings, the system is brittle.
  • Audit retrieval randomness: Different seeds producing opposite λ signals reveal weak schema.
  • Ensure eval reproducibility: Stable λ means tests repeat reliably under small perturbations.

λ state encoding

SymbolMeaningExample failure
Forward convergence, stable pathSame citations and reasoning across paraphrases
Backward collapse, early abortTool call retries, empty citations
<>Split state, partial divergenceOne paraphrase cites correct snippet, others miss
×Total collapseRandom answers, no citation alignment

Acceptance targets

  • Convergence rate ≥ 0.80 across 3 paraphrases × 2 seeds.
  • No × states tolerated in gold-set eval.
  • Split states (<>): ≤ 10% of test cases acceptable.
  • Forward (→) must dominate stable runs.

Evaluation workflow

  1. Run triple paraphrase probe
    Ask the same question three ways. Collect λ states.
  2. Repeat with two seeds
    Track variance.
  3. Roll-up stats
    Compute convergence ratio, collapse frequency, divergence rate.
  4. Escalation
    If λ <0.80 or × >0%, run root-cause: schema audit, retriever split, prompt ordering.

Example probe schema

{
  "query_id": "Q42",
  "runs": [
    {"paraphrase": 1, "seed": 123, "λ": "→"},
    {"paraphrase": 2, "seed": 123, "λ": "→"},
    {"paraphrase": 3, "seed": 123, "λ": "<>"},
    {"paraphrase": 1, "seed": 456, "λ": "→"},
    {"paraphrase": 2, "seed": 456, "λ": "×"},
    {"paraphrase": 3, "seed": 456, "λ": "→"}
  ]
}

Common pitfalls

  • Only measuring ΔS → misses hidden divergence.
  • Seed-fixed eval → looks stable but fragile in production.
  • Ignoring split states → small divergence often grows into collapse.
  • No per-query logs → averages hide catastrophic single failures.

Reporting recommendations

  • λ distribution table: % of →, ←, <>, ×.
  • Convergence trend: chart over time by eval batch.
  • Drift alerts: trigger if convergence <0.80 or × appears.
  • Correlation: track ΔS vs λ to spot mixed failures.

🔗 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