Freshness Policy — What's Automated and What Isn't

Evidence records carry a retrievedAt date and authority pages carry a lastReviewed date. This page is honest about what those dates mean: there is no automated job on this site that re-fetches sources, checks for staleness, or moves pages between lifecycle states. Freshness here is a manual editorial practice, not infrastructure.

What the dates actually tell you

• An evidence record's retrievedAt is the date that specific source was fetched and hashed. It does not update itself — it changes only when someone re-verifies and re-hashes the source.
• An authority page's lastReviewed is the date someone last checked that page's content. Pages with an old date have not necessarily gone stale, but they also haven't been re-checked recently — read the date as information, not as a freshness guarantee.

Why this matters more for volatile fields

A pricing figure retrieved 90 days ago carries more real risk of being wrong than an identity fact retrieved 90 days ago, since prices change far more often than whether a repository exists. See /trust/how-to-verify for how to check a specific claim's currency yourself rather than relying on the presence of a date alone.

What we don't claim

We don't claim a scheduled re-verification cadence, an automated expiry mechanism, or lifecycle states like monitored or refresh_required — none of that is built. If and when automated re-verification is built, this page will describe the real mechanism, not before.

Related methodology pages

• Evidence methodology
• How to verify a claim
• Corrections

Source receipts

• Internal — lib/evidence.ts, lib/authority-evidence.ts. The real retrievedAt fields this page describes.
• Internal — lib/authority-pages.ts (lastReviewed field on the real AuthorityPage type).

Last reviewed

• Page last reviewed: 2026-09-02