Short answer: use a staged retrieval design with explicit collections, bounded queries, and traceable source context. For a travel itinerary planner, “delete” is not one operation. A place can leave the index, the answer cache, and the citation trail at different times. Treat those as separate contracts, then test them with a small labeled set before shipping.
I care about the first useful call. If an itinerary still recommends a closed museum, a polished embedding pipeline does not help. The visible answer must map back to a retrieval unit, its metadata, and a freshness promise.
What should delete semantics mean in a travel itinerary planner?
Start with a written contract for one retrieval unit. In this system, that might be a single attraction-hours record or one policy paragraph, not an entire destination guide. Give it a stable source identifier, a collection, and metadata such as city, date range, and source revision.…