FindingcurrentRunning agents

'What's happening now' needs a date filter instead of a relevance store

Recency decay re-weights old facts but never excludes them.

SymptomAn agent's account brief describes a project or deal stage that ended weeks ago as current.

A brief that reads current state from a relevance-ranked store with recency decay can narrate weeks-old project names as current.

The store looked recency-aware, which made the mistake easy.

Decay only re-weights, so an old fact keeps part of its score. A salient old fact beats a fresh, ordinary one, and the agent narrates page one as the present.

Current-state questions now go through a date-bounded query scoped to the entity, the only path that excludes by date. Relevance ranking stays for durable context, such as the standing thesis and long-running risks.

Rolling verification has the same blind spot between checks. If you re-verify people on a rolling window, a job change the week after a check stays invisible until the next one.

Any first-party sign of a move acts as a cheap trigger and bumps that person to the front of the next verification pass.

A date-bounded query suits thematic questions. For an exhaustive list of every interaction in a window, I page the full record instead.

Check your setup read-only

Take the 3 most recent agent transcripts that answer a current-state question about an account. Look up the source date of every fact each answer cites, in the store the agent queried. Any cited fact older than the window the question asked about, shown without its date, is a gap.

Passes ifEvery fact cited in the 3 answers falls inside the asked window or carries its date in the answer text.

Access needed:agent-transcriptscontext-read

If it fails: changes to make later (not part of the check)
  1. 01Answer "what's happening now" questions with a date-bounded query, not the relevance-ranked inventory.
  2. 02Use relevance ranking only for durable context, and show every surfaced fact with its date.
  3. 03Read structured state, such as renewal date or opportunity stage, from the record, never from prose facts.
  4. 04Treat any cheap sign of a job change as a proposal only, never as truth.
  5. 05Move a proposed person to the front of the next verification pass. A human confirms the proposal before it becomes truth.
Applies ifYour agent's tool config points at a relevance-ranked search store, and transcripts show it answering current-state account questions.

← 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.