Beyond parallel agents
Running several agents at once is not the same as organizing a difficult job. Parallelism can produce more output while leaving the central question unanswered: who should do each piece, with which model, at what effort level, and how will the parent know the work is actually complete?
Stormbreaker starts with a single Goal. That goal is the fixed outcome and acceptance boundary. UltraCode decomposes it into concrete work packets. Stormbreaker then gives the parent enough live runtime information to make an explicit assignment for every packet rather than broadcasting the same prompt to a row of interchangeable workers.
The parent chooses from live inventory
Each assignment can name an exact runtime, model, and effort level from the inventory connected to the current host. A contract-focused task might go to one runtime at high effort; an implementation inspection can go to another; a fast surface check can use a lighter allocation. The host validates those choices before the work begins.
The resolved allocation is written into the task result. That receipt matters because it separates the plan the parent proposed from the runtime and model that actually performed the work.
Model names can change; the contract should not
Connected tools rename models, add variants, and remove old identifiers. Stormbreaker treats those changes as runtime facts rather than editorial assumptions. The parent sees the current inventory, can choose exact identifiers when they exist, and receives a fallback receipt if the host resolves the request differently.
That makes allocation inspectable without pretending the surrounding model market will stay still.
The final answer has a gate
Stormbreaker does not treat worker completion messages as proof. Final synthesis can claim success only when the run has the expected task receipts, resolved allocations, test results, and surface evidence. If the evidence is missing, the parent should report the gap rather than turn partial work into a confident release claim.
- Goal defines the outcome and acceptance boundary.
- UltraCode creates concrete, reviewable work packets.
- Stormbreaker assigns runtime, model, and effort per packet.
- The evidence gate controls what the final synthesis may claim.
Where it stands
The parent-directed swarm path, live runtime inventory, exact allocation fields, fallback receipts, and evidence-gated synthesis were being integrated in the then-current 0.8.13 development line when this preview was published. This article describes the implementation direction we could inspect at publication; it is not a promise that every connected runtime or model is already available in a public build.
