Document IR - Production Document Ingestion Engine
An IR-first, extensible document compiler for AI systems.
This is NOT a PDF-to-Markdown script. It is a production-grade document ingestion and canonicalization engine designed with compiler-like architecture: Input → IR → Backends.
Architecture
Design Philosophy
Think like a compiler engineer:
- Input Layer: Format-specific parsers (currently PDF via Docling)
- AST/IR: Canonical intermediate representation with strict schema
- Backends: Multiple export formats (Markdown, Text, Parquet)
Layer Separation (Non-Negotiable)
┌─────────────────────────────────────────┐
│ Input Adapter Layer │
│ Format-specific parsing only │
└────────────────────┬────────────────────┘
│
┌────────────────────▼────────────────────┐
│ Extraction Layer │
│ Extract raw structural elements │
└────────────────────┬────────────────────┘
│
┌────────────────────▼────────────────────┐
│ Normalization Layer │
│ Convert to canonical IR with hashing │
└────────────────────┬────────────────────┘
│
┌────────────────────▼────────────────────┐
│ Canonical IR Layer │
│ Typed schema, stable IDs, relationships│
└────────────────────┬────────────────────┘
│
┌────────────────────▼────────────────────┐
│ Export Layer │
│ Markdown, Text, Parquet, Assets │
└─────────────────────────────────────────┘
Key Features
✅ Deterministic & Idempotent
- Hash-based stable IDs (document, block, table, image, chunk)
- Running pipeline twice produces identical output
- No UUIDs, no randomness
✅ Canonical IR Schema
Document
├── document_id: str (hash-based)
├── schema_version: str
├── parser_version: str
├── metadata: DocumentMetadata
├── blocks: List[Block]
│ ├── block_id: str (deterministic)
│ ├── type: BlockType (heading, paragraph, table, image, etc.)
│ ├── content: str
│ ├── page_number: int
│ ├── bbox: BoundingBox
│ └── metadata: dict
└── relationships: List[Relationship]
✅ Pluggable Chunking
SemanticSectionChunker: Section-based (headings)TokenWindowChunker: Fixed token windows with overlapLayoutAwareChunker: Layout-aware (stub)
All chunking operates on IR, not raw text.
✅ Multiple Export Formats
- Markdown: Human-readable with formatting
- Plain Text: Simple text extraction
- Parquet: Efficient structured storage for tables/blocks
- Assets: Extracted images (PNG) and tables (CSV)
✅ Structured Output
/<document_id>/
manifest.json # Processing metadata
ir.json # Canonical IR
chunks.json # Chunk definitions
/assets/
/images/ # Extracted images
/tables/ # Tables as CSV
/exports/
/markdown/ # Markdown output
/text/ # Plain text output
/parquet/ # Parquet datasets
/logs/ # Processing logs
Installation
IMPORTANT: LayoutIR requires PyTorch with CUDA 13.0 support for GPU acceleration. Install PyTorch first:
# Step 1: Install PyTorch with CUDA 13.0 (REQUIRED)
pip3 install torch torchvision --index-url https://download.pytorch.org/whl/cu130
# Step 2: Install LayoutIR
pip install layoutir
Alternative Installation Methods
# Install from source
git clone https://github.com/RahulPatnaik/layoutir.git
cd layoutir
pip3 install torch torchvision --index-url https://download.pytorch.org/whl/cu130
pip install -e .
Note: The package intentionally does not include PyTorch in its base dependencies to ensure you get the correct CUDA version. Any existing PyTorch installation will be overwritten by the CUDA 13.0 version.
Usage
Basic Usage
# Using the CLI
layoutir --input file.pdf --output ./out
# Or using Python directly
python -m layoutir.cli --input file.pdf --output ./out
Advanced Options
# Semantic chunking (default)
layoutir --input file.pdf --output ./out --chunk-strategy semantic
# Token-based chunking with custom size
layoutir --input file.pdf --output ./out \
--chunk-strategy token \
--chunk-size 1024 \
--chunk-overlap 128
# Enable GPU acceleration
layoutir --input file.pdf --output ./out --use-gpu
# Debug mode with structured logging
layoutir --input file.pdf --output ./out \
--log-level DEBUG \
--structured-logs
Python API
from pathlib import Path
from layoutir import Pipeline
from layoutir.adapters import DoclingAdapter
from layoutir.chunking import SemanticSectionChunker
# Create pipeline
adapter = DoclingAdapter(use_gpu=True)
chunker = SemanticSectionChunker(max_heading_level=2)
pipeline = Pipeline(adapter=adapter, chunk_strategy=chunker)
# Process document
document = pipeline.process(
input_path=Path("document.pdf"),
output_dir=Path("./output")
)
# Access results
print(f"Extracted {len(document.blocks)} blocks")
print(f"Document ID: {document.document_id}")
Project Structure
src/layoutir/
├── schema.py # Canonical IR schema (Pydantic)
├── pipeline.py # Main orchestrator
│
├── adapters/ # Input adapters
│ ├── base.py # Abstract interface
│ └── docling_adapter.py # PDF via Docling
│
├── extraction/ # Raw element extraction
│ └── docling_extractor.py
│
├── normalization/ # IR normalization
│ └── normalizer.py
│
├── chunking/ # Chunking strategies
│ └── strategies.py
│
├── exporters/ # Export backends
│ ├── markdown_exporter.py
│ ├── text_exporter.py
│ ├── parquet_exporter.py
│ └── asset_writer.py
│
└── utils/
├── hashing.py # Deterministic ID generation
└── logging_config.py # Structured logging
ingest.py # CLI entrypoint
benchmark.py # Performance benchmark
test_pipeline.py # Integration test
Design Constraints
✅ What We DO
- Strict layer separation
- Deterministic processing
- Schema validation
- Pluggable strategies
- Observability/timing
- Efficient storage (Parquet)
❌ What We DON'T DO
- Mix business logic into adapters
- Hardcode paths or configurations
- Use non-deterministic IDs (UUIDs)
- Combine IR and export logic
- Skip schema validation
- Load entire files into memory unnecessarily
Extensibility
Adding New Input Formats
- Implement
InputAdapterinterface:
class DocxAdapter(InputAdapter):
def parse(self, file_path: Path) -> Any: ...
def supports_format(self, file_path: Path) -> bool: ...
def get_parser_version(self) -> str: ...
- Implement corresponding extractor
- Update pipeline to use new adapter
Adding New Chunk Strategies
class CustomChunker(ChunkStrategy):
def chunk(self, document: Document) -> List[Chunk]:
# Operate on IR blocks
...
Adding New Export Formats
class JsonExporter(Exporter):
def export(self, document: Document, output_dir: Path, chunks: List[Chunk]):
# Export from canonical IR
...
Performance
Designed to handle 200+ page PDFs efficiently:
- Streaming processing where possible
- Lazy loading of heavy dependencies
- GPU acceleration support
- Parallel export operations
- Efficient Parquet storage for tables
Observability
- Structured JSON logging
- Stage-level timing metrics
- Extraction statistics
- Deterministic output for debugging
Schema Versioning
Current schema version: 1.0.0
Future schema changes will be tracked via semantic versioning:
- Major: Breaking changes to IR structure
- Minor: Backwards-compatible additions
- Patch: Bug fixes
Future Enhancements
- DOCX input adapter
- HTML input adapter
- Advanced layout-aware chunking
- Parallel page processing
- Incremental updates (only reprocess changed pages)
- Vector embeddings export
- OCR fallback for scanned PDFs
License
See project root for license information.
Contributing
This is a research/prototype phase project. See main project README for contribution guidelines.
layoutir
Metadata
Release files for layoutir 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| layoutir-1.0.4.tar.gz | 44.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| layoutir-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 89.1 kB
Release files / layoutir-1.0.4.tar.gz
| Download URL | layoutir-1.0.4.tar.gz |
|---|---|
| Size | 44.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17e8453c6d7585ba767399fd324587250f20512738929d597585f17a45d57bf9
|
|
BLAKE2b-256 checksum How to use checksums |
5f371a96ebc308245ad98e287be373b3d61ca176395ceacfd318e4fe4e846c80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logRelease files / layoutir-1.0.4-py3-none-any.whl
| Download URL | layoutir-1.0.4-py3-none-any.whl |
|---|---|
| Size | 45.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d86d4335046644796ea3310cb70ec0405e75841a7bea6d5a46e806d029ef87db
|
|
BLAKE2b-256 checksum How to use checksums |
f0fbc61713878efd0be31d8f3bb9f2f3edc975ce8421d1d227b30d9feaba5edf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logSecurity for layoutir 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for layoutir-1.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.