Integrating parallel agent results against one current artifact

Goal

Combine independently prepared changes without assuming that each worker’s passing checks remain valid after the changes interact in the shared result.

Prerequisites

Assign bounded ownership, identify shared interfaces, and record the base artifact each worker used. Decide who integrates the final result and which worker can still modify an area.

Steps

1. Require each worker to return a change summary, affected interfaces, actual validation, and unresolved assumptions. A message saying done is not enough to establish what can be safely combined.

2. Inspect overlaps in behavior as well as files. Separate modules can still modify the same data contract, configuration key, generated interface, or ordering assumption.

3. Integrate against a known current base and resolve conflicts deliberately. Preserve the reasoning behind incompatible choices instead of selecting whichever patch applies last.

4. Rerun checks that exercise interactions in the combined artifact. Keep worker-local results as scoped evidence, but invalidate them where another change altered their inputs or assumptions.

5. Exercise the process with two locally valid changes that disagree on a shared field or default. The integration gate should expose the incompatibility before reporting the whole task complete.

Expected result

The final artifact has its own validation record and an accountable integration decision. Delegated work remains traceable without treating independent local success as proof that the combined result works.

Limits and test basis

This original protocol has not been tested here. Ownership boundaries can miss semantic coupling, so the integrator must inspect shared behavior. Parallel work does not reduce the need for authorization checks or for reviewing the final user-visible outcome. Avoid keeping full duplicated work products after their useful integration lifetime.