# Compute a fact's age when it's shown instead of in a refresh job

Badges computed at render time keep moving after every refresh job stops.

By Ki Moon · 2026-08-25 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/design-for-decay/

**Symptom:** A seller-facing page shows a fact as current long after its source changed, such as a contact's old role with no date beside it.

I keep a living list of the people we target at our best-fit accounts. My first design refreshed it on a schedule and pushed a digest of proposed changes to me as the one reviewer. Digests like that outran me and were dead within days.

Staleness is now computed from each fact's last-verified date when the page renders, so no job has to run for a badge to move. Sellers still see amber and red on pages they already use even if every watcher dies.

- A person's role goes stale after about 90 days.
- A company-level judgment goes stale after about 180 days.
- A buy signal goes stale after about 30 days.

Each judgment is also split by half-life, because leaving a decaying signal inside the score reshuffles the list every run and serves week-old "hot" flags as current. A structural fit read changes over quarters and ranks the list, while a timing read decays in weeks and shows only as a dated note after selection.

Moving proposals from a push digest to a pull queue turned two ignored weeks from archaeology into a 20-minute triage.

These windows are judgment calls rather than measured rates of how fast each kind of fact goes wrong, so treat them as starting points.

## Check your setup (read-only)

Open the seller-facing account page for any 1 account. Read the first 10 facts on the page. Look for a last-verified date shown beside each fact. More than 2 of 10 without a visible date is a gap, because the page can't show its age.

**Passes if:** 8 or more of 10 sampled facts show a last-verified date on the page itself.

**Access needed:** local-config

## If it fails (changes to make later, not part of the check)

1. Store a last-verified date on every fact you display. Compute the fact's age at render time.
2. Mark a role fact stale after about 90 days. Mark a company-level judgment stale after about 180 days. Mark a buy signal stale after about 30 days.
3. Rank only on durable signals, cached per rubric version. Show timing signals as dated notes after selection.
4. Let a newer proposal about the same entity and field supersede the older one.
5. Expire low-impact proposals visibly, with a count of what expired unreviewed.

**Applies if:** One person approves changes to a list the page shows, and the approval log shows gaps of several days between reviews.

**Skip if:** The records' edit history shows several different people editing them on most days.

Tags: staleness, signals
