The freshness and permissions fields are the two everyone forgets until an answer cites a doc the user was not allowed to see, or a stale one that got retracted. Carrying a content_hash for provenance is smart, it lets you detect when a source changed out from under a cached answer. Do you re-verify last_verified_at on a schedule, or only when the retrieval surface reports the underlying doc changed?
Kartik N V J K
The freshness and permissions fields are the two everyone forgets until an answer cites a doc the user was not allowed to see, or a stale one that got retracted. Carrying a content_hash for provenance is smart, it lets you detect when a source changed out from under a cached answer. Do you re-verify last_verified_at on a schedule, or only when the retrieval surface reports the underlying doc changed?