Changes - yes, there's been one change so far; and we're working on a second. It's not really a problem at all.
It all works out in the end. It's only money, right? Unfortunately, it's all too typical of how some large successful companies run projects - everyone likes to delegate but some decisions will always need to be made near the top. That's called leadership but it's hard work because it means dealing with uncomfortable details. After all, that's what IT Managers are paid to do, right?
ACC clauses frequently come into play in jurisdictions where property insurance does not normally include flood insurance and expressly excludes coverage for floods. The classic example of how ACC clauses work is where a hurricane hits a building with wind and flood hazards at the same time. If the evidence later shows that the wind blew off a building's roof and then water damage resulted only because there was no roof to prevent rain from entering, there would be coverage, but if the building was simultaneously flooded (., because the rain caused a nearby body of water to rise or simply overwhelmed local sewers), an ACC clause would completely block coverage for the entire loss (even if the building owner could otherwise attribute damage to wind v. flood).
The reading of named properties returns the first value found, on the object or then from its prototype chain. The assigning of a value to a named property on an object will create a property on the object itself if no corresponding property already exists.
So as many others mentioned, the problem is that the inner function is referencing the same i variable. So why don't we just create a new local variable each iteration, and have the inner function reference that instead?