Chunking divides documents into smaller units for indexing and retrieval in a RAG pipeline. The choice matters: fixed windows can work for narrative documents but split structured content at the wrong boundaries. section 4.5.5
Choose boundaries to match the corpus, then measure retrieval quality before adding preprocessing complexity:
- Use fixed windows as a starting point; the baseline uses 400-word windows with 50-word overlap. section 4.5.5
- For structured content, split policy documents at numbered clauses, code repositories at function boundaries, and transcripts at speaker turns. section 4.5.5
- Consider semantic chunking when topic boundaries matter; it is more flexible but adds preprocessing cost and non-determinism. section 4.5.5









