TechniquecurrentRunning agents

When you remove the human gate, name what replaced it

Going hands-off takes named compensating checks and a written dial-back trigger.

SymptomAgent output that used to wait as proposed now lands live, and no log shows a check holding anything back.

A target list that gains entries daily from an unattended research agent was designed to stage them as proposed for me to ratify.

Taking the ratify step out means the safety has to move into deterministic gates first.

  • A dated source must show the person holds the role now, or the account component scores zero.
  • Every non-zero score component points to a sourced evidence item.
  • Gold rows are graded with each batch, and a calibration fail holds the whole batch.
  • Each run commits locally before it publishes so any published file is one revert away, while external writes need their own reversal snapshot.

The dial-back trigger is written down. One bad unattended record sends new entries back to proposed.

The gold rows can't go stale either. They rotate per session by a salt, and a row that fails in two sessions of a run is quarantined instead of holding everything. A quarantined gold row goes to a person before the next run.

A veto window must not ambush old proposals. Tier changes later got a 48-hour window that opens at the first live run, so proposals that predate the switch never confirm unseen.

Check your setup read-only

Find each agent step in your job configs that no longer waits for a person. Name the check that replaced the review for each step. Find the last hold that the check recorded in the run logs. A hold is a run-log line where the check stopped or held back at least one record. A step with no named check, or one whose check has no hold in the run logs, is a gap.

Passes ifEvery unreviewed step names the check that replaced review. Each check shows at least one recorded hold in the run logs.

Access needed:schedulerlocal-config

If it fails: changes to make later (not part of the check)
  1. 01List the checks that replace a review step, and how each check fails, before you remove the step.
  2. 02Grade rotating gold rows with every batch. Hold the batch on a calibration fail.
  3. 03Quarantine a gold row that fails in 2 sessions of one run. Do not hold all output for that row. Route the row to a person before the next run.
  4. 04Commit each run before publishing so any published file can be reverted. Snapshot external writes separately so they can be reversed.
  5. 05Start a veto window at the first live run, never at the proposal's creation date.
Applies ifA job config in your setup writes agent-researched records to a list or the CRM with no approval step by a person.

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