TechniquecurrentRunning agents

More agents grow the backlog while a closing job and one capped channel shrink it

Nothing closed work until one job took over closing and one channel carried every ask.

SymptomYour work queue's Inbox and Review counts climb week over week while no automation closes anything.

Every job, agent and session I run files follow-ups, scan findings and handbacks, and nothing closed that work. Most of the queue sat in Inbox, and a steady tail waited on review or on me.

When agent capacity is idle and I am the constraint, more producers only add stock.

The parts that pay off cut decisions. One capped voice wakes me through a nightly brief with one card per item, while specialist jobs stay silent on empty runs. One reply such as 'yes 2 except one' clears a whole set.

The closer works in four steps.

  • A deterministic pre-pass finds duplicates, work done elsewhere, quiet decisions and stale tickets.
  • One read-only model session proposes verdicts.
  • The runner re-checks the evidence itself and applies at most 25 moves.
  • If I reopen 2 moves inside 7 days, it drops to proposals only.

The closer's first runs merged only about one candidate in fifteen, because what remained was my own decisions.

Quiet by default needs proof of life. Two of my jobs failed by building a digest, having the post blocked, and exiting cleanly. Now each job declares whether its post is its health signal. About one in ten do.

Check your setup read-only

Count the items waiting on you today by state, from your work queue's state counts. Count the items any automation closed last week, from the queue's close history. If the waiting count grew and the automated close count is zero, that's a gap.

Passes ifAutomation closed items last week, or the count waiting on you held flat or fell.

Access needed:local-config

If it fails: changes to make later (not part of the check)
  1. 01Route every report through one capped digest. Keep specialist jobs silent on empty runs.
  2. 02Let the closer act alone only on evidence the runner can verify. Verifiable evidence is a related ticket done, or a path or commit that exists.
  3. 03Keep absence-based moves as questions in the digest, never closes. Absence-based moves cover items stale 30+ days and decisions quiet 14+ days.
  4. 04Log every move with its prior state. Cap moves at 25 a run. Halt on 2 human reopens within 7 days.
  5. 05Alarm when a job whose post is its health signal passes without its post.
Applies ifYour work queue is the board, ticket list or file where agents file items for a person to act on. It shows one approver for items that several jobs and agents file.

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