In creating an .esp you are fundamentally creating a list of changes to make to an .esm
Supposition #2:
An .esm file has the original "state of affairs" for a game (the original intent) while an .esp acts as a list of changes and additions to make to the .esm data during game play.
Question:
When we merge an .esp with an .esm does the .esm maintain the list of changes that were introduced in the .esp, or does the .esp get lost and the .esm take on a new "state of affairs" as if the changes were never made, i.e. as if the .esm with the changes of the .esp were the original intent? In other words is the original intent replaced by the new intent, or is the original intent still there, just with a list of new intentions?
I'm asking this to better understand .esm bloat. If I'm creating a new worldspace mod do I need to make every decision perfectly as .esp files are created so that my final .esp or .esm doesn't end up being gigantic? Or do i need to go back and remove every single time I slightly change my mind on a particular aspect? I'm asking this particularly about region generation. In other words generating a region... changing my mind about contents and removing the region... and then repopulating the region with new contets - does that cause my .esp file to grow unnecessarily? Do my old decisions get discarded when I merge an .esp file with the .esm.