What is the primary operational risk of adopting a micro-chunking strategy (50 to 100 tokens per chunk) in an industrial equipment RAG platform?
Day 6: Choose and Evaluate Chunk Boundaries
Choose and Evaluate Chunk Boundaries
Loading lesson content...
In the FieldDesk parent-child chunking implementation above, what specific engineering dilemma is resolved by searching child vectors but injecting the parent synthesis_text into the LLM context window?
PolicyDesk chunks an employee handbook where Section 4.1 sets a general 2-day remote work policy, and Section 4.2 lists mandatory on-call engineering exceptions for Germany. An arbitrary 400-token chunker cuts the text between 4.1 and 4.2. An on-call engineer in Munich queries remote work rules and is given only Chunk A (Section 4.1), leading to an erroneous refusal of flex work. Which chunking strategy prevents this defect?