TechniquecurrentRunning agents

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.

SymptomA 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 if8 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. 01Store a last-verified date on every fact you display. Compute the fact's age at render time.
  2. 02Mark 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. 03Rank only on durable signals, cached per rubric version. Show timing signals as dated notes after selection.
  4. 04Let a newer proposal about the same entity and field supersede the older one.
  5. 05Expire low-impact proposals visibly, with a count of what expired unreviewed.
Applies ifOne person approves changes to a list the page shows, and the approval log shows gaps of several days between reviews.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.