---
title: "Comment by Kartik N V J K on \"Answer Engine Source Records Need More Than URLs\" | Hashnode"
description: "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"
url: "https://hashnode.com/posts/answer-engine-source-record-design/6a79f7c6f6a43780a055b932/comment/6a7c802ed7262ff37aed209f"
---

[Discussion](https://hashnode.com/posts/answer-engine-source-record-design/6a79f7c6f6a43780a055b932)

Comment [Answer Engine Source Records Need More Than URLs](https://hashnode.com/posts/answer-engine-source-record-design/6a79f7c6f6a43780a055b932)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 12](https://hashnode.com/posts/answer-engine-source-record-design/6a79f7c6f6a43780a055b932/comment/6a7c802ed7262ff37aed209f)

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?
