When components are deleted, which system reflects those deletions?

When components are deleted, the system that reflects those deletions is the Destination Org. This is because in the context of continuous integration and deployment, the Destination Org is typically where the changes (including deletions) are intended to be applied after they have been developed and tested in other environments like the Source Org or Dev Org.

In a typical deployment process, the Destination Org is the final environment where changes, including deletions of specific components, are executed to ensure that the live environment accurately reflects the desired state. This means if a component was deleted in the Source Org and subsequently deployed, this deletion will be mirrored in the Destination Org, thereby maintaining consistency across environments.

The other environments, such as the Source Org and Dev Org, do not necessarily reflect deletions immediately since they may still contain the components until the next deployment occurs. Similarly, the Integration Org primarily serves to manage integration across various systems rather than holding the live state of the components.