Short answer: assign each document class a freshness window, verify the source on that schedule, and keep expired chunks out of retrieval until one complete new index generation is ready. For a logistics team watching an operating-status page, that hybrid design keeps normal queries fast without letting yesterday's instructions masquerade as current guidance.
The least complex useful pipeline has five stages: fetch the page, extract its meaningful text, compare a stable content hash, build a new chunk generation only when the hash changes, and apply a freshness check before retrieval. Freshness describes source verification, not merely the time a chunk entered the index. A nightly ingest timestamp cannot prove that a page was still current at noon.
How should internal engineering documentation retrieval enforce freshness windows?
Treat the window as an eligibility rule attached to a document class. A short window belongs to a page whose operational instructions can change during the working day.…