A software integration gate runs at the boundary where independently developed units become one system. It can check interfaces, builds, end-to-end behavior, data compatibility and other properties that isolated unit checks cannot prove.
The parent workflow should rerun relevant child evidence and add checks for interactions among the parts. Completion is accepted only when the combined state satisfies the root requirements, not merely because each contributor reported success.
ELI5
A software integration gate is a required check performed after separately built changes are combined. It tests interactions that each part's own tests cannot prove, such as shared interfaces, data compatibility, builds, and complete user flows.
For example, two agents may each finish a module successfully, but their modules may use incompatible data fields. The integration gate reruns relevant checks on the combined system and accepts completion only when the root requirements work together.
How is an integration gate different from a unit test?
A unit test checks one component in isolation, while an integration gate verifies that multiple completed components operate together as required.
When should a software integration gate run?
It should run after relevant changes are combined and again whenever later modifications could invalidate the previously verified interaction.

