InCommon maintained a "fallback" metadata aggregate in the event a breaking change to the metadata scheme was published and caused unforeseen issues with one or more metadata clients. In the event that InCommon operations needs to make a change to metadata schema that could negatively impact clients, we would create an "on-demand" instance of our metadata pipeline (likely a copy of the previous version of production with a different signing key) to allow for a temporary fallback.