Short answer: use separate freshness windows for policy wording, claim events, and reference guidance, then make the window part of every retrieval filter and answer citation. For an insurance claims intake bot, this keeps a newly submitted loss from being explained with yesterday's status while avoiding a wasteful full re-index on every upload.
I would record the decision as an architecture decision record (ADR): freshness is a correctness constraint, not a tuning knob. The bot may retrieve an older document only when its source explicitly permits that age and the answer labels the document's effective time.
The decision record: what must stay true
The system has four invariants. Every chunk carries effective_at , observed_at , expires_at , claim_id (when applicable), and a source revision. Retrieval rejects expired chunks before ranking. A claim event can narrow a search, but it cannot silently widen a policy window.…