Re-run the dispatch brake on recurrence#1
Open
Nanako0129 wants to merge 1 commit into
Open
Conversation
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 <noreply@anthropic.com>
This was referenced Jul 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The dispatch brake evaluates one decision at a time. That leaves 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 alternative test individually. No single decision is wrong, and the main agent absorbs them serially for hours.
Observed
From a time/token attribution of two long orchestration sessions (75h + 26h wall-clock; full report in Nanako0129/pilotfish#16, with the matching policy amendments specced in Nanako0129/pilotfish#15, numbers cross-checkable against public TokenBar PRs):
The primitive table already has the right row ("Repeated homogeneous items → Batch or workflow") — it just never fires, because at each decision point the shape on the table is one item, not the accumulated stream.
Change
One
###subsection under Start with the dispatch brake: 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 — batch the remainder to a worker, keep per-item acceptance in the main agent. Capability-neutral wording, per the skill's own conventions; no version bump (left to your release flow).🤖 Generated with Claude Code