WFGY/ProblemMap/GlobalFixMap/MemoryLongContext

Memory & Long-Context — Global Fix Map

🏥 Quick Return to Emergency Room

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

• WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
• WFGY Problem Map 1.0 — 16 reproducible failure modes

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

Stabilize long windows and multi-session memory.
This map helps you repair drift, collapse, forks, and ghost contexts when conversations or documents stretch far beyond the usual size.

---

What this page is

• A beginner-friendly checklist for long contexts and multi-day sessions.
• Copy-paste guardrails that stop drift and collapse before they spread.
• Concrete metrics with ΔS and λ_observe so you know if your system is stable.

---

When to use

• Dialog grows past 50k–100k tokens and answers degrade.
• Facts flip after tab refresh or model switch.
• Citations look right but reasoning goes flat or chaotic.
• OCR transcripts look fine but capitalization or spacing drift.
• Multi-day support threads lose task state or rewrite history.

---

Orientation: quick routes

Page	What it solves	Typical symptom
memory-coherence.md	Memory fences & continuity	Threads repeat or contradict
entropy-collapse.md	Attention melt in long windows	Outputs drift into filler
context-drift.md	Long reasoning drift	Correct early, wrong later
pattern_memory_desync.md	Cross-tab & cache hazards	State flips after refresh
ghost-context.md	Stale buffers & residue	Model recalls “phantom” text
state-fork.md	Divergent memory forks	Same task_id, different answers
ocr-parsing-checklist.md, ocr-jitter.md	OCR-specific noise	Exported text drifts vs. original
retrieval-traceability.md, data-contracts.md	Traceability & audit	Citations break or vanish
chunking-checklist.md	Chunk stability at joins	Mid-sentence cuts or overlaps

---

Acceptance targets

• Retrieval coverage ≥ 0.70 to the intended section
• ΔS(question, retrieved) ≤ 0.45 and joins ≤ 0.50
• λ_observe remains convergent across 3 paraphrases
• No state fork across tabs or agents for the same task_id

---

60-second fix checklist

1. Lock metrics — same analyzer & embeddings across sessions.
2. Enforce memory fences — require task_id, session_id, and snippet_id.
3. Probe ΔS and λ — run 3 paraphrases × 2 seeds.
4. Patch drift — realign chunks, re-check OCR, drop ghost spans.
5. Audit consistency — run traceability logs and verify continuity across restarts.

---

🔗 Quick-Start Downloads (60 sec)

Tool	Link	3-Step Setup
WFGY 1.0 PDF	Engine Paper	1️⃣ Download · 2️⃣ Upload · 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 it’s 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	Grandma’s 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.