Carbon calculation updates - factor in flexibility/history archive or rebaseline for customer operational processes

The recent update to the Carbon calculations in CLDY has highlighted an improvement area that would help with customer adoption.

Customers who baselined using the previous calcs would have seen their numbers jump 4x with the recent change to the calculation methods through no action/change on their side.

If they had previously reported the baseline to their ESG Teams and were taking steps to reduce cost & carbon side by side, this unforeseen increase puts them in a tough spot to explain, and also affects confidence in the reporting. The net impact is that their comparisons are now apples to oranges unless the calcs are the same for baseline/operational updates/reporting moving forward. It also removes Accountability if the Carbon emissions will just change randomly - which is contrary to FinOps principles..

There is nothing wrong with improving our calcs (in fact this is a good thing as long as we stay transparent about them more so than the CSP's calc methods). 

Could we have a way for customers to either keep their historic calculations/what was reported and continue that as baseline; or rebaseline as standard if we change the calculations (or ideally give customers the choice to decide when new calculations take effect).  

This will be a bigger problem in future - German legislation has fines for inaction on carbon emissions - so if you were reporting some action/ reduction but then next month this looks like an increase (or inaction because it's cancelled out your activity) our clients could incur financial penalties. If customers cannot trust a steady baseline for reporting carbon emissions they will not adopt/operationalise the solution. 

Noting this now as Carbon Emissions exits beta in the next few months..