Short answer: for a travel itinerary planner, I use chunks whose boundaries follow itinerary facts and citation units, then retrieve a small set of those chunks with metadata filters. Bigger windows are easier to build, but they blur which source supports a date, fare rule, or opening hour.
I learned this while reviewing an on-call incident pattern in production systems: a missed job is visible, but a duplicate delivery that looks plausible can survive for days. Retrieval has the same shape. A planner can return a beautiful day-by-day route with one unsupported detail hidden inside a large passage. The failure is quiet. The fix starts with boundaries, not with a larger model.
How should chunk boundaries support retrieval, grounding, and citation?
In my postmortems, I write down the smallest claim that must be replayed. For an itinerary, that might be “the museum is closed on Monday” or “the rail ticket is valid after 09:00.” Each claim needs a stable source span, a
Discussion
Don’t hold back—comment!
Don’t wait—start sharing your ideas now!