Reasoning

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: a

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

A compact hub to keep long chains stable, prevent collapse, and make decisions auditable.
Use this folder when answers drift across runs, chains dead end, or the model rewrites reality during long plans.
Every page maps symptoms to exact WFGY fixes with measurable targets. No infra change required.


Orientation: what each page solves

PageWhat it fixesTypical symptom
Entropy OverloadCaps branching and token wanderSteps keep growing, plan never lands
Recursive LoopBreaks self reference loopsChain circles back to the same step
Hallucination Re entryPrevents re asserting wrong claimsModel repeats a false claim after correction
Logic CollapseRebuilds structure and legal jumpsJumps without citing the step that caused it
Symbolic CollapseGuards abstraction changesFrame jump breaks meaning, invariants vanish
Proof Dead EndsAdds pivots and escape hatchesChain stalls at an unprovable step
Anchoring and Bridge ProofsBuilds safe bridges across framesNeed to cross domains without losing semantics
Context Stitching and Window JoinsStabilizes long windows and joinsWindow roll drops the anchor or flips the claim
Chain of Thought Variance ClampMakes reruns agreeReruns disagree because thoughts wander
Redundant Evidence CollapseBalances majority and minority factsToo many similar snippets drown the truth

When to use this folder

  • Multi step answers change when you rerun the same prompt
  • Chains go in circles or re assert a claim after correction
  • Logic jumps without citing the source that drove the jump
  • Long chats lose earlier anchors when the window rolls
  • Plans grow without bound and never converge

Acceptance targets

  • ΔS(question, selected_evidence) ≤ 0.45 on all runs
  • Coverage of the target section ≥ 0.70 with cite then explain
  • λ_observe convergent across three paraphrases and two seeds
  • E_resonance flat across long windows and at window joins
  • Deterministic step count for plan stages after clamps

Fast triage by symptom

SymptomOpen this
Steps keep growing, answer never landsEntropy Overload
Chain circles back to earlier stepRecursive Loop
Model re asserts the wrong claim after you fix itHallucination Re entry
Reasoning jumps without structure, loses invariantsLogic Collapse
Abstract move breaks semantics across framesSymbolic Collapse
Proof chain stalls at an unprovable stepProof Dead Ends
Window roll drops the anchor or flips the claimContext Stitching and Window Joins
Reruns disagree because thoughts wanderChain of Thought Variance Clamp
Too many similar snippets overpower minority factsRedundant Evidence Collapse
Need a stable bridge between two framesAnchoring and Bridge Proofs

Fix in 60 seconds

  1. Measure ΔS and observe λ
    Probe ΔS(question, selected_evidence). Sample λ across two seeds and three paraphrases.
    If ΔS ≥ 0.60 or λ flips, you have structural drift.

  2. Apply the right clamp

  3. Contract the payload and cite first
    Enforce snippet schema and cite then explain.
    Open Retrieval Traceability and Data Contracts

  4. Verify
    Coverage ≥ 0.70, ΔS ≤ 0.45, λ convergent on two seeds.
    If flat high ΔS remains, fix retrieval first with the playbook.
    Open Retrieval Playbook


Copy paste diagnostic prompt

Context: TXT OS and WFGY pages are loaded.

Task:
- For question Q, log ΔS(Q, selected_evidence) on 3 paraphrases and 2 seeds.
- Report λ states across steps, and the first point where drift starts.
- Recommend the smallest page from this folder that will clamp variance
  and recover anchors. Name the page and the exact subsection.
- Return a reproducible check that proves ΔS ≤ 0.45 and coverage ≥ 0.70.

Return JSON only:
{ "ΔS": 0.xx, "λ": "<>|→|←|×", "failing_step": "...",
  "page": "anchoring-and-bridge-proofs", "subsection": "...",
  "verify": "run X, expect Y" }


🔗 Quick-Start Downloads (60 sec)

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

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