The other issue is for use cases in which admin_level=6 CCC entities have been added by exception to an end-user’s application while admin_level=8 entities are added by rule. If the level 8 boundary gets added later, it could get swept in without anything to indicate the duplication. If there is at least a CCC indicator in tagging, the end user can query for the CCC IDs and handle the duplicates. That would impact me directly, along with any data consumer querying for 7/8 boundaries by rule and others by exception for city-level boundaries.