WFGY/ProblemMap/GlobalFixMap/DocumentAI_OCR
2025-09-05 10:40:01 +08:00
..
checklists Create .gitkeep 2025-08-25 19:05:54 +08:00
eval Create .gitkeep 2025-08-25 19:06:29 +08:00
mvp_demo Create .gitkeep 2025-08-25 19:06:17 +08:00
ops Create .gitkeep 2025-08-25 19:06:39 +08:00
patterns Create .gitkeep 2025-08-25 19:05:30 +08:00
playbooks Create .gitkeep 2025-08-25 19:06:05 +08:00
tools Create .gitkeep 2025-08-25 19:05:42 +08:00
.gitkeep Create .gitkeep 2025-08-25 19:05:16 +08:00
abbyy.md Update abbyy.md 2025-09-05 10:39:31 +08:00
aws_textract.md Update aws_textract.md 2025-09-05 10:39:37 +08:00
azure_ocr.md Update azure_ocr.md 2025-09-05 10:39:42 +08:00
google_docai.md Update google_docai.md 2025-09-05 10:39:49 +08:00
paddleocr.md Update paddleocr.md 2025-09-05 10:39:55 +08:00
README.md Update README.md 2025-09-03 23:49:29 +08:00
tesseract.md Update tesseract.md 2025-09-05 10:40:01 +08:00

Document AI & OCR — Global Fix Map

🏥 Quick Return to Emergency Room

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

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

A beginner-friendly hub to stabilize OCR (Optical Character Recognition) and document AI pipelines across providers and open-source stacks.
This page helps you:

  1. Understand common OCR failures.
  2. Jump directly to per-tool guides.
  3. Apply structural WFGY fixes with measurable acceptance targets.

📌 When to use this folder

Use this map if you see any of these problems:

  • OCR extracts text but loses tables or column alignment.
  • Words are captured but semantic grouping is wrong (paragraphs broken).
  • Citations dont match the original scanned page.
  • Layout-aware models drift after format changes (e.g. headers, forms).
  • Two-column PDFs or rotated scans break retrieval.
  • Cloud OCR services return different JSON fields each run.

🎯 Acceptance targets for OCR systems

Think of these as “green lights” after your OCR step:

  • ΔS(question, extracted text) ≤ 0.45 (semantic match stays tight).
  • Coverage ≥ 0.70 of target section or table.
  • λ stays convergent across 3 paraphrases and 2 random seeds.
  • E_resonance stays flat across long documents (no drifting answers).

🚀 Quick routes — per-provider guides

Provider / Tool Open this guide
Tesseract (open-source OCR) tesseract.md
Google Document AI google_docai.md
AWS Textract aws_textract.md
Azure OCR azure_ocr.md
ABBYY (enterprise OCR) abbyy.md
PaddleOCR (open-source) paddleocr.md

🛠️ Common symptoms → exact fixes

Symptom Likely cause Fix page
High similarity but wrong snippet Embeddings confuse words with meaning embedding-vs-semantic.md
Citations dont line up with scanned region Missing traceability or weak schema retrieval-traceability.md · data-contracts.md
Multi-column / rotated pages fail Chunking instability chunking-checklist.md
Wrong OCR version after deploy Boot ordering or pre-deploy collapse bootstrap-ordering.md · predeploy-collapse.md
OCR+Vision hybrid worse than single Query parsing split issue pattern_query_parsing_split.md

60-second fix checklist

  1. Run OCR twice (two providers or seeds) → compare ΔS & λ.
  2. Validate JSON schema → enforce {page_id, bbox, text, confidence}.
  3. De-rotate scans, split multi-column before embedding.
  4. Confirm coverage ≥ 0.70 on a gold page.
  5. Force “cite then explain” in downstream reasoning steps.

FAQ (beginner-friendly)

Q: What is ΔS and why should I care?
ΔS measures semantic drift — if its above 0.45, your OCR text no longer matches the question well. Keep it lower to ensure stable answers.

Q: What does λ mean in practice?
λ checks consistency across paraphrases. If the system gives different answers for re-phrased questions, λ is unstable.

Q: Why do my citations not match the scanned PDF?
Usually because the OCR JSON has no stable IDs or coordinates. Fix by enforcing traceability fields like page_id and bbox.

Q: My OCR works on simple PDFs but fails on forms or invoices. Why?
Thats a chunking issue. Multi-column and rotated layouts need pre-processing before feeding to embeddings.

Q: Do I need to switch providers if accuracy is low?
Not always. Most errors come from pipeline design (chunking, contracts, retrieval) rather than the OCR engine itself.


🔗 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

Module Description Link
WFGY Core Semantic firewall engine (reasoning & math) View →
Problem Map 1.0 Original 16-mode fix framework View →
Semantic Clinic Index Expanded clinic: OCR, prompt injection, memory drift View →
Benchmarks vs GPT-5 OCR + reasoning stress test View →

👑 Hall of Fame: See the Stargazers who supported this from the start.

WFGY Main
TXT OS
Blah
Blot
Bloc
Blur
Blow