The idea
A correct answer to yesterday's document can be wrong for today's process. Index freshness describes the delay between a source change and its availability to search. Deletions and access changes are as important as newly added content.
Design choice
Track source revision and indexed revision separately. Choose a measurable freshness target for each collection. Treat a failed deletion as a potentially serious access problem, rather than merely a delayed content update.
Worked example
A daily reference collection tolerates a scheduled refresh. A live operational notice needs a much shorter delay and a clear warning when its index is stale.
Before you ship
- Measure update lag and deletion lag
- Surface stale collections
- Recheck access during retrieval
Examples are illustrative. Adapt the checks to your own environment.