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.
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
- 01Require a Why line and a Would change if line on every recommended option.
- 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.
- 03Probe each option's mechanism once with a help page, a dry run or 1 test call before offering it.
- 04Link corrections made within 6 hours in the same folder back to the pick they followed.