Insurance claims intake has an awkward retrieval constraint: a document can become legally irrelevant before it becomes physically old. A withdrawn medical note, a superseded policy endorsement, or a duplicate claim must stop influencing an answer on a predictable schedule.
Short answer: use a staged retrieval design with explicit collections, bounded queries, and traceable source context; make deletion a first-class state transition so the application can swap vector providers without changing its answer contract.
Start with the retrieval contract
The contract is more important than the first embedding model. Define what one retrieval unit means (a paragraph, a form field, or a claim event), which metadata filters are mandatory, and how fresh an update must be before it is visible. For claims intake, I would attach claim_id , policy_id , document_id , revision , tenant_id , and a source timestamp to every unit.…