Queue stale evidence for purpose-specific review — what should the operator record?
A timestamp alone cannot decide whether evidence is useful for a task. A product specification may need a different review cadence from a public event announcement. Build a freshness queue tied to the table's operational purpose, while keeping current access and retention rules independent from a team's preferred review interval.
Separate evidence age from validity and prioritize only the rows that need a freshness check.
Use local review_after and freshness_reason fields, explaining why this table needs another check rather than asserting a service-wide freshness guarantee. A local rule can require review before a specific release without claiming any universal number of hours during which a public statement remains accurate.
Mark confirmed-current, revised or unresolved with a reviewer and time; update dependent tables only through a new documented revision. The closure entry should name the checked fields and next review condition; a generic fresh label can otherwise outlive the purpose for which it was assigned.Define the stale-for-purpose rule
Use local review_after and freshness_reason fields, explaining why this table needs another check rather than asserting a service-wide freshness guarantee. A local rule can require review before a specific release without claiming any universal number of hours during which a public statement remains accurate.
Record available times
Keep received_at, source_published_at and last_reviewed_at separate so a recently copied old row does not appear newly observed. Copying a file today should not reset last_reviewed_at unless a real review occurred; use copied_at separately if the transfer time matters operationally.
Queue eligible checks
Select rows whose local review deadline has passed and whose current access permits review; mark inaccessible rows blocked rather than automatically fetching elsewhere. The queue should identify why review is needed, such as upcoming release or changed dependency, avoiding unnecessary rechecks of every old row regardless of task.
Inspect changed evidence
Compare only the relevant fields against authorized current evidence, distinguishing a wording change from a failure to read the source. A source read that fails now should yield unresolved-availability, not a claim that the older observation was false or that the source was deleted.
Resolve the review
Mark confirmed-current, revised or unresolved with a reviewer and time; update dependent tables only through a new documented revision. The closure entry should name the checked fields and next review condition; a generic fresh label can otherwise outlive the purpose for which it was assigned.
Keep the boundaries clear.
- Separate evidence age from validity and prioritize only the rows that need a freshness check.
- Operational record: Define the stale-for-purpose rule. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.