What are the files in Sugar 11 that are called orderMapping.php?

Question

Matt Marum & Michael Shaheen - 
 Sugar 11 has added a bunch of new files in the custom directory with the name orderMapping.php. Can you explain what these files are used for? Do they get rebuilt via QRR? 
 They causing havoc with Source Code Control. 
 Example custom/Extension/modules/Opportunities/Ext/LogicHooks/orderMapping.php 
 <?php
// created: 2021-03-26 10:56:52
$extensionOrderMap = array (
 'modules/Opportunities/Ext/LogicHooks/DeleteOpportunity.php' =>
 array (
 'md5' => '38db1da780d6b18f38b7cb5472758c17',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/FixWorksheetAccountAssignment.php' =>
 array (
 'md5' => '9aa1f6f0d6be9066c4f142f9af8db4ea',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/GenerateRenewalOpportunity.php' =>
 array (
 'md5' => '207fa6307d110a83eba589f7ed82082d',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/OpportunitySalesStatus.php' =>
 array (
 'md5' => 'c35c3364902925e5a15e2cc82e38062e',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/OpportunitySyncWorksheet.php' =>
 array (
 'md5' => '97276a801d4a0c4d0b40e0dca02a6ca4',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/QueuePurchaseGeneration.php' =>
 array (
 'md5' => 'de3fe02382aacc28473b01b831b74814',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/SetCommitStageForClosedWon.php' =>
 array (
 'md5' => 'bf9f44d5d332a045ceeddb7c2557ed14',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/SetForecastCommitStage.php' =>
 array (
 'md5' => '5c1669e98c87c034c284be74b061e5bf',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
 'modules/Opportunities/Ext/LogicHooks/SyncBestWorstWithLikely.php' =>
 array (
 'md5' => 'cff052a0a6215992ef2e9004f9983c36',
 'mtime' => 1612792956,
 'is_override' => false,
 ),
);

Jeff Bickart · Answer

Jeff Bickart , 
 These are auto-generated files which you should not modify manually nor include into module loadable packages in any way. 
 I am a little confused on why you would have conflicts. Are you mixing the full versioning of your code base with Studio/Module Loadable Packages changes by any chance? Or how are you working today? 
 
 As you would understand there are two approaches based on Module Loadable Packages (cloud or on-site) and full system versioning (on-site). 
 These are the approaches I see going forward: 
 
 Sugar Cloud : you should not worry about their existence, they are there to help the system have a fixed order of merging that will not change. New files added, will be merged last. Never include those files into Module Loadable Packages, modify them, nor delete them 
 On site : you should version them as part of your code tree as those files will evolve automatically (if today your approach is to version the full code or even just the custom directory). These files should not be modified or deleted manually. If instead your approach is to just use Module Loadable Packages, you would follow the same approach as Sugar Cloud above

When copying/promoting an instance (eg: from Dev to UAT), you should copy those files as any other file across, and not modify them manually in any way. 
 
 They are really a system's reference point on when a file was first seen/merged, so that the order of merge is consistent. They are not supposed to be changed manually. 
 
 Hope that answers your questions