Source Trail Maintenance Flow

# Update Date Audit for Searchable Records

Searchable records age unevenly. Some pages remain useful because they define a concept. Others become misleading because a current number, interface label, or policy step changed. An update date audit is a quick way to decide which records need revision before they keep attracting search traffic.

## Start with claim types
Scan the record and mark claims as stable, time-bound, interface-bound, or market-bound. Stable claims include definitions and conceptual boundaries. Time-bound claims include deadlines and eligibility periods. Interface-bound claims include button names, menu paths, and API fields. Market-bound claims include prices, rankings, and adoption numbers.

## Compare date to volatility
A page from last month can be stale if it describes a UI that changed yesterday. A page from two years ago can still be fine if it explains a historical concept. The audit should judge the claim, not the document age alone.

## Add a visible review note
When a record contains volatile claims, add a short review note near the top or near the claim. “Checked for API field names on 2026-06-22” is better than a generic updated timestamp. The note says what was checked.

## Prioritize high-risk stale claims
Do not audit every old page equally. Prioritize records that affect money, access, safety, compliance, travel timing, or user trust. A stale styling preference is annoying; a stale eligibility threshold can cause real harm.

## Example workflow
1. Find records with current-year language.
2. Identify the claims that can change.
3. Recheck only those claims against their role-labeled sources.
4. Add a correction trail if meaning changed.

The outcome is not a perfect library. It is a library where readers can see which parts are safe to rely on today.

Update Date Audit for Searchable Records

// COMMENTS

ON THIS PAGE