TechniquecurrentRunning agents

A recommendation has to show what would change it

If you take most picks, each pick needs its own counterweight.

SymptomYour approval log shows you took the recommended option on most questions, and the cards give no reason the others lost.

When one person approves many agent questions a day and takes most picks as offered, an unchecked recommendation is a ruling made by whoever wrote the card.

So every recommended option carries two lines. "Why" gives the reason. "Would change if" names the fact that would flip it, which hands me something specific to check instead of a reason to nod.

Config and destructive questions, about 13% of the total, also get a blind second opinion. A read-only agent sees the options shuffled, never the pick.

An option is only as good as its mechanism. One card offered loading records through a vendor table that the vendor's command-line tool couldn't write to. I picked it, the agent dead-ended, and I did the import by hand.

I also link later corrections back to the followed pick.

Check your setup read-only

Read the 20 most recent approval questions in your agent's transcripts or decision log. Count the recommended options that state the condition under which another option would win. Fewer than 15 of 20 means picks arrive without a stated condition for another option.

Passes if15 or more of 20 sampled recommendations state the condition under which another option would win.

Access needed:agent-transcripts

If it fails: changes to make later (not part of the check)
  1. 01Require a Why line and a Would change if line on every recommended option.
  2. 02Add a second opinion to config and destructive questions. Get the opinion from a read-only agent shown the options shuffled and not the pick.
  3. 03Probe each option's mechanism once with a help page, a dry run or 1 test call before offering it.
  4. 04Link corrections made within 6 hours in the same folder back to the pick they followed.
Applies ifYour decision log or transcripts show agent approval questions on most days, and the recommended option wins most of them.

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