From 7361afc8bc2ebdfc8ab7f05f642a6ea5a3b4a8d1 Mon Sep 17 00:00:00 2001 From: Nanako Tsai Date: Mon, 20 Jul 2026 05:19:34 +0800 Subject: [PATCH] Re-run the dispatch brake on recurrence MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The brake evaluates one decision at a time, which leaves a blind spot: same-shape small tasks that arrive one at a time each pass the direct-work test individually, and the main agent absorbs them serially for hours without any single decision being wrong. Observed in a 26-hour field session: 1,267 direct edits alongside 12 delegations, with milestone fan-out working correctly the whole time. After ~three direct repeats of the same shape with more arriving, re-enter the primitive table with the accumulated shape: the remainder are repeated homogeneous items — batch them, keep per-item acceptance. Co-Authored-By: Claude Fable 5 --- SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/SKILL.md b/SKILL.md index 9c1f0ed..ce3071a 100644 --- a/SKILL.md +++ b/SKILL.md @@ -23,6 +23,10 @@ Before delegating, answer these questions: If any answer is unclear, do not fan out. Clarify the task, perform a small scout, converge the shared contract, or design ownership first. +### Re-run the brake on recurrence + +The brake evaluates one decision; it has a blind spot for accumulation. Small same-shape tasks that arrive one at a time — review findings with a known remedy, templated documents, single-file follow-up fixes — each pass the direct-work test individually, and a session can spend hours executing them serially in the main agent without any single decision being wrong. After completing the same shape of small task directly about three times, if more instances are still arriving, re-enter the primitive table with the accumulated shape rather than the next single item: the remaining instances are repeated homogeneous items, so batch them to a worker and keep only per-item acceptance in the main agent. An already-diagnosed finding with a known remedy counts as such an item — a hot context justifies the first direct fix, not the twentieth. + ## Choose an execution primitive | Task shape | Prefer |