Enterprise Document Intelligence [Vol. 1 #5octies] - Rules propose, LLM validates: six deterministic signals on span-level typography surface heading candidates, one bounded loop keeps the real ones, and the same toc_df drops back into the RAG pipeline The post Building Document Structure with Loop Engineering: Recovering a PDF’s Outline from Body Typography for RAG appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #5septies] - When a PDF prints a contents page but exposes no outline, two ways to turn it back into structure, plus the page-alignment step everyone forgets The post Reconstructing the Table of Contents a PDF Forgot to Ship, So RAG Can Scope by Section appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #5B] - One PDF in, a relational set of DataFrames out: lines, pages, TOC, images, cross-references, captions, spans, and a parsing summary The post Stop Returning Flat Text from a PDF: The Relational Shape RAG Needs appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #13bis] - The four bricks return useful results most of the time.
Enterprise Document Intelligence [Vol. 1 #5A] - Document signals (metadata, native TOC, source software) and page-level content (text vs scans, tables, images, columns, page profile) The post Beyond extract_text: The Two Layers of a PDF That Drive RAG Quality appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #7quater] - A 492-page document has a 358-entry table of contents.
Enterprise Document Intelligence [Vol. 1 #5B] - One PDF in, a relational set of DataFrames out: lines, pages, TOC, images, cross-references, captions, spans, and a parsing summary The post Stop Returning Flat Text from a PDF: The Relational Tables RAG Needs appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #10A] - The escalation cascade and the free, deterministic checks that flag a failed parse before you pay for a deeper one The post Loop Engineering with Adaptive PDF Parsing: Start Cheap, Pay for a Heavier Parser Only When the Page Needs It appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #6quinquies] - Prompt engineering, then context engineering, then loop engineering.
Enterprise Document Intelligence [Vol. 1 #7bis] - Tobi Lütke and Andrej Karpathy named the practice in 2025.
Enterprise Document Intelligence [Vol. 1 #7bis] - Tobi Lütke and Andrej Karpathy named the practice in 2025.
Enterprise Document Intelligence [Vol. 1 #11] - When the first answer points elsewhere in the document, the pipeline loops back to fetch the linked context The post Loop Engineering for Cross-References: When RAG Answers ‘see Section 7.
Enterprise Document Intelligence [Vol. 1 #5quinquies] - Same 1974 scanned PDF, two engines.