FindingcurrentRunning agents

A finding written in a doc doesn't change the system

A finding has not landed unless you can name the executable line it changed.

SymptomA lesson already written in a process doc's notes gets rediscovered, while the doc's scoring step is unchanged.

My account-selection process had a pain-points section. Early in the year it recorded a clear insight about which kinds of accounts fit best.

Five months later I derived the same profile from scratch, because the finding never reached the line the process runs.

Its scoring still weighted a signal that pushed exactly those accounts down, and every quarterly run repeated the miss.

The step now calls my shared fit rubric instead of hand-rolling its own scores. A rubric edit reaches every run the same day, because the rubric is the mechanism.

The reverse direction drifts too. When I retired three holds from a daily sweep, four prose copies kept describing them as live:

  • the runbook
  • the root instructions file
  • a memory note
  • the script's own header comment

Anyone reading those trusted a net that no longer existed, and agents read the same docs.

Check your setup read-only

Take the 5 newest lessons in each process doc's notes or pain-points section. Search the scoring rubric, filter or gate code that the process runs for a line that encodes each lesson. A line encodes a lesson if it names the same field, value, threshold or condition the lesson names. More than 1 of 5 with no such line is a gap.

Passes if4 or more of 5 sampled lessons per doc map to a scoring, filter or gate line. Each line is in the code or rubric the process runs.

Access needed:local-config

If it fails: changes to make later (not part of the check)
  1. 01Name the scoring, filter or gate line a finding changed, after you land the finding. A finding that changed no such line has not landed.
  2. 02Replace hand-rolled scoring inside a process with a call to the shared rubric.
  3. 03Search docs, instructions, memory and script comments for the old phrasing when a gate or threshold changes in code. Do the search in the same session as the change.
  4. 04Correct every restatement you find before you call the change done.
  5. 05Close the old documented findings that a changed mechanism now resolves.
Applies ifYour setup has process docs with a notes or pain-points section, kept apart from the code or rubric the process runs.

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