FailurecurrentRunning agents

Agents re-read their own wrong output as ground truth

A wrong inference recorded on a persistent page becomes the starting fact for every later run.

SymptomAn agent-maintained page still states a claim about a person that a human corrected in the thread.

A prototype deal agent I built kept a persistent page per account, including a stakeholder map that later runs read as ground truth. When someone on the deal team posted an ambiguous three-word note about a buyer's new title, along with a link, the agent wrote that the buyer had left the company and cited the link even though it said otherwise.

Four defects lined up, and each one is common:

  • The agent recorded its inference as fact.
  • "Appears to have left" in the table hardened by the time it reached the headline.
  • The run's own detector found the right record, but no stage could amend the page.
  • The weekly re-read took only agent posts as input and left out the human's correction.

Correctors that only reply in the conversation never heal the artifact.

The fix is four rules, plus one for deduplication, enforced by a check before the page is written rather than by instructions alone, because a finding that contradicts today's summary is the opposite of a duplicate.

Check your setup read-only

List the docs, plans or tables that 2 or more agent sessions wrote. Take the 5 most recently written claims in each one. Search the session transcripts after each claim for a human correction of the claim. Any corrected claim the doc still states in its old form is a gap.

Passes ifEvery sampled claim that a person corrected in a later session reads as corrected in the persistent doc.

Access needed:local-configagent-transcripts

If it fails: changes to make later (not part of the check)
  1. 01State that someone joined, left or changed role only from a primary source read in the same run.
  2. 02Make confidence monotonic so a headline inherits the weakest hedge among the claims beneath it.
  3. 03Rank a human correction above the agent's own earlier output. When a correction conflicts with the CRM, flag the conflict for a person. Do not overwrite the correction or the CRM value.
  4. 04Leave a "stale, supersede at next write" marker for the next authorized writer where write ownership blocks an edit.
  5. 05Exempt corrections from dedup. Label them as corrections to today's summary.
Applies ifYour transcripts show agent runs reading a page, plan or table that an earlier agent run wrote.

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