A freshness label should explain which version the answer used, not merely when a background job ran. Source publication, connector observation, index activation, and answer generation are different timestamps.
Freshness describes a specific boundary
Knowledge freshness indicates how current the evidence is for the requested claim. It depends on the source’s effective status and the pipeline’s update state, not only the age of the file.
For a proposed answer record, retain source version, relevant effective date, last verified observation, ingestion or index version, and generation time. Display only the meaningful subset with plain wording and controlled source access.
Do not describe a freshly indexed obsolete policy as current. A rebuild can happen today while preserving an older rule. Authority and effective status remain separate from processing recency.
Review a fictional hours answer
An office changes holiday hours at 09:00. The connector observes the source at 09:05, the new index activates at 09:07, and an answer at 09:06 still uses the prior version. The trace should make that relationship visible.
The user may need a qualified response if current hours cannot yet be verified. A label saying “updated today” would hide the material difference. These timestamps are illustrative, not measured service guarantees.
| Freshness field | What it establishes |
|---|---|
| Source effective date | When approved meaning applies |
| Source version | Which content was used |
| Connector observation | When that state was seen |
| Index activation | When derived evidence became eligible |
| Answer generation | When the response was produced |
Test old sources recently reprocessed, new sources awaiting indexing, and answers served from cache. Verify that the displayed label does not imply stronger currentness than the evidence supports.
Explain limits without flooding the interface
A concise statement can identify the cited policy version and meaningful observation limit, with details available to authorised users. Avoid showing an unrelated technical timestamp simply because it is easy to obtain.
Detailed provenance increases metadata and storage. Focus on claims where freshness changes action, such as schedules, eligibility, and current procedures. Historical questions may intentionally need older versions, so newer is not always the correct target.
This freshness interface is proposed. The voice integration case study describes related retrieval work without claiming these timing guarantees. Pair it with ingestion-delay measurement.
Answer freshness FAQ
Does indexed today mean policy is current?
No. Check source authority, effective status, and the version actually supplied.
Should every answer show all timestamps?
Show what helps the user judge the claim, with deeper authorised diagnostics where needed.
What if the connector is behind?
Apply the defined stale-evidence policy and avoid implying that all recent source changes were considered.