SYSE.44 - Divide and Recombine Work across Agents

Type: Method pattern Status: Stable

SYSE.44:1 - Problem frame

Use this when people or technical agents could usefully divide a needed result, but preparation, dependencies or joining errors may consume the gain. Start with the whole result and compare one-performer completion with a concrete division.

The subject is the working division, the material each participant receives and the recombination of their contributions. People may bring different source access or expertise; technical participants may use separate contexts of one model or different tools. Those arrangements need different preparation but share the requirement that their returned contributions fit the same whole. The first result is an integrated contribution that the receiver can use, or the dependency, conflict or evidence gap preventing it.

Keep dependent steps in order: dividing 347 × 6 at each digit introduces carry handovers into a calculation one person can complete. A proposed division must repay preparation, communication, duplicate work and integration. A.15.9/SYSE.9 supplies bounded requests; independently governed Systems retain SYSE.18’s governance question.

SYSE.44:2 - Problem

Splitting a brief or prompt can remove the common premise that made its parts meaningful. Even with the same supplied material, participants may interpret a quantity differently or intend different next contributions. Agents can then solve different versions of the problem, duplicate the same source error, or change shared state incompatibly. A final summarizer can conceal those differences instead of resolving them.

SYSE.44:3 - Forces

Separate contexts can protect attention and allow parallel inquiry, but every boundary needs a usable handover. Narrow context limits distraction while risking loss of a global condition. Diversity can expose mistakes, although different role names do not produce independent evidence. Integration must preserve justified disagreement without making every disagreement a reason to repeat all work.

SYSE.44:4 - Solution

SYSE.44:4.1 - Select contributions and the receiving result

Name the whole result, its protected conditions and the person or system that will integrate it. Recover which missing results could be obtained separately and which inputs they share. Distinguish a calculation, source interpretation, alternative proposal and independent check; their return conditions differ.

Compare one-performer completion, including one-context LLM work, with the proposed division on expected task quality and total effort. Include preparation, source access, repeated work, waiting and integration. Use a small representative comparison through SYSE.46 when the advantage is uncertain. More agents is a candidate arrangement, not a quality measure.

For the selected arrangement, state each contribution’s receiving use, required inputs, permissible actions, available sources, result form and stop. A.15.9 and SYSE.9 supply bounded requesting and reliance. A concise passage or a structured return is sufficient when the recipient can act from it.

SYSE.44:4.2 - Construct usable contexts and effect boundaries

Give each participant the common premise and source/configuration needed for the contribution, plus the relevant constraints of the whole. A human work brief and an LLM request must each preserve those meanings; their size and presentation need not be identical. Separate governing instructions from quoted source material. Preserve a route to the original when a summary could hide a decisive qualification.

When a message or work product leaves consequential uncertainty about how that material is understood or what the participant intends to do next, use the Reference’s collaborator application. Construct the alternatives that would change the explanation or division, then choose a small distinguishing return only when its value warrants the burden. Use the qualified result to clarify the needed meaning, revise the requested contribution or proceed with the supported arrangement. An unclear return leaves alternatives open; a supported action common to them can end the inquiry. Supplying a common brief alone establishes neither common understanding nor an accepted commitment. Keep ordinary settled collaboration lightweight.

Make result dependencies explicit. A source interpretation can begin alongside an independent calculation only if the calculation’s inputs are already settled. Otherwise obtain the prerequisite first or keep the dependent conclusion conditional.

For actions on shared executable state, establish who can write what and how incompatible effects are prevented. Isolate working copies or serialize conflicting actions under the real interface contract. Two participants cannot both rely on an old target state merely because their briefs or prompts differ. SYSE.20 and SYSE.40 supply overlap and shared-capacity conditions; SYSE.47 implements the chosen routing and limits.

SYSE.44:4.3 - Integrate claims against their actual grounds

Ask each return to preserve the result, premises, source/configuration, unsupported conditions and what it did or did not establish. Check that it answers the requested contribution for the same receiving use. A confident response to a nearby question is a missing contribution.

Reconcile disagreements by identifying the claim and its source or assumption. Compare original evidence, run a discriminating calculation or obtain a qualified specialist result when needed. Do not resolve common-source error by majority vote. Independence requires the evidence and checking relation that the claim needs; a second persona or fresh context alone does not supply it.

Combine only mutually usable returns. Test the joins: compatible units, definitions, input versions, scope and whole-result conditions. Preserve a supported partial result when another required result is missing, and state why the whole is still incomplete. The integrator retains the whole result’s required conditions.

SYSE.44:4.4 - Localize change and stop

When an input or source changes, identify the returns that used it and reopen their dependent conclusions. Keep unaffected results. Cancel or redirect obsolete work when doing so is permitted and useful; do not let its later arrival replace a result based on the new premise.

Use the integrated result in the receiving decision or action and observe whether it supplies the needed contribution. A handover delivered on time can still fail there. Return a context omission to context construction, a defective component to its supplier, a bad join to integration and an unsupported whole condition to the domain decision.

Stop when the whole result suffices or the remaining work cannot supply a worthwhile permitted continuation. A timed-out agent is an unavailable result, not evidence for whichever alternative the other agent favors.

SYSE.44:5 - Archetypal Grounding

Compare divisions for the same service-update proposal

The receiving result is a bounded service-update proposal with an applicable interruption/recovery contract and a capacity/backlog calculation. Target, source edition, demand interval, interruption duration, worker effects and allowed backlog must agree. The following are constructed comparison conditions, not measured agent timings.

One available LLM context can do both jobs. A two-context alternative gives the long contract examination to one context and the capacity calculation to another. Here the numerical input is already settled, the common brief is short, both contexts can obtain their needed source, and the integration check is a small comparison of duration, capacity and limit. A stipulated representative trial for this configuration shows that the one-context way repeatedly loses a needed contract qualification when moving between the long source and calculation; separate working material avoids that repetition without adding an equally costly join. The preference is adequate result with least total preparation, execution and repair burden.

Compare three complete ways. One-context completion retains the repeated rereading/checking cost but needs no handover. The proposed division adds the short common brief and join, while keeping each examination usable. A third proposed division omits the settled duration from the calculation brief and makes it a later return from the contract reader. That arrangement creates a serial dependency: the calculation must wait or stay conditional, so its apparent parallel gain is unavailable. C.38 constructs these ways and C.11 selects the second under the stated evidence and preference. No number of contexts by itself supplies the choice.

The contract reader returns the allowed recovery operation, duration, worker effects and source edition. The calculator consumes the settled inputs and returns the backlog trajectory with units and assumptions. Integration compares the modeled interruption with the contract and uses the joined proposal in the engineering decision. A fluent summary that omits the duration would fail this join.

Now supply a short authoritative contract excerpt and a calculation that the same one context can keep and check reliably. The repeated-rereading cost disappears while the extra brief and join remain. Reopen the same-result comparison and keep the work together. If instead duration was genuinely unsettled, obtain it first; useful source examination may continue while the capacity result stays conditional.

During a divided attempt, a new contract edition doubles the interruption duration. Reopen the dependent trajectory and the proposal that consumed it. An unrelated description of the monitoring interface remains usable. If both contexts copied an incorrect capacity from one summary, their agreement adds no independent evidence: obtain the actual capacity basis and retain the calculations as conditional if it is unavailable.

People supply the same joined contributions

A contract engineer and a capacity analyst can enact this division with source access, a written brief and an explicit receiving decision. The engineer returns the applicable duration and recovery condition; the analyst calculates from that version; the integrator checks their shared assumptions and uses the proposal. If both copy the same erroneous capacity sheet, different professional roles do not repair the source. A changed duration reopens the dependent calculation just as in the technical case.

This common operation does not require identical human and model mechanisms. Human availability, preparation and coordination cost enter the whole comparison; model input limits and repeated invocation cost enter their technical realization. For the small dependent digit operations of 347 × 6, keeping one performer and a readable carry layout can remain the cheaper adequate way.

SYSE.44:6 - Bias-Annotation

Benchmarks with easily separable questions can exaggerate the benefit of parallel agents. Shared state, source revisions and specialist authority often dominate real engineering work. Compare the actual arrangement at its required joins, not a generic multi-agent label.

SYSE.44:7 - Conformance Checklist

The division is compared with one-performer completion for the same whole result, including preparation, dependency and joining costs.
Each participant receives the needed common premises, sources, boundaries and receiving use; consequential uncertainty about interpretation or intended continuation is resolved enough for the selected action, or remains explicit.
Serial dependencies and conflicting effects remain explicit.
Returns retain their evidence and unsupported conditions.
Integration tests compatibility and common-source failure rather than counting agreement.
Changed premises reopen only affected returns; the final contribution is used.

SYSE.44:8 - Common Anti-Patterns and How to Avoid Them

Invent roles before finding contributions. Identify a missing result and its integration condition first.

Give every agent the entire history. Select the needed context and source return; duplicated overload can defeat the proposed division.

The integrator smooths over disagreement. Preserve the exact incompatible claim until evidence or a decision resolves it.

SYSE.44:9 - Consequences

The arrangement can obtain separable results with better attention or shorter elapsed time. It adds communication, integration and shared-resource costs, and can amplify a common error. A usable result may therefore justify fewer contexts or a narrower division after comparison.

SYSE.44:10 - Architectural Rationale

Contribution design and executable routing are different results. This pattern constructs what the participants separately supply and how their returns combine, consuming the existing whole-way comparison and choice. SYSE.47 builds the surrounding procedure. Keeping the distinction permits a useful human-integrated comparison before automating the arrangement.

SYSE.44:11 - SoTA-Echoing

The practice question is when divided work improves the receiving result after its joins and total burden are counted. For the LLM realization, Towards a Science of Scaling Agent Systems, v3 supports a task-dependent comparison rather than automatic gains from team size. Its tested configurations do not establish a universal architecture ranking.

Adopt the comparison of task structure and coordination burden, and qualify the actual joins and evidence dependencies here. A single capable context is the serious baseline. Reopen the division when shared errors, context loss or integration cost defeats its expected contribution.

SYSE.44:12 - Relations

A.15.9 and SYSE.9 supply bounded requests and qualified use. SYSE.18 addresses independent governance; SYSE.20 addresses overlapping work. SYSE.42 executes needed calls, SYSE.43 supplies selected retained context, SYSE.47 builds routing, and SYSE.46 tests the configured result. C.38/C.11.CRC compare complete alternatives when changing the overall obtaining arrangement. A.3.3.PI supplies the consequential hidden distinction and its revision; MMP.8.SD compares information-dependent continuations, with C.11.DUA judging inquiry burden. The Reference application connects those results to the participant’s contribution; A.15.7 uses the qualified observation in the next action.