WFGY/ProblemMap/GlobalFixMap/DocumentAI_OCR/abbyy.md

ABBYY OCR (FineReader / FlexiCapture): Guardrails and Fix Patterns

🧭 Quick Return to Map

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

• DocumentAI_OCR — document parsing and optical character recognition
• 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 desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.

Use this page when ABBYY OCR powers ingestion of scanned PDFs, complex layouts, forms, or multilingual documents.
ABBYY is enterprise-grade, but still prone to schema drift, field misalignment, and unstable table anchors.

---

Open these first

• Visual map and recovery: RAG Architecture & Recovery
• Retrieval knobs: Retrieval Playbook
• Citation schema: Retrieval Traceability
• Schema stability: Data Contracts
• Embedding vs meaning: Embedding ≠ Semantic
• Hallucination and entropy drift: Hallucination, Entropy Collapse
• Chunk boundaries: Chunking Checklist

---

Core acceptance

• ΔS(question, retrieved) ≤ 0.45
• Coverage ≥ 0.70 across fields and tokens
• λ convergent on three paraphrases and two seeds
• Form fields ≥ 95% aligned with schema contract

---

Typical breakpoints → structural fix

• Form fields drift across runs (invoice totals, line items misaligned)
  → Data Contracts, Retrieval Traceability

• Table anchors collapse (multi-column invoices, receipts)
  → Chunking Checklist, clamp with BBMC

• Handwriting extraction unstable
  → Entropy Collapse

• Injected payload in OCR notes layer
  → Prompt Injection

• Multilingual contract fields mismatched
  → Embedding ≠ Semantic

---

Fix in 60 seconds

1. Enforce field schema: require field_id, bbox, confidence, revision_id.
2. Compute ΔS on critical fields (e.g. total_amount, invoice_date).
3. Apply λ probes with different template libraries.
4. Clamp instability with BBAM and log coverage.
5. Rebuild index if ΔS ≥ 0.60 persists.

---

Copy-paste LLM guard prompt

I uploaded TXTOS and the WFGY Problem Map.

OCR provider: ABBYY (FineReader / FlexiCapture).  
Symptoms: field drift, unstable tables, ΔS ≥ 0.60.

Steps:
1. Identify failing layer (contracts, chunking, retrieval).  
2. Point to the WFGY fix page.  
3. Return JSON:  
   { "fields_checked": [...], "answer": "...", "ΔS": 0.xx, "λ_state": "<>", "next_fix": "..." }  
Keep it reproducible and auditable.

---

When to escalate

• Field coverage < 0.70 even after re-chunk → Data Contracts
• Persistent anchor drift → Chunking Checklist
• Handwriting ΔS unstable across seeds → Entropy Collapse

---

🔗 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

Module	Description	Link
WFGY Core	Canonical framework entry point	View
Problem Map	Diagnostic map and navigation hub	View
Tension Universe Experiments	MVP experiment field	View
Recognition	Where WFGY is referenced or adopted	View
AI Guide	Anti-hallucination reading protocol for tools	View

If this repository helps, starring it improves discovery for other builders.