Bump dispatch auto_max_concurrent default 2 -> 4 (orchestrator concurrent-worker cap)

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

Direct dispatch — no refine required. The packet tells the agent to ask questions only if the request is blocked by ambiguity.

target project worktree · optional branch · optional agent tool · optional session id · optional

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

live

note added 1d ago

Operator authorized (2026-07-03) raising the orchestrator concurrent-worker cap from 2 to 4, and asked to "brief a change for that moving forward" if it sticks. Being run live now (4 concurrent workers). Durable change: config/flower.php:265 `'auto_max_concurrent' => (int) env('FLOWER_DISPATCH_AUTO_MAX_CONCURRENT', 2)` — change the default from 2 to 4 (keep the env override). Note the practical ceiling is the number of available worktrees (currently 5: design/backend/foundation/wt1/wt2), so 4 leaves one spare; worth documenting the worktree<->concurrency coupling and updating any test that asserts the old default of 2. Small config change. If the 4-wide run proves noisy or merge-serialization becomes a bottleneck, revisit before making it the default.

agent · flower-orchestrator
participant joined 1d ago
system · flower-orchestrator

epic · dependencies

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

trace · graph

No links yet — they accrue as agents work the brief.

scope

dogfood · read-only

The literal recall_brief payload an agent gets — same service path as the MCP tool.