FindingcurrentRunning agents

A stated reason is a hypothesis rather than a rule

Turning a reviewer's stated reasons into a filter threw out good accounts.

SymptomAn exclusion rule in your target list traces back to one person's explanations of their no's, with no outcome data behind it.

A seller reviewed a batch of our target accounts and disqualified several, with a reason for each. My analysis read the reasons as rules.

More than a third of the no's shared one firmographic attribute, so the analysis turned that attribute into a penalty. A back-test agreed, because it ran on the same verdicts the rule came from.

The filter then removed about twice as many accounts as the seller had rejected, none of them researched.

The reason had the cause wrong. Those no's shared a passing business condition rather than a fixed attribute. The removed accounts were re-screened and recovered.

Now a verdict and its stated reason are separate records. The reason is a hypothesis with a confidence, never a rule.

Until outcomes can test a rule, I don't mine rules. A new candidate shows the 3 most similar past verdicts beside it, and a person judges.

Check your setup read-only

List each exclusion rule in your target-list scoring config. An account with a known opposite verdict is one the rule excludes whose CRM opportunity closed won. It is also one the rule keeps whose opportunity closed lost. Look for a stored test that scores each rule against such accounts. A stored test is a script, its output or a doc. The test must use accounts that weren't used to derive the rule. Any rule with no such test is a gap.

Passes ifEvery exclusion rule was scored against accounts with a known opposite verdict that weren't used to derive it.

Access needed:local-configcrm-read

If it fails: changes to make later (not part of the check)
  1. 01Store each verdict and its stated reason as separate records.
  2. 02Do not mine rules until outcomes, not opinions, can test the rules. Show the 3 most similar past verdicts beside a new candidate until then.
  3. 03Score the accounts a rule would touch against their recorded verdicts before the rule surfaces.
  4. 04Do not back-test a rule on the verdicts it was derived from.
  5. 05Let rules down-rank with a visible reason, never remove. Let anyone challenge a rule back into review.
Applies ifYour scoring config takes reviewer verdicts as input, and fewer than a few hundred accounts carry a verdict.

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