Mapping the pipeline to the docs

This documentation splits operational detail (how to run and validate) from conceptual pages (contracts, layout, governance). This note is a map, not a tutorial: it tells you where to read once you know which stage you care about.

Processor documentation emphasises batch cleaning, intermediate artefacts under Processed Database, and quality signals before handoff. Designer documentation explains how stable intermediates become per-doc_id delivery folders (default under Designed Database)—full-text JSON, structure JSON, multimodal indexes—and how those views relate to training and extraction consumers.

For a single narrative path from install through integration, start at End-to-end workflow, then open Processor and Designer as needed.