Repository navigation
docs(specops): builders run on an explicitly passed builder-tier model, never the orchestrator's - #32
Merged
Merged
Conversation
…l, never the orchestrator's The protocol said "use Sonnet for the implementation subagents" but did not say how, and the harness default is to inherit the orchestrator's model when a dispatch omits `model`. An orchestrator on the strongest tier then runs every builder on that tier: the most expensive way to implement, and one usage-limit event on that tier stops every builder at once. State the rule as a dispatch requirement: pass `model` on every Agent call (Sonnet by default, Opus for correctness-critical plans), set CLAUDE_CODE_SUBAGENT_MODEL as the backstop, and reserve the orchestrator's own model for the human's explicit request. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015AK5HiZZnymqkm7nVLfnpP
themightychris
force-pushed
the
docs/builder-model-explicit
branch
from
October 22, 2026 13:24
d397675 to
e402cc2
Compare
… the same builder The adversarial pre-review pass runs first on every branch; the orchestrator then reads the diff with that report in hand and owns the merge. Each finding is routed: a substantive fix goes back to the implementation subagent that built the branch, resumed so it keeps its context, never a fresh builder; a quick, unambiguous fix the orchestrator makes directly. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015AK5HiZZnymqkm7nVLfnpP
Merged
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
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.
The drain-the-DAG protocol said "use Sonnet for the implementation subagents" but did not say how, and the harness default is to inherit the orchestrator's model when a dispatch omits
model. An orchestrator running on the strongest tier then runs every builder on that tier, which is the most expensive way to implement a plan and means one usage-limit event stops every builder at once. Seen in practice on 2026-10-21.Changes
references/parallel-execution-protocol.md: the model bullet becomes a dispatch requirement. Passmodelon every Agent call: Sonnet by default, Opus for correctness-critical plans (migrations, concurrency, auth). Name the backstop (CLAUDE_CODE_SUBAGENT_MODELin a settingsenvblock, which a per-callmodelstill overrides) and reserve the orchestrator's own model for an explicit human request.SKILL.md: the one-line summary of the protocol says the same ("a builder-tier model passed explicitly on every dispatch, never inherited from the orchestrator").No project or client references.
🤖 Generated with Claude Code
https://claude.ai/code/session_015AK5HiZZnymqkm7nVLfnpP