TechniquecurrentRunning agents

Every agent result gets one fresh-eyes review

What the agent produced determines the lens, and the runner supplies the 'reviewed' line.

SymptomAgent results land marked done with no review file beside them, or with a 'reviewed' claim the agent wrote itself.

Only code had a reviewer on my agent queue. Everything else could close without one. An audit of two weeks of agent-closed tickets found about half had closed with no review at all.

Now no result reaches me, or closes itself, unless a fresh-context review ran on that dispatch, or it lands explicitly marked not reviewed. There is no skip label, so a trivial ticket still pays one cheap pass.

A classifier with no model reads the output folder and picks the lens from the deliverable's kind.

  • Code gets a code review.
  • A Salesforce write packet gets checked for scope, per-field values, blanks over live values, and a reversal snapshot.
  • A spec or plan gets an approach review.
  • Everything else gets a findings review so claims are traceable, the brief is covered, and untested parts are disclosed.

High-consequence work gets three loops with distinct lenses, each run even when the last came back clean.

The handback states what ran, built from the runner's own record, never from agent text. Agent text that imitates that line is removed, so an agent can't claim a review it didn't get.

Check your setup read-only

Look at your last 20 agent results marked done in the work queue. Count how many had a review by a separate session, from the review log or transcripts. Any done result without a review that isn't explicitly marked not reviewed is a gap.

Passes ifEvery one of 20 sampled done results shows a review by a session other than the working session. A sampled result explicitly marked not reviewed also passes.

Access needed:agent-transcriptslocal-config

If it fails: changes to make later (not part of the check)
  1. 01Require at least one fresh-context review session per dispatch before any result is marked done. Allow no skip label. Land the result explicitly marked not reviewed when no review can run.
  2. 02Choose the lens from the output's kind: code, write packet, spec or plan, or findings. Read the kind with a script, not from a label.
  3. 03Run 3 loops with distinct lenses for high-consequence work, even when earlier loops came back clean.
  4. 04Allow 3 fix cycles per ticket. Stop patching after the third cycle. Redraft from the brief instead of a fourth patch.
  5. 05Build the 'reviewed' line from the runner's record. Strip any agent text that imitates the line.
Applies ifYour work queue is the board, ticket list or file where agents file items for a person to act on. It lets agents mark their own results done.

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