Mentioned in today's sync meeting. It would be good to define which build infrastructure should be shared and required across all repositories inside the VMR. I was thinking of the following pivots:

1. The eng/common/ layout: That directory tree is already read-only in consuming repositories and not intended to be changed.
2. The .NET SDK: The toolset SDK is the thing that is currently propagated via Arcade but picked up at different times. I.e. some repositories today prefer to not be on the latest preview. As part of the VMR consolidation, it makes so re-evaluate that option and consider requiring one version of the SDK for all repositories.
3. The Arcade SDK: Recently the Arcade SDK got more tied to the .NET SDK so that it can depend on newer features or bugfixes.

There are probably others but these are the main ones that I'm concerned about at the moment.

cc @mmitche @MichaelSimons @dotnet/product-construction

T-Shirt Size Large (includes design and implementation)